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

Why are new ideas ranked at the top?

Garrett Olsen

We're trying to use the native ability of JPD to use ranking across views as our central source of priority order. However, for some reason, when we create new ideas they seem to automatically shoot to the top of the view, and therefore the top of the ranking. Very rarely is the newest idea the very top priority, so this is a really strange behavior.

Am I missing a setting or is there some way to make new ideas sink to the bottom of the priority list rather than floating to the top? I'm wondering if there's something we've done that would cause that to happen because it seems counterintuitive.

Accepted answers

All comments

Nick Haller

Hi @Garrett Olsen ,

The order in which your ideas are shown would all be dependent on how they are being sorted, filtered, etc. - which you can control here:

In the screenshot above, the ideas are sorted by the key in descending order - so all newer ideas would appear at the top of the view. If you have some sort of "ranking" field, you could sort on that.

Yong Yang

Hi @Nick Haller

I think you might misunderstand this question.

Without any field ordering, the newly created ideas are always on the top while @Garrett Olsen expect they should be at the bottom of the board view.

From my personal perspective, the behavior design in All ideas view is reasonal because we want the new ideas to been seen firstly when someone is browsing this view.

Please correct my if my understanding is incorrect.

Thanks guys,

YY哥

Garrett Olsen

Yes, that's correct. I'm talking about when there's no sort applied, also known as the "project rank" which is shared across the entire project (and is manually ranked). We're using that tool to order our ideas by priority, which causes them to be ordered by priority across any view, which is super helpful to make sure there's a single source of truth for priorities.

The problem is, when you create a new idea, it goes right to the top of the "project rank". So every time we create ideas we're having to go move them down, since very rarely are the new ideas the top-ranked ideas in the whole project.

Hermance NDounga

Hi Garett,

When using the project rank, the newly created ideas are always going up to the top, and there is no way to have them created at the bottom.

Basically, that was a choice we had to make (should it be at the top or at the bottom?) and we chose that it would be created at the top, and for some use cases, it fits well, and in your case, when you have at the top the most refined and prioritized idea, it doesn't fit well.

Is there a field, or a combination of field that you are using in order to determine this priority?

If yes, then I suggest sorting your ideas through these fields in all your views, and so when you create a new idea, it will always go at the bottom.

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

Garrett Olsen

@Hermance NDounga There are fields we use to inform the order, but ultimately we're making decisions about the priority order, and JPD doesn't really have any capability for manual ranking other than the "project rank" drag and drop reorder. We could try to put a number in for the rank, but as soon as an idea moves up in priority you'd have to go change the number of every other idea below it which is totally impractical. I also really like how the project rank is shared across views because it means we can filter to various subsets of ideas without losing the priority order we've established in the priority rank view we've created.

I guess we'll just have to get used to moving new ideas to a lower rank manually.

kyle bell

Agree that this is a pretty strange 'choice' they made, as described in the original answer. "all new ideas are number 1 priority"? Quite annoying having to change this, and I'm having the same annoyance.

You can create them at the bottom of the list, but why would the 'Create' button and the in-line creator behave differently?