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

Sorting order filter for added sprint points

anne.gerten

Hello, when I go to the active sprint board -> Sprint Burndown widget -> Click on active points, then a filter with all added sprint tickets shows.

My question is about the order of display for this filter. In my example the filter is:
issuekey in (issue1,issue2,issue3,issue4,issue5,issue6,issue7)

Now the display order in the table is different:

issue1

issue2

issue4

Issue5

Issue6

Issue7

Issue3

Why is the table display not in the same order as the issues are listed in the issuekey filter?

Thanks

Accepted answers

Bill Sheboy

Hi @anne.gerten -- Welcome to the Atlassian Community!

I am unclear if either of those behaviors are documented...

The issue search which shows when the JQL runs appears to default to ORDER BY id DESC when no specific sort is provided (and where id is the Issue Id).

The order of the issues within that IN () expression is different.

What problem you are trying to solve related to those issue orderings? Knowing that may help the community to offer suggestions. Thanks!

Kind regards,
Bill

All comments

Bill Sheboy

Hi @anne.gerten -- Welcome to the Atlassian Community!

I am unclear if either of those behaviors are documented...

The issue search which shows when the JQL runs appears to default to ORDER BY id DESC when no specific sort is provided (and where id is the Issue Id).

The order of the issues within that IN () expression is different.

What problem you are trying to solve related to those issue orderings? Knowing that may help the community to offer suggestions. Thanks!

Kind regards,
Bill

anne.gerten

Thanks for your answer!

My problem that I am trying to solve is to easily see the newly added tickets to a sprint on a daily basis.

Bill Sheboy

I recommend trying the full burndown report for that, as it will show any scope changes and when they happened.

For a company-managed project: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-burndown-chart/

For a team-managed project: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-team-managed-sprint-burndown-chart/

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud