I am not sure that I understand the question.
I think what you mean is that you want to have some sort of relationship between a component and a team, and use that in JIRA somehow. If that is incorrect, could you correct me?
If that is correct, then I need to know how you are storing that relationship in JIRA, as JIRA has components as part of a project, not a team (so, off the shelf, the only available relationship is "a team owns a project, and that project has components, which implies that all those components belong to the team")
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 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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs