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,639,539
Community Members
 
Community Events
196
Community Groups

Prevent Rank Changes

Hello there,

I'm trying to write an automation rule to prevent reordering of rank on our Epic Kanban board. Mainly so our filters can continue using ORDER BY Rank and be against an official order.

The end goal here is to limit the users to our Project Managers for ordering of Epics. It's a very easy activity to accidentally shift an Epic on a backlog and no audit to know who did it to help educate them away from that accidental action.

My two problems achieving this so far are:

  1. Setting the Trigger to target Rank
    • I tried field change with various attempts to find "Rank"
  2. Preventing the action
    • In my attempts to just prevent say Assignee from being set, I can't seem to find a way to prevent the action from being completed

Is this a legit goal/usage of Jira Automation?

Any help here would be greatly appreciated.

Thanks in advance,
Andrew

1 answer

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 26, 2021

Hi Andrew - Welcome to the Atlassian Community!

Automation Rules are not capable of preventing anything, including reordering. They only fire in response to a trigger happening and then perform some type of action. 

To prevent a user from being able to reorder cards based on Rank, simply remove their permission to the Schedule Issues permission in the Permission scheme attached to the project. 

I appreciate the quick response, John! That's what I was fearing. We went down the scheduling path before and it caused unintended side-effects. I'll need to google more and see if there are more docs around Scheduling and working around those side-effects. 

Thanks again!

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 26, 2021

Yes, one of the other side effects is that the user cannot enter estimates. 

@John Funk Is it possible in the team based project ?  I can'not see the option to prevent rank changes

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 13, 2022

No, rules cannot do that. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events