Component count for a Single Release (FIX Version)

Manish Gupta

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

vitaliy zapolsk1

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.