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
I am leveraging advanced roadmaps across 10 different jira projects so that I can visualize and manage cross-team dependencies. Each project = 1 team.
1. To get a Team associated to a Jira issue, I have to publish an edit to Advanced Roadmaps.
This spams the team with email notifications (they have a lot of tickets in their respective projects). Is there any workaround to not do this? I tried to bulk edit within Jira but looks like this needs to be done from Advanced Roadmaps.
2. Assuming every issue in a Jira project needs to be associated with its respective team, is there any sort of clean automated way to ensure new Jira issues are tied to the team? Or is this something we need to manually reconcile on a continuous basis?
And yes, you can use automation to add the Team.
In Project A create automation like:
Trigger: When issue is created
Action: Edit issue
Currently the “Team” field cannot be selected from the “Choose fields to select” dropdown, so you need to add a Smart value setup like this into the “more options” section.
Note; Team 298 is just an example. To find the relevant team name type into Advanced search (JQL):
Then start typing the name of the team and select it from the list. JQL will transform it into the number
I tried setting this up for my Advanced Roadmap as I have multiple projects included in the Roadmap and each project represents one team. I got this error:
How do I fix this? Ideally, whenever someone creates a ticket for a particular project, when I go to view this ticket in the Advance Roadmap, I will see a team assigned to that ticket.
Thanks for the assistance!
So 116 is definitely a valid Team ID, yeah?
Can you share the rest of how you have put the automation together please? as I have never encountered that error.
But, what you want to do should be achievable.
Is the Team field available for all the issue types and projects in scope for your version of te automation?
You could turn your teams into "shared teams", in doing so, this opens up the "Team" field in Jira, that you can add to your screen as each shared team will become an entry in the "Team" field dropdown, and you can then do your bulk edit, to get all the existing issues caught up with the "Team" Value.