-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Hi all,
I'm April, a product manager on Atlassian Teams 👋.
I appreciate you sharing your insights and use cases regarding this topic around associating a Team with a board. I'm keeping this as 'under consideration' because it's not on our official roadmap yet. We have some upcoming work that may tangentially address this. I will update once I have more to share around this.
Please feel free to continue to provide feedback on this suggestion in the comment thread below if you believe this is an important ticket to address. We will take this into account. Thank you!
Best regards,
Best regards,
April
Source feedback:
We have a common project with a Scrum Board per team. We would like to assign a Team to the Board and have all issues created on that board default to the team. This would seem like a very common use case.
Since Jira doesn't support this "Team per Board" ownership model up by design, each if our boards have a simple filter query "project = <projectname> and "Team[Team]" = 2"
That works fine.
However when we create new issues within the board, we want the Team field to default to the Board on which it's been created. Otherwise, newly created issues disappear from the board due to the query filter.
The Team field is not allowed to be a required field for some reason. The team field is not an easily accessible field for Jira Automation from what I've discovered. There's a few ScriptRunner and Jira automation w/ "Additional Fields" ways to possibly do this but it's very convoluted.
Will it be possible to have a Team default for a Board in the near future? If not, what's the recommended way to set the default the Team to a default per board where the issue was created? (e.g. when it's created within the backlog view or timeline view of the active board?)