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?

[Sheraz Muneer]

In the scenario you described, using a custom field of the type 'Select List (multiple choices)' seems like a suitable approach to tag the teams working on your issues, especially when you have a fixed set of teams.

As for pairing assigned persons with their teams for increased efficiency, one potential solution is to create a separate custom field for team assignment and another for individual assignment. The team assignment field could be a dropdown or select list where you can choose the relevant team, while the individual assignment field could be a user picker field that allows you to assign specific individuals to the issue.

By utilizing separate custom fields for team and individual assignment, you can track both the overall team responsible for the issue and the specific individuals involved, providing clarity and accountability.

Regarding best practices, it's important to align your approach with your team's workflow and preferences. Custom fields offer flexibility, so you can adapt them to suit your specific needs. It's recommended to communicate and collaborate with your team members to ensure the chosen solution meets everyone's requirements and promotes efficient tracking and filtering of issues on boards.

Remember to document and communicate the usage of the custom fields to maintain consistency and avoid confusion. Regularly reviewing and updating the custom field options can help ensure they remain relevant and aligned with your team's structure and evolving needs.

Ultimately, the recommended way to handle this scenario may vary depending on your team's unique requirements and the project management tool you are using. It's advisable to consult any documentation or resources provided by the tool's vendor, as they may offer specific recommendations or best practices for managing teams and issue tracking within their system.

CEO https://proinstaapks.com/

[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.