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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have setup Change Management workflow which my team is happy with, and now I'm trying to make some fields not editable, unless it's during a specific transition.
I created a separate Create, Edit, and couple of Transition Screens, and everything works fine. For example I have Jira Automation populating Change Risk field automatically based on Service Tier and some other fields, while user is not able to set or change this field as it's not in Create or Edit screens. On the screenshot you can see how Change risk is not in the Edit screen, but Jira Automation is able to update it.
One field I have issue with is Approvers group, that is populated by Jira Workflow approving step (Affected Services).
If this field is present in the Edit screen, the group is added, and in History I see "Automation for Jira updated the Approver groups"
however, when field is removed from the Edit screen, it never gets populated. You can see on the screenshot how when I remove the Approvers group from the Edit Screen, nothing happens when transitioning from Open -> Under Review
If Jira Automation bot account has permissions to modify hidden fields, why does it not work in this case with Service approvers group?