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!


Automation showing a Specify the Priority (id or name) in the string format (priority) error

I am running an automation that clones a created issue into another project and then links the new issue and its clone. The rule has worked more times than not, but is failing randomly. The only correlation I can find is that the users creating the issues that fail are not users of the project. However the project has the standard permissions which allow non users to create issues. Just wanted to see if anyone knew why it would fail in these instances, or if there is another issue going on. I have attached my automation and the logjira automation error.PNG

4 answers

You have to have a issue Priority or the rule won't run for some reason.

have we found a solution for this error? I just got this error message when cloning an epic with multiple tasks.

I believe the issue may be that you can clone an issue where you are setting the priority to NULL (i.e. the original issue priority is also NULL).  I am currently battling the same issue

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 23, 2021

Hi @Colin Hunt ,

Do the projects share a field configuration? What maybe happening is in the 2nd project the Priority field is mandatory but in the first it isn't and therefore can't clone into that project as the Priority is not set.

Let me know if that is the problem.


Nick Menere
Automation Group Product Manager

@nmenere ,


That doesn't seem to be it. Priority isn't a required field in either project. I also tried to remove the priority value from the creation form, but that didn't recreate the failure. It just re-populated the field. 

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 23, 2021


I think this may require some debugging - looking at specific examples of issues where this passes and doesn't pass. I'd create a support ticket at and provide as much details of the issues as you can.


I m running into the same problem, when doing a bulk of issues. 

But the automation works fine when cloning less then 20 Issues.

Any news in this case?


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events