Automation rules using "Field Value Changed" for the trigger. The "Team" Field is not available.
So good news. I the Premium Support team found a solution. Here is the video for my specific situation. I hope it also works for others looking for a similar solution.
looks really good! Thanks for sharing! Awesome tool.
are you using a premiere/business version of Automation for Jira? I don´t have all the condition check options?
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, we have Premium Jira in the Cloud. Also, this is automation for Classic Projects, not Next-Gen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Linda,
maybe the field is missing on your screen/s?
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is on all of the screens. Our issue is trying to use it for an Automation rule. "Field Value Changed" as a Trigger. "Select a Field" does not allow us to use the "Team" Field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Linda,
at least I can pick it. So it might be a permission issue. Can you please verify which Tempo versions you have installed (Timesheets only or Tempo Planner as well)?
You might want to create a support ticket for the Tempo support team.
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We don't have Tempo. The Team Field came in with the Premium Jira with Advanced Roadmaps. I believe that it originally belonged to Portfolio which if I understand correctly has morphed into Advanced Roadmaps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, sorry about the mixup where the field is coming from. Currently the Team field from Advanced Roadmap is not supported when using Automation rules, there is a bug logged for this, see JSWCLOUD-20812.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. I'm now "watching" that one and checked that it was affecting my team too. Not very happy that it's declared Minor with a Low priority considering Automation claims that it works with any Field... But that is the way of software development.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Tempo team field is not available from the drop down, so you would have click the More Options and set it using the additional fields. Note that you have to find the ID of the team you want to set the field to, something like this:
{"fields":{"customfield_xxxxx":4}}
custom field_xxxx is the Tempo Team field, and 4 is the Team name.
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.
On the action you have More option, click on it and you will see the additional fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If we are reading correctly this is for fields to edit. We want to trigger a rule when we change the Team field so that the QC Contact field automatically changes with it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, from what I could gather currently it is only the Tempo Account field that is supported, but I bet Atlassian is working on adding support for Team too. Let me see if I can find a request for it.
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.