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

Problem: Resolution field auto selecting Fixed when Edit issue - Kanban

Blane Brady

I am trying to add epic names to these issues. They've been changed form an Issue type of Task > Epic so we can make them milestones for projects.

When I click into the now made Epic, I click on Edit (to change the epic name), but the when I get into the edit screen the Epic changes the Resolution field from Unresolved to Fixed automatically and Unresolved is NOT on the drop down. It then shows up crossed out in the backlog list. Please Help.

Inked2018-10-15 16_15_36-INPL board - Agile Board - JIRA_LI.jpg Inked2018-10-15 16_16_12-[INPL-305] Migrate Image Resizer from 129 subnet to 9. Subnet. - JIRA_LI.jpg Inked2018-10-15 16_16_30-Edit issue_ INPL-305 - JIRA_LI.jpg

Accepted answers

All comments

Bharath Kumar Kappala

Fixed must be the default value set for the Resolution field.

You can change that by going into Issues> Issue Attributes> Resolutions

Joe Pitt

Unresolved should never be on the select list. When an issue is opened the resolve field is NULL, which JIRA shows as UNRESOLVED. Once you put ANY value, including a space, in the field JIRA treats it as resolved. The ONLY way to set it back to unresolved is to use a transition that CLEARS the resolution field to set it back to UNRESOLVED.

Blane Brady

Ok, so as I get deeper into this issue I can provide some more information.

We are using our Kanban board to track task progress for projects. I don't understand why the task changes the resolution status out of blank just by editing the ticket. How do I change this? It then shows it crossed off like its complete with a strike through in the Task #. The status is ok for To Do, In Progress, Done, but the task name (INPL-331) shows crossed out and is confusing.

- Blane

Blane Brady

Thank you, this is great info. And as I really look into the issue I realized I don't care about the resolution status. We're using the workflow to track progress, To Do, In Progress, Done. It's a Kanban board and if I could just remove the Resolution requirement it should not be a problem any more... thought?

-Blane

Joe Pitt

Several built in filters, including the assigned to me filter uses the resolution field and only reports issues that aren't resolved. If you don't use the field every issue will appear in the results. Most people resolve the issue when moving it to the done status.

Something must be happening in the background during the edit function that is setting the resolution. Normally people only set the resolution in a post function during a transition.

Blane Brady

Gotcha, ya I'm new to helping this dept so I'm doing the new guy back tracing on their current stuff. This is one of the current quarks. Thank you for this info. Hmm, I'll try to look up issues with auto field updates after clicking edit.

Bharath Kumar Kappala

You must be having the Resolution field on the edit screen and defaulted to a value which is making this happen.

I guess this is what is happening in your scenario on the create screen you dont have the resolution field but on the edit screen you have the Resolution field (also the field value is set to a default value "Fixed" which I explained in my previous post).

I would suggest making these changes remove the default value for the resolution field also remove the Resolution field from the edit screen and set the resolution value in the workflow as a post function for the transition that you wish.

Blane Brady

Thank you I will try this - I appreciate everyone's input, between them all I think I understand how this part of the tool works and those screens. I'll let this page know if it worked and the resolution.

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