nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

After the 8/26 "upgrade" to JIRA Agile (OnDemand), the REST API call for setting a rank no longer works

Lee Correll

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?

Accepted answers

Lee Correll

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.

All comments

Lee Correll

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.

Lee Correll

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.

Lee Correll

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud