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

Configuring new issue planning board position

George Stathis

There used to be a way to chose in Greenhopper whether new issues should automatically appear at the top or the bottom of the backlog in the Planning Mode view (with Ranking enabled). For a while, we had been experimenting with new issues appearing at the top but we would now prefer to go back to the default of having new issues show up at the bottom. For the life of me, I can't seem to find where that option can be configured any more (using on Demand version). I've gone through the docs and I can't seem to find where this is documented.

Is that option still available? If so, could someone please point us to the right configuration screen?

Accepted answers

George Stathis

OK, I think I know what's going on just not sure if it's a bug:

If one adds a new ticket from a view other than the Planning Board (e.g. from JIRA) then the new ticket does indeed appear at the bottom of the Planning View once we navigate there.
If one is in the Planning View and creates a new ticket, the new ticket will automatically appear underneath whichever ticket is currently selected
If no ticket is selected in the Planning View and a new ticket is added that ticket will appear at the TOP of the backlog. To reproduce, just manually remove the selectedIssue=XXX query string parameter from the Planning View URL and try to create a new ticket.

Is this just us or can other people reproduce this?

All comments

Christian Czaia [Decadis AG]

The board is based on a filter. You may have changed the sorting order of that filter. Go into your board's configuration (tab filter) and check the filter query. Make sure that the results are ordered like this:

"ORDER BY RANK"

Cheers Christian

George Stathis

Thanks Christian, we are actually using the proper filter for Ranking as described in https://confluence.atlassian.com/display/GH/Enabling+Ranking?application=cac&continue=https://confluence.atlassian.com/display/GH/Enabling+Ranking:

project = &lt;project name&gt; ORDER BY Rank ASC

We even tried playing with the ASC vs DESC order and tickets still appear at the top.

George Stathis

OK, I think I know what's going on just not sure if it's a bug:

If one adds a new ticket from a view other than the Planning Board (e.g. from JIRA) then the new ticket does indeed appear at the bottom of the Planning View once we navigate there.
If one is in the Planning View and creates a new ticket, the new ticket will automatically appear underneath whichever ticket is currently selected
If no ticket is selected in the Planning View and a new ticket is added that ticket will appear at the TOP of the backlog. To reproduce, just manually remove the selectedIssue=XXX query string parameter from the Planning View URL and try to create a new ticket.

Is this just us or can other people reproduce this?

Fabian E_

We've got the same behavior, and I think it's a but. At least it's unwanted behavior. We use Jira Agile 6.2.5.1.

I took the liberty to file a bug with your reproduction text quoted, I hope you don't mind: https://jira.atlassian.com/browse/GHS-10472

Peter_0kagsn

Thanks for the explanation George. It helps figuring out why some tickets are created on the top and some are created on the bottom of the backlog which seem to be unpredictable.

Now it makes more sense and made it a habit to always create a ticket outside the backlog.

By the way: see also https://jira.atlassian.com/browse/JSWSERVER-5368

I would rather see the following ticket to be implemented: https://jira.atlassian.com/browse/JSWSERVER-11139

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-software

jira-software-cloud