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

crossed out/strikethrough key

Mika Hotti

When epic is updated key is crossed out in any status. That is something I really don´t want to happen. It is causing many problems for me (I am quite new Jira Admin). Is it because for some (historical) reason in our organisation users want to update resolution manually? Because of that resolution field is active. Does Jira think that resolution is manually updated when epic is updated eventhough resolution field value is not changed?

We just updated the version to current 9.12.8 and I think that this issue came with that update. Our previous version was quite old and it´s support ends next Autumn.

I found a page which supports my thinking but I am not so sure about it:

https://support.atlassian.com/jira-software-cloud/docs/choose-when-subtasks-and-linked-issues-have-a-strikethrough/

So should I define resolution in workflow and deny all manual adjustments?

Mika

Accepted answers

Hans Polder_7ci2ta

@Mika Hotti ,

From which version prior to 9.12 did you upgrade?

Strikethrough of issue keys indeed happens when the resolution is set to any value other than the system default 'Unresolved' (or: empty).

The Resolution field should indeed only ever be filled once the ticket is resolved (and closed), not during the workflow.

See some more information here as well: https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html

All comments

Hans Polder_7ci2ta

@Mika Hotti ,

From which version prior to 9.12 did you upgrade?

Strikethrough of issue keys indeed happens when the resolution is set to any value other than the system default 'Unresolved' (or: empty).

The Resolution field should indeed only ever be filled once the ticket is resolved (and closed), not during the workflow.

See some more information here as well: https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html

Mika Hotti

Thanks!

Your comments solve the problem. I already had post function to update resolution when issue is done. I took resolution away from all screens so there is no more possibility to make that mistake. I added clear resolution transition to epic workflow so i can fix all mistakes we have in Jira. That is improving quality of our Jira data also.

I think it is not because the update but because the way some of our user are using Jira. I didn't find previous version easily because my technical colleague is on summer holiday.

Greetings from land of Santa Claus,

-Mika

Hans Polder_7ci2ta

Happy to hear that 🎅 came early this year

Regards,

Hans

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

jira-data-center

data-center