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

Value selected from a single choice select list changes when issue is created.

Ken Wood

User selects value A from a single choice select list.

When the issue is created, the value shown on the view issue screen is value B, not value A.

I've checked, there is NOT a post-function on the create transition that sets the value to B.

Where else can jira set/change the value of a custom field if there is not a post function on the transition that is doing it. I.e. Where should I focus my investigation?

Jira 7.8.1

Accepted answers

Ken Wood

Found the problem - the create screen was using a custom field called "request source" but the view and edit screens were using a custom field "requested source" - so the user was selecting a value from ONE custom field at creation time, but a DIFFERENT custom field was displayed on the view/edit screens. Because the two custom field names were so similar and had the same options, mass confusion resulted...

All comments

Steven F Behnke

It'd be good to check the Issue History to see if the field is being set after the issue is created originally. If it is being changed (you'll see a separate entry where that field is being set), then this could be an Event Listener or an external service operating from Webhooks.

Ken Wood

When I created the issue, I selected "Solutions Deployment" from the drop down.

When I looked at the issues immediately after it was created, the value somehow had changed to "Customer Operations".

The history only shows one event, and that's when I edited the issue to change the custom field value back to the value I selected originally.

So, good call, I should have checked that earlier, but sadly the only history I see is me editing it.

Field Original Value New Value

Requested Source Customer Operations [ 15077 ] Solutions Deployment [ 15076 ]

Tom Lister_fo1j4e

Hi @Ken Wood

Try rebuilding your indexes. Out of sync indexes can cause differences between database values and displays

Ken Wood

I'm doing a background re-index now, later today I can check to see if that resolved the problem.

Ken Wood

After a re-index, problem is still there.

Tom Lister_fo1j4e

Is this only on issue creation?

Can you correct in by editing?

Could you post screen shots of what you see on issue create?

( something obvious that once fooled me - if you're viewing an issue, and the go through create process, the new issue is not displayed to you, just the original issue you were viewing)

Ken Wood

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