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

Move cloned issues to top of the backlog

When new tickets are created, they are moved to the bottom of the Backlog and that is fine.

In case of Cloned issues, we want to have them moved to the top of the Backlog.

We haven used some automation before, but I can't find the function 'move to top of the Backlog'. I know it should be possible to update the Rank field, but I have no idea how I can update Rank so that the newly created ticket is moved to the top of the Backlog.

Please send me your ideas :-)

1 answer

2 votes
Stefan Salzl Community Leader Aug 25, 2022

Hi @Richard den Dulk ,

As far as I am informed this is not possible with native A4J. I guess there is a way to do this with an API call out of your automation rule. This needs a bit more of "development" effort than just a simple automation rule. (see following link:

Furthermore an issue already exists suggesting this functionality you can upvote:

I found the following post that seems similar to your question:


Even if this doesn´t solve exactly your problem I hope I could at least give some valuable and helpful input.



Stefan Salzl Community Leader Aug 31, 2022

Hi @Richard den Dulk 

Could you try the mentioned options? Any feedback from your side?


Hi @Stefan Salzl ,

Sorry for the late reply.

I red your remarks and I also found the similiar post earlier. I am a 'non developing' scrum master in an organization where  add-ons are hard to get. So your remarks didn't help and that is the reason why I didn't reply.
I do understand the automation function in Jira, but I can not code. So I need a no-code solution. Maybe it is possible to get the highest rank via a JQL statement and somehow change the rank of the new story via the Jira automation function?

Otherwise I will have to wait until 'move to top of the Backlog' is provided in the Jira automation. I believe this is already a function in Jira, so it shouldn't be hard to implement.

Thanks for your reminder,


Like Stefan Salzl likes this
Stefan Salzl Community Leader Sep 01, 2022

Hi @Richard den Dulk ,

Originally I have "only" been a scrum Master too ;) It´s not about another add-on. The RestAPI is something that exists already within your Jira.

If you have engineers in your team or an admin by your hand it would 'only' be creating an API call that you than could include into your automation rule. So it´s not "really" a big development deal for engineers.

Furthermore: The JQL is an internal query language to search for issues. So to say: the output of a JQL is always a list off issues. everything else (like the rank or a value of a field) is kind of a property of those issues. A JQL can filter issues based on these but it cannot return the rank as a result of a jql.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events