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:
https://jira.atlassian.com/secure/attachment/119285/Screen%20Shot%202014-05-27%20at%201.44.11%20PM.png
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.