Rank (Obsolete) number after project clone is all the same 19 digit number


We have recently cloned a project using the built in script of 'Script Runner' plugin as it contains a standard set of Epics and Stories that are required for each project.

After a project was cloned recently we found that all of the Rank(Obsolete) fields for each epic and story in the newly cloned project had been changed to the same 19 digit number instead of the original 4 digit individually ranked numbers.

This has resulted in some of our reports not working correctly as they input the data in rank order and with them all being the same number for this particular project it has resulted in that function failing.

Any help on this would be apprecaited.



4 answers

1 accepted

1 vote
Accepted answer

The 19 digit number was 9223372036854775807 and is the maximum 64 bit signed integer.

The cause of the error was due to the fact that the field had become obsolete.

Is that 19 digit number 9223372036854775807? If so, that’s the maximum 64 bit signed integer.

I don’t actually know what happened. I just thought this information might help someone else looking into this problem.

Yes it is that exact number

Isn't the Rank(Obsolete) field, err obsolete? Don't you also have a Rank field?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

921 views 3 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you