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

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

119 views 0 5
Read article

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