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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

user-specific permissions for work flow

My workflow involves approval where only 2-3 people on my team can approve. Is there a way I can set it so only they can approve and move the status from pending approval to approved?

 

Is there a way to make this a group permission if it can't be done on user level?

1 answer

Hi there and Welcome!

Depending on whether  you're in a SD project or not, there are several ways to do this. A way to do this is by adding a Condition on your transition (see screenshot). You can add the users to a group and then place a condition on the transition that only users in that group can do the transition.

When will this not work? When your question is about an approval in the SD portal. Was that your use-case? In that case you could use scripting to populate the approvers field of the issue once created.

Screenshot 2020-10-12 at 22.00.05.png

Let me know if this was helpfull.

Regards,

Jeroen

Hi,

please also consider to use Project Roles. This is more flexible and more generic, so in practice you benefit in two ways from Project Roles:

  1. Project Roles can be configured by Project Admins while Jira Groups have to be configured by Jira System Administrators. So Project Roles allow delegation.
  2. Workflows could be used in multiple projects. If you refer in Workflows to Jira Groups this is fixed for all projects using this workflow. Using Project Roles is more generic because it abstracts from fixed Jira Groups. In each project you can then define members of the Role which could be Jira Groups or single Accounts.

Kind regards,

Tobias

Hi,

related to "scripting to populate the approvers field" an important detail came into my mind. In the configuration of a field with type "user picker (multiple)" you should be able to define a default value. Such a field configuration can be project specific. If you don't put that field on an edit mask, users can not change the defined approvers.

This could be a simple approach to avoid scripting. A disadvantage is obviously that it is not very flexible.

Kind regards,

Tobias

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

133 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you