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

On updating bugs, the bug marked as "Strike" just as bug displayed when moved to DONE

Deepak Soni

Hi All,

I need your help to understand on issue which I am facing while working on JIRA.

Whenever I update any BUG in JIRA like I added any comment or added no. of hours, etc then it get displayed as DONE. It's status is not changing to DONE, only it's id displayed with Strike on it. Just like when you mark any task or bug as DONE, then it displayed with Strike on it.

Can you please help that, why it is happening? And what changes I have to do in this regard. I am attaching a screen here. Please have a look.

Thanks,

Deepak

Accepted answers

Henning Tietgens

Is it a JIRA Agile simplified workflow? Take a look at the configuration of the board columns and double-check that the checkbox "Set resolution" is not set for the first column.

All comments

Nic Brough -Adaptavist-

You are setting the resolution by accident - do you have it on the "edit" screen for bugs?

Deepak Soni

No. I am not changing the resolution. On the edit screen I am just entering no. of hours or changing the assign etc. And after doing it, I saw that Bug ID marked as crossed.

After that, I am not able to remove that cross icon any how. Nothing works for me. Like you see in the screen shot. The Bug is in TO DO status and In Progress status but it is still showing as crossed.

Henning Tietgens

Is it a JIRA Agile simplified workflow? Take a look at the configuration of the board columns and double-check that the checkbox "Set resolution" is not set for the first column.

Nic Brough -Adaptavist-

I didn't ask if you thought you were changing the resolution, I asked if it was on the screen.

If it is on the screen, then you are setting it. You might not intend to, but if it's there, it will get set without you even touching it.

Please, check again - is the resolution on the screen you are entering hours or assigning on? (I don't mean the quick-edit options though, where you view an issue and can click on a single field to change it, I am talking about the full edit screen)

Deepak Soni

Hi Sir,

I checked and found that we are using "Agile Simplified Workflow". But Sorry I didn't understand the "Set Resolution" thing. I am new to JIRA.

If you can give me the steps like "Configure - Issues Tab - WorkFlow Section - Workflow option". Then It will be a great help.

Thanks in Advance,

Regards,

Deepak

Deepak Soni

When I am viewing bug on full screen then I am getting limited fields to edit like priority, resolution. So, if I need to enter the estimates then I need to go to Edit option. On that screen I don't have resolution option. (So, the probability of changing this field unknowingly is removed.)

Now, on the edit screen I change anything, then the bug shown as crossed. Interestingly, the Bug before edit shows Resolution as "Unresolved" and after edit any field for the bug it automatically changed to "Undefined" which is the default value.

And I checked the Resolution drop down value, I don't see any Unresolved option. That is, first time when you create a bug, the resolution is set to Unresolved and after creating a bug, if you change anything on the edit screen, the resolution gets set to Undefined and bug id shown as Crossed.

Regards,

Deepak

Henning Tietgens

Board -> Configure -> Columns: On each mapped status "card" there is a checkbox "Set resolution". This checkbox should only be checked if the resolution should be checked for an issue in this status.

Deepak Soni

Attached Screen shot of options i am getting

Deepak Soni

How to Close this question?

I am not getting any option where I can close this.

Nic Brough -Adaptavist-

Mark the best answer as correct - there's a tick mark to the left of the avatar of the person who gave the answer

Welcome!

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

Quick Links

Find more posts tagged with

jira

bug