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; } } }

JQL Search by ID across projects is inconsistent

Zach Gutterman

I'm working on a JIRA integration that would allow me to log new accepted issues using camel across all of our team's projects. To do this, the camel component looks for the most recent issue ID (not key) and then does a JQL search for issues that are accepted and have an ID > the most recent id when the camel route is started. The weird thing is that the JQL ID > search provides really inconsistent results. For example, searching our team's issues in the browser with JQL for issue id > 1200 gives me 15 results for one project, searching for issue id > 1500 gives me 26 results for yet another project and so on. It seems like IDs are only consistently sequenced within a project but not across projects. Is that the case? Is there a way to change this sequencing? Why does a JQL ID search not recognize that an id of 2702 is greater than 1500?

Accepted answers

All comments

Nic Brough -Adaptavist-

The ID of an issue is the unique key for it in the database. This table is not divided by project, every new issue gets a key id a bit higher than the last one, irrespective of the project or anything else. Also, they're not sequential, you will find you've got gaps in the numbers.

The ID is simply the wrong thing to be searching on, you should assume it is a simple unique key and nothing more.

This cannot change, you'd have to rewrite Jira to do it.

Zach Gutterman

Appreciate the reponse. Why does the JQL search results look like this? First image looks for ids of a lower id number but returns fewer results AND all of the results are always limited to a single project. Screen Shot 2021-12-16 at 9.45.10 AM.png

Zach Gutterman

Another example of this issue is hitting the following endpoint (this time i'm testing on JIRA cloud and seeing the same problem):

/rest/api/latest/search?jql=ORDER+BY+id+desc

And getting the following results. You can see that the ids are not returned in order. Screen Shot 2021-12-16 at 10.52.10 AM.png

Zach Gutterman

It looks to me that sorting by id actually is sorting by key perhaps?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jql