I have found that the the "new" issue view shows a strike through open issues I have linked. Easiest way to explain is with the screen shots.
I did discover that someone had created a resolution status of "unresolved", which I have since removed. There were only 2 issues that had been populated with that field, so I don't think this is fully related.
My main concern is linked issues should have the strike through unless they are in face fully done and resolved. First screen shot is the old issue view and second is the new issue view.
Dear @Jeneen_DesChamps ,
the strike-through is an indicator that the resolution of an issue != NULL (unresolved). Regardless of the status you can set the resolution to any value, if the configuration of your project allows this.
Good practice to avoid this is, to forbid editing resolution and just let the user select during one or two workflow transitions. Transitions from a "closed-like status" to an "open-like status" clear the resolution automatically.
So long
Thomas
Hi @Thomas Deiler , the issues that are showing with the strike-through aren't resolved, nor do they have a value in the resolution field. When I look at the issue with the "old issue view" the strike-through does NOT show, but the "new issue view" they are struck out. That is what is so frustrating about this! The main items I am looking are the tests (we have Zephyr add on) that have been linked to the requirements issues. The active tests have a status of Ready. I have no Ready issues with anything in the resolution field. (project = SL AND issuetype = Test AND status = Ready AND resolution !=NULL) 0 results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We use cloud, the projects are not Next-Gen.
I am wondering now if someone messed with the transitions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Jeneen_DesChamps ,
when you can exclude that somebody of you users messed up your configuration, I recommend to contact the support.
Have a look at https://<yoursite>.atlassian.net/auditing/view, first.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! We've had a few "too many cooks in the kitchen" with our JIRA configuration, so sometimes things aren't correct or easy to resolve. I find JIRA very confusing at times!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.