Jira + Portfolio. One development project. Six dev teams. One board per team.
When I create an issue in the backlog of one of the boards, I want this board's team to be automatically assigned to this issue.
How do I do that?
assigning a team to an issue is not possible, but you can create a mailing list and create for this list a Jira account. (one list = one team). When assigning the issue to this account, all team members get notified.
This "automatic thing" will not work. If you have 6 boards, then at least your board filter must be clever enough so that one new issue does not pop up on all boards simultanously. Lets say you use labels Team_1, Team_2, ... then you have to set this label on issue creation.
To automate this, the logic "I am on board of Team_2, so I prefill labels with 'Team_2' and set assignee to account 'Team 2'" has to be injected when you press this create issue link. That's Jira Software.
Auto assign could be managed by components, if you use them instead of labels. There you can define a default assignee (Team_1, Team_2,..) per component.
As we're using Portfolio, there is a team field in the issue screen (standard level issues, e.g. user stories). And it's assignable, so I can assign a team to an issue.
What I'd like to have, is to fill this field automatically, whenever an issue is created within the board.
The board filter looks like this:
project = PROJECT AND Team = 4 ORDER BY Rank ASC
the 'Team' field is most likely a custom field introduced by Portfolio. To fill this automatically you need to extend either the board functionality (Jira Software) or when done on the Portfolio Screen within that plugin. For both you can create a suggestion at https://jira.atlassian.com
If you do not like to wait there will be no other way to do it on your own. Eventually with groovy scripts, but I doubt that this "On which teams board am I?" is easy.
I'm also looking for this. But besides that, I have the problem that I can't assign Private Teams to any initiatives, I've created my Team in Advanced Roadmap, but it doesn't show when I'm selecting the Teams custom field.
When I create a shared Teams, this is visible. But it doesn't work that well for me as the capacity has to be indicated in hours, not story points.
Any pointers on this?
Private Teams in Advanced Roadmaps are only available in the Plan where they're created. You can assign the plan-specific team to an issue and it will be visible in Jira. However, if you want to assign a team to an issue in Jira, then the Team must be created as a Shared Teams in Advanced Roadmaps. See here: https://confluence.atlassian.com/advancedroadmapsserver/showing-advanced-roadmaps-custom-fields-in-jira-857058481.html
If I understand your last sentence correctly you do your capacity planning with story points. This has to be enabled in Advanced Roadmaps by going to the Configure screen and choosing "Scheduling". There you will see the Estimation options and can choose to estimate in Days, Hours, or Story Points.
Hope that helps!
Hi, I recently found the "Automation Rules" to be very helpful for many things.
In my case, inherit Epic fixVersion to childs automatically when added or created withing the Epic, and secondly propogate fixVersions to all childs if an Epic is rescheduled for another release. Works like a charm.
You can find the Automation Rules in the System Config section if you are a full admin.
This is just a hint, as I didn't figure out how to add the custom field "Team" of portfolio to a rule via JSON code within the advanced options for the Automation. If this is possible and also to detect the board ID on which a ticket was just now opened, then it might be the magic we need as a workaround. Letdown, it has to be created from within the backlog/board to work I guess.
As mentioned, just a hint, as I didn't get to the bottom of it and don't know when I can spend time on this. Maybe someone with more skills in JSON and understanding the JIRA DB and Fields better can solve it?
You can add Team values to an issue using Automation via JSON but you need to know the custom field ID of the Team field. It would look something like this:
where "12115" is replaced with whatever the custom field ID for Team is in your system and "396" is replaced with the Shared Team ID from Advanced Roadmaps.
Also, our automation is set up to assign the Team field when an issue is assigned to a Sprint. We use a naming convention for our sprints that includes the Team name (e.g., Sprint 3 - ABC). Then, in the Automation script, we use a JQL condition to determine which sprint the issue has been added to (e.g., "sprint = "ABC""). So when the Sprint value is changed in an issue then, based on the sprint name, we can assign a Team value.
Hope that helps!
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events