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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,555,884
Community Members
 
Community Events
184
Community Groups

Distribute permissions to transfer issues statuses between groups

Deleted user Jul 12, 2019

Hi there. 

Our workflow consists of these statuses:

  1. To Do
  2. Selected for Development
  3. In Progress
  4. Code Complete
  5. Under QA
  6. In Review
  7. Reopened
  8. Resolved
  9. Done
  10. Closed

And we have 2 groups:

  1. Developers
  2. Testers

What we want is to allow all users to create issues (which is already done by default) but to allow transfering specific issues statuses only for the appropriate group. So issues with statuses 1, 2, 3 can be transfered to the next status (up to 4, but not 4 to 5) only by Developers. Testers take issues from status 4 (Code Complete) and can transfer their statuses from 4 to 10. 

I suppose I should write some jira.permission.???.group conditions to appropriate statuses in our current workflow. I have also found this list of jira.permission parameters: admin, use, sysadmin, project, browse, create, edit, scheduleissue, assign, assignable, attach, resolve, close, comment, delete, work, worklogdeleteall, worklogdeleteown, worklogeditall, worklogeditown, link, sharefilters, groupsubscriptions, move, setsecurity, pickusers, viewversioncontrol, modifyreporter, viewvotersandwatchers, managewatcherlist, bulkchange, commenteditall, commenteditown, commentdeleteall, commentdeleteown, attachdeleteall, attachdeleteown,viewworkflowreadonly.

But I don't really know what parameter I need and whether it's the one I'm searching.

Will be grateful for any help.

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 13, 2019

You've found workflow properties - these are not quite the right way to do this.  You need to use "conditions" in your workflow.  These put rules on to transitions that say things like "only group/role X can use this transition"

Like Deleted user likes this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events