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

Deleted user August 27, 2014

Hi

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.

Thanks

Adam

4 answers

1 accepted

1 vote
Answer accepted
Deleted user November 24, 2014

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.

0 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 31, 2014

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

0 votes
Deleted user August 28, 2014

Yes it is that exact number

0 votes
CEDRIC ZABEL
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 28, 2014

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events