Best way to manage different product from the same JIRA project

[Troy Rambo]

I'm looking for some advice.

For a single external customer we have 3 products, all with the same bi-annual release dates. All managed by one JIRA project.

Two are part of the same common code base and linked to a SVN project, Fish Eye, and of course JIRA.  The third has it's own SVN code repo and Fish Eye configs, however they are part of the same DEV JIRA project.

In order to get a holistic view of all work being done by the team for a single sprint, I would like to manage them in the same Sprint board even though they have different Release versions,, components, etc so that in SCRUM we do not have to bounce between boards. 

Currently we are using two boards with queries setup to filter by the components.

The same single team of 3 developers work on all three products as a team, one QA for all three products, so separating the third one to it's own project is not an option.  I want to be able to manage this better to properly show what the entire team is working on in a single view.

Does anyone have a good way to manage this in one Sprint board view? or custom report

Help is much appreciated?

Troy

[Craig Castle-Mead]

Hi Troy,

While you could also use components to track the product as well - it’s an easy option but will be limiting (if you MUST have a product selected for every issue, you can’t just check if component is not empty as you mentioned components are being used for other purposes).

The cleaner option that comes to mind is adding a custom field for the product. If an issue will only ever be related to a single product, then single select drop down, but if there’s a chance an issue could touch 2+ (infrastructure changes, release, rebranding as a few examples) then a multi select list.  This will allow you to better error handle and report accordingly.

CCM