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

Project move problem

Rumceisz

Hi All,

we have a big problem:

when we move a project to another the order will be erased!

We order the issues in Issue Navigator: ORDER BY KEY ASC

and then move -> the order confusing.

Can you please help? It's necessary to retain the order of the issues!!!

Thanks in advance,

Rumi

Accepted answers

Jobin Kuruvilla [Adaptavist]

When you move, the issue key changes. And if you order by key, the order will change. Isn't that expected?

All comments

Jobin Kuruvilla [Adaptavist]

When you move, the issue key changes. And if you order by key, the order will change. Isn't that expected?

Rumceisz

I made an order by key asc and I also saved the original issuekeys in comment. After the move the order confused: which was the 1st issue with the old project key now it turned to far else in the target project key.

Jobin Kuruvilla [Adaptavist]

Order by key orders issues only based on the current key. it doesn't look at old keys or keys in comments. I don't think you can change that behavior - unless you store the order in a custom field and use that.

Welcome!

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

Quick Links

Find more posts tagged with

jira

project

move