-
Suggestion
-
Resolution: Unresolved
-
184
-
47
-
Hello everyone,
I'm April, a product manager looking after Atlassian Teams 👋. I appreciate you sharing your insights and use cases regarding this teams in automations.
We recognise its importance and plan to explore it further in the upcoming year. I'm moving this to the 'under consideration' phase, as it's not yet part of our official roadmap but is something we hope to explore within the next 18 months. I'll provide an update in a few months on where this is at 🙏
Please feel free to reach out in the comments if you have any questions about Atlassian Teams and I will try my best to answer you.
Best regards,
April
Issue Summary
Ability to Use Team field in Issue condition Field in Automation for jira
Steps to Reproduce
Go to project settings > automation > create a rule
Select Issue field condition and add the field Team and select in drop the value of the field
Expected Results
The automation should trigger a fine and run as expected
Actual Results
Could not evaluate this condition, Jira has given us invalid information about the chosen field, please contact Atlassian Support.
com.codebarrel.jira.model.team.ImmutableTeamBean != java.util.LinkedHashMap
...
Workaround
Presently the JQL condition can be used
- depends on
-
- Gathering Interest
- has a derivative of
-
- Gathering Interest