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
Next: Root
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
Hello Community,
I am having an automation issue. i want to create an issue in a project based on the team assigned.
i have no issues using team in filters, queries, etc... however when i try to make it a condition of an automation i never get a match
i have tried the advanced compare and JQL option, i have used {{Team[Team}}}, Team[Team], "Team[Team]", Team[ID], {{Team[id]}}, issue.Team.id. i have tied the number and team name with no success.
in filters "Team[Team]" = 27 works just fine but it seems like no variation i try works in a condition in automation.
Please Help!!!!!!!
Hi @Wally Brabec
Welcome to the Atlassian community.
Unfortunately Advanced Roadmap-> Plan-> Team field is not part of automation yet. There is feature request which is under consideration. There is a similar question already on the community regarding Team field. https://community.atlassian.com/t5/Automation-questions/What-smart-value-can-I-use-to-a-Team/qaq-p/2014541
If I were to implement this if there is not a lot of variations/teams/team-conditions I will try creating a manual trigger automation for each team/team-condition.
Hey @abelalia87
there is virtually no variation. if its team 1 a new initiative is created in that project, if its team 2 a new initiative is created in that project. so really a nested if.
when you talk about manual trigger would you do that in the workflow? not sure what team-condition means?
Very greatful for your quick response (a screenshot would probably show me what to do and where to go)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
sorry for the confusion about team condition, just how you would group a team into which particular automation, it is not a Jira jargon or anything. You can create two automations, one for Team 1 and another for Team 2. You can trigger it directly from the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.