Component count for a Single Release (FIX Version)

This question is in reference to Atlassian Documentation: Managing components

Component as per my understanding is a unique value. Thus, why JIRA consider it as part of each project and not filter. i.e if ABC is component updated on 2 projects will show 2 different entry on heat map instead of 1.

This is not the distinct value as mentioned on heat map.

Please advice.

Thanks,

 

Manish

1 answer

This widget could not be displayed.

Your statement that each project has its own components list is correct.

The most closest analogue is a custom field having different contexts for different projects. Each context can have the same options, say A,B,C but they have different IDs. i.e.

Field Context for Project P1

Option A: ID=1

Option B: ID=2

Option C: ID=3

Field Context for Project P2

Option A: ID=6

Option B: ID=7

Option C: ID=8


That's why when you're looking for particular option value (say "A") JIRA retrieves 2 different internal IDs.
Heat map, it turns out, is using value itself.


Suggest an answer

Log in or Sign up to answer
Community showcase
Asked yesterday in Data Center

Hi! I'm Cameron Deatsch, enterprise enthusiast and Head of Server at Atlassian. AMA!

Hey team! I'm Cameron Deatsch, Head of Server at Atlassian. At our European Summit just a few weeks ago, I spoke about the latest regarding our Server and Data center products and o...

10,762 views 2 4
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you