Team Tagging: Best Practice?

[Aron Kuch]

We want to tag which team is working on our issues. Larger issues, like Epics, might have multiple teams involved. Additionally I hope to filter boards by which team(s) were tagged.

I have considered using labels, but we have various current and historical uses for that which would be difficult to clean-up. Additionally, the flexibility to add new labels might be problematic when we have a fixed set of teams.
I am currently considering a custom field, of the type 'Select List (multiple choices)'. Initial testing points to it working well for this purpose.
Categories and Components are out because each issue can only have one, as I understand.
If there's a way to pair assigned persons with their teams, that would be more efficient.

Is there a recommended way to handle this scenario? A best practice?

[Jeanne Howe]

Aron,

We also use a custom field for development teams.

Many of our teams have set up project automation rules to do various tasks, for example if there is only one team associated with the Jira project, a project automation rule can be created to set the custom field at the time an issue is submitted. For Jira projects that are supported by multiple teams, an automation rule may be run at the time of assignment (trigger = issue updated and a JQL to determine if the assignee has been altered). This rule requires a little more administration if your team members change frequently, an "IF" statement can be used to associate the assignee with the team.

I also agree with Sheraz, consider how your teams work, what their processes are, and the individual team requirements.