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

When editing an issue, the priority field shows a different value

Myra_Rebillard

I have issues with the field Priority not set.

They are correctly displayed with no Priority.

However, when bringing them up to Edit, the Priority field shows a different value.

I thought this could be due to a bad index, so I've re-indexed our whole system over the weekend, but this is still an issue.

Any ideas?

Accepted answers

All comments

Pete Singleton

Can you see which Priority is set as the default? When you edit the issue it is pre-selecting the default value, even though it was previously empty.

Myra_Rebillard

Hi Pete, thanks for looking into this.

The default priority is "Not reviewed".

It is pre-selecting "Blocker" even though it should be empty.

Nic Brough -Adaptavist-

The defaults only apply on issue create. Otherwise, they would overwrite a value incorrectly on most edits.

Myra_Rebillard

Hi Nic, yes, exactly. So what the team is doing now is setting it explicitly to Not reviewed when they do an edit so as not to change the value to Blocker.

This seems like an indexing issue, but we ran a re-index over the weekend but it didn't fix the issue.

Pete Singleton

I have reproduced this on our instance. Searching for issues where Priority "is EMPTY", and then editing one of those issues.... The priority field is shown on the Edit screen and 'Critical/Blocker' (our top priority) is preselected.

I can only assume that this occurs when the Priority field is added to a screen after the issue was created? Does seem like a bug to me.

Myra_Rebillard

No way! Thanks for trying (and succeeding) in reproducing it!

I've just searched open issues and didn't find one reported.

I'll try to reproduce it on my end as well then go ahead and create a bug. I'll update this with the the reference later.

Can you note version you are using? Our instance is 7.6.6.

Pete Singleton

We're on 7.10.1

Myra_Rebillard

Just a caveat to this, I am unable to create issues with no priority value, even when the priority field is not on the screen using normal create.

Some of the issues in our instance that do not have this value set (to the default) were created using a CSV import. Some, however, look like they must have been created using normal create. However, I don't know how to recreate that scenario at the moment.

Adrian Stephen_q490r0

There is actually no problem here. The priority field does not take null values. It always pre-selects the first value in the drop-down. So, if a user wants to keep Null values, they should remove the Priority field from the issue edit screen.

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