Because that field (which used to be a custom field) seems to no longer be the correct field. However, Atlassians documentation doesn't seem to identify (and the REST browser isn't helpful) how to make that change any longer.
Anybody have a clue on this?
To which I got:
That is correct. As an example, please take a look at the following screenshot:
To understand how the Ranking field is now being stored.
So Atlassian has stripped the ability to rank issues without using the GUI. That's, in a single word, idiotic.
How it's being stored is a moot point - we never used an integer field to define rank in the API to begin with, we always identifed the issue before and after. There is no reasonable rationale for not including that code in the same ranking capability - Atlassian chose not to include it.
I got this response:
The new ranking field is now custom field id 11990, however, the changes made in rank system (the data format was changed, it's no longer an integer number) won't make possible any longer to use it as it's not usable data outside of JIRA Agile.
Sorry for not being able to further help you on this one.
Which would seem to imply that there is no ability to use the API to rank issues any longer. I asked that question, no reply from Atlassian yet.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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!
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