You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
is it, by any chance, possible, to auto-assign / pre-populate the team value on an issue?
We have teams being organized by components, each team has its corresponding scrum board that I use as source for the team assignment.
It's kind of cumbersome to assign each and every tiny bug ticket manually to the corresponding team.
Thanks a lot in advance
Hi @Hans Keller
You sure can....presuming you are on Jira Cloud???
If so, you can do this via Automation for Jira.
Trigger = Issue Created
Condition = User condition (where you then add the team members)
Action = Edit issue (at this stage the Team field isn't available in the dropdown of fields to select, so you need to use the more options section and set it up as below). Note; you need to know your Team ID (procurable via JQL)
Another Note, if you want to set up more than one team within the one Automation rule, use an "If/Else block" (as below)
Hi @Hans Keller,
I think that @Curt Holley has provided a good answer using automation, but I'd like to ask more about your use case if I may?
When you say that you have teams organised by component, does this mean that all teams work within the same project but are responsible for issues based on the component(s) assigned to the issue?
I can see from the screenshot that you have created teams in Advanced Roadmaps but I was just curious to see if you'd used the team field as a JQL filter value to define each team board (rather than say the components themselves). If this is the case then I'd be interested to know how you'd feel about having the team association on the board itself (rather than defined via the team in the plan)?
thanks for your fast replies and apoligies regarding my delay in answering.
Our Jira is self-hosted, it used to be Server and I guess that it has been changed to Datacenter - but definitely not Jira Cloud (which is not allowed for compliance reasons).
@Daveregading team- and project setup, it's a little bit more difficult, unfortunately (had to "anonymize" it a bit):
The whole Setup is Scrum @ Scale. For historical reasons (and compliance), we had to split into several Jira Projects, the blue boxes.
So we have one big project in the middle, where all the backend services are developed by multiple scrum teams and two smaller projects which handle the Hardware/Device portion and the other one catering for all oranizational overhead.
The smaller ones are rather easy, only one scrum team, only one component (if any).
The "Tardis" is more difficult, as we have cases where multiple components are handled by one team (could also be the other way round than displayed in the 2nd Tardis Issue, i.e. Team Rory handling Ami-Rory-issues) or Multiple Components are handled by mutliple teams.
I can see from the screenshot that you have created teams in Advanced Roadmaps but I was just curious to see if you'd used the team field as a JQL filter value to define each team board (rather than say the components themselves).
The Teams are defined by the corresponding Scrum Boards - e.g. the Tardis Project has 4 Team Scrum boards which are filtered by the value of the component field - we don't use the team field yet (and this sounds a bit like a circular reference - defining the team by using a board which is filtered by the team value defined in the team...)
If this is the case then I'd be interested to know how you'd feel about having the team association on the board itself (rather than defined via the team in the plan)?
I can't really imagine how this would look like - do you have a practical example?
@Hans Keller you have had way too much fun "anonymizing", but as a Dr Who fan, I love it. Brilliant!!
In terms of a practical example of Team association, it is simply replace filtering the board board via Component/s with filtering via the Shared team. See example:
project = LSTT AND "Team[Team]" = 213 ORDER BY Rank ASC
An advantage of using Shared teams, is unlike Components, they can be used across all Jira projects. So it would be easy for Rose Tyler to be in the TARDIS again, Rory could visit Gallifrey etc. :-)
It is also a fairly simple concept for teams to get used to...."For work to appear on our teams board, the work needs to be assigned to the Team".
This leaves the components to be freed up and used not just as a proxy Team field, but for actual components (you know, things like; Relative Dimensional Stabilizer, Exponential Crossfield, Omega Configuration, Spatial Dampeners, and Relative Continuum Stabilizer subsystems) Sorry, couldn't help myself.
Example of the Team field (which needs to be added into the relevant Field/ Screen schemes to be visualised) below.
Hi @Curt Holley , fellow Whovian :)
apologies again for the delay, daily business was a little overwhelming the last three weeks.
I guess using global / shared teams will be the right approach for us as well, we already use them partly now (not all teams being on the roadmap now, but some).
Right now I'm in a discussion with our internal JIRA support - they claim that it's not possible to display the "Team" field on an issue type as Adcanced Roadmaps blocks it.
Could this be due to JIRA Server or is there a misconfiguration?
Yes you can add teams to your screens in Jira server, see sample screen shot
I wanted to do this, but the issue we have, is that I have 200+ teams and because this is a locked field, I cannot change or add contexts. and for us we would need to add project context to have teams by project. But since the team field values are derived from shared team in Advanced roadmaps, and Advanced roadmaps has no concept of project/team relationship, this cannot be done, so we were unable to use team, cause a dropdown of 200+ entries would not be useable.
@Hans Keller , go in with eyes wide open, that the dropsdown is also not sortable. it loads the teams in an order (I think, as they were created in Advanced Roadmaps), because they are not alphabetical. And the managed shared teams in Advanced Roadmaps, does not let you sort them there. You would have to enter them in the order you want them to appear and if you have a new team, oh well, to the bottom they go.
Thanks @Bonnie Lopes - can you give me some more context where and how to enable this field? I want to give my support the best guidance possible in how to support me.
In regards of the Dropdown / Maintainability: Right Now, we are the only Program using the Porfolio, but Yes, I've already thought about this as well - my solution for now would be:
Does this make sense?
If you are using Server, you can also change your teams to shared teams and then the teams will actually populate in the Team field dropdown, so upon issue creation and update the teams are available.
We were set up the same way and wanted to take advantage of this but we have over 500 teams across 100 projects and the team field does not allow for adding project context, so we would have had a dropdown of 500 teams, which is un-useable, when with project context we would have just had 5 , which would have been perfect. So we had to create a separate custom field call scrum team where we can provide context and have the dropdown with 5 items per project. The unfortunate consequnce of this is we still have to manually update team for capacity numbers. We can bulk update team using scrum team, or write some automation to do same and will look to do that in our future as we start using our plans more and more.