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.
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
Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot