Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation for Approval in Team Managed project

I am trying to set an automation from a team managed project. I have a field that I am editing that is a drop down. The selection of a department name and then in the edit of this department name it then will edit the approver field in the team manged project. But I think the field its editing is from the jira classic fields not the team managed. Is there away to edit these team managed fields in automation to change the approvers? Do I need to create a new field with a different name?

2 answers

1 accepted

0 votes
Answer accepted

In this response I am assuming that:

  1. Affected Groups is a Group Picker (multiple) field that you created.
  2. Approvers is a User Picker (multiple) field that was either created by Jira Service Management or created by you. This doesn't have any particular special restrictions or usage instructions but JSM will recreate a field with this name if you change the field context or remove or rename this field.

JSM does not presently support using groups for approvals. See

Automation does not presently have an action or function to populate a Users custom field with members of Groups.  I cannot identify a feature request for that.

If you want to be creative, you could use an Outgoing Webhook action to the Get users from group REST API endpoint to obtain the members of groups and an advanced edit issue action to populate the Approvers field with the webhookResponse, but that wouldn't support multiple groups. I wish you luck with that.

Also note that using Automation for changing Approvers requires the workflow to have a self-looping "Change approvers" transition and a "Transition issue" action after populating the Approvers field.

Affected group is a dropdown, But I have moved this project back to a classic as there is a limitation in Team Managed projects of no context for approvals so therefore they can't be edited.

2021-06-15 12_37_08-Settings - Jira.pngThis is the automation but the field Approvers also exist in classic. This is in a team managed project.

<Moved to an answer in instead of a reply>

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events