Distinguish between different streams of work based on common fix versions

unknown

It's a bit tricky situation here 

My teams work on two different projects non-classic & classic 

All this while we had different fix versions for each so it was easy to pull up the trends using JQL/Dashboards. where we had separate dashboards for each project. But now we decided to merge both the projects and have a common fix version for both. 

I was wondering on how should I be able to distinguish between two projects as I need to pull up trends separately as the teams are separate.

To be more clear 

so there are two projects which different teams are working on
Classic - uses 5.5 as FV - so all the dashboards have trends based on affected version or Fix version - spread across various teams
Non-Classic - uses 2.23 as the fix version and likewise uses the same affected or fixed versions - spread across various teams

Now we want to merge from 5.5 and 2.23 to 3.5. However, they all represent under the same project in Jira but worked by different teams. It was easy to separate by fix versions, bit now when we merge Classic n non-Classic to one branch how best can I distinguish them. 

 

Appreciate quick response, thanks! 

Petter Gonçalves

Hello Ramya,

The best option you can use to distinguish issues of a common project between two different teams would be by using Components to identify them.

Components are subsections of projects that you can use to group issues into smaller parts, allowing your team to create customized boards/dashboards for their relevant issues, with customized notifications as well.

Been more specific, you would perform three steps:

1 - Create two components: Team 1 and Team 2

2 - Add the components to the relevant issues by using the bulk operation feature

3 - Move the issues to the common project

You can check more information on how you can create and implement components by checking the documentation below:

- Organizing work with components

Additionally, you can use Security Level to properly hide the issues from the other team, in case it is necessary.

Let me know if you have any questions.