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
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events