From a reporting perspective, 1 project with multiple boards or multiple projects 1 board?

[Jamie Sperla]

Use Case:

• all software change requests (new features, enhancements, bugs) need to be recorded, reviewed, prioritized, approved/rejected prior to being passed on to be development (i.e. supports an intake process)
• software change requests may be initiated from multiple sources (testing teams, product team, user feedback/product, other stakeholders)  
• software change requests may be assigned to a specific milestone / release
• software change requests will have different groups of people that need to submit a request based on milestone / release
• software change requests should be consistently recorded at initiation regardless of milestone / release association (i.e. a single template)
• software change requests need reporting based on milestone / release (number of cumulative requests by type)
• approved software changes requests must be associated with development work (done in separate project in JIRA) for tracking 
  • would be awesome if there was a way to report on software change requests based on the status(es) of associated dev tickets

General Question: Should I setup JIRA as 1 project with multiple boards based on milestone/release OR multiple projects (for each milestone/release) with a single board bringing in all software change requests?

*Note - a release is a set of features controlled by releasing branches of code.  What is released in 1 branch may only be shown to a certain group of users while another release may be a completely different user base.  

Questions:

• How should I setup JIRA to best support the above requirements and maximize value of out of the box reporting? 
  • I would like to report by milestone / release (most important)
    • I would like to report by software change request type (new feature, enhancement, bugs)
    • I would like to report by change request status
  • I would like to report cumulative of all milestones / releases
    • I would like to report by software change request type (new feature, enhancement, bugs)
    • I would like to report by change request status
• What other questions can I answer that will help drive the best setup to meet business requirements outlined above? 

[John Funk]

Hi Jamie,

I usually decide on projects based on the team. If there is one team working all of the stuff, then one project. If multiple teams or squads with totally different products, then different projects.