The issue has been marked as done for about a week, but it doesn't show with the strikethrough on the backlog. See screenshot - one is how it looks on the backlog, the other shows the status when the issue is open.
If it doesn't have the strikethrough the resolution isn't set. Your workflow is wrong. Issues shouldn't be able to be moved to Done without going through a transition where the user or a post function sets the resolution.
Thanks @Joe Pitt . We just set up this new next-gen board, so we only have To Do, In Progress, QA, and Done right now. So if the user moved it straight from To Do to Done, it would cause this to happen?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need to look at the workflow. The transition to what you are flagging as 'done' needs to go through a transition where the resolution field is set. I'm not using next gen projects, but the rule about resolution is the same. Also, look at the criteria for what is 'done'. The last time I used boards Done could be defined as workflow status and resolution value.
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.
@Joe Pitt Thanks for your help. But I'm still not sure why some issues show as done in some screens, don't show as done in other screens, yet other issues show as done in all screens - our workflow is currently the same for all issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Somewhere along the line a user is seeing a screen where they can set the resolution field or there is a possible branch were it is set by a post function. Is this a recent problem? Maybe the workflow was changed or the resolution field was deleted from a transition scheme. If you dig deep enough I'm sure there is an answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That totally makes sense, but it's been a problem across the board since we moved to next-gen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not using next gen yet so I don't know the difference. Did you migrate current project to next gen or start fresh? I suggest searching the forum and google about next gen problems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We started fresh. I'll search some more. Thanks so much for your help!
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.