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

Accidentally marked an issue as done, changed status back but it still doesn't show up on the board

Andrew Berry

At some point we had a workflow on a basic team managed kanban project accidentally changed to create issues with the Done status, so when a new issue was created it immediately disappeared from the board. I went back and found the issue and changed its status back to "to do" but the issue still isn't showing up on the board. I've looked at the relevant documentation I can find, but haven't found a resolution. Is there an additional status field I can change? Where is it?

Accepted answers

All comments

Valen Cardozo

Hi @Andrew Berry
A pleasure to greet you!
I understand that if a task is placed in done status, if it is then changed to another status for example: In progress, the task will remain with the Done check mark and will not appear in the backlog.

One measure that could be taken is to review the project schemas and the respective workflow of the tasks, so you can add a transition from Done to To Do or any other state you need.

Regards

Valentin

Joe Pitt

you need to clear the resolution field. That needs to be done in a transition with the post function to clear the field. The resolution field is NULL in the database. Any value in the field will show that it is resolved.

Andrew Berry

Thanks Valentin. After I fixed the workflow and confirmed that new issues are created in the correct status I did try adding an explicit transition from "Done" back to "To Do". Moving the issue in question back and forth through those transitions still doesn't get it to show up on the board. I looked for some sort of separate "Done" property I could edit directly but didn't see one anywhere. I also looked in the workflow configuration, I looked in the issue properties lists, I looked in the automation section. I don't see any likely field pop up in the field pickers, I even looked for documentation on the existing fields that can be accessed via JSON in the advanced automation section and didn't see anything that seemed likely. In fact I didn't see anything that looked like a complete list of JSON fields that had any sort of field that looked likely.

Andrew Berry

I looked for something like that in the workflow and I don't see any way to access the Resolution field there. The field just doesn't show up anywhere in this project that I can see. I can't add it to an issue type, I can't create a new field because it already exists.

The only place I can see a reference to Resolution at all is in Automations. I can create an automation that sets the Resolution field, but neither "Unresolved" nor NULL is an option. If I leave the value to set it to blank the automation throws an error when it runs:

Invalid value for resolution field
No fields or field values to edit for issues (could be due > to some field values not existing in a given project)

Maybe it's because this is a team managed project? Or some other aspect of the project configuration that makes this not available?

Edit to add: I can use an automation to set the Resolution status to some other value that's in the list (I get "Done", "Won't Do", "Can't Reproduce", and "Duplicate") but I can't set it to NULL as far as I can see

Valen Cardozo

Ok, I'm thinking that maybe it's due to a Kanban configuration.

I ask you, did you enter the board settings?
Maybe the "Done" status is not associated to any column and that is why they are not shown.

That's the only thing I think it could be, besides everything you already wrote.
If you come up with a solution, share it with me because I am very intrigued!

Jakub Sławiński

Hi @Andrew Berry

Can you check your board configuration? What do you have in the Kanban board sub-filter?

I have the following default:

"fixVersion in unreleasedVersions() OR fixVersion is EMPTY"

So if I set the fixVersion to a released one, I do not see the issue on the board anymore regardless the ticket status.

Andrew Berry

I've looked at the documentation for sub filter settings and I simply don't see those options in this project. Instead of "Board Settings" I see "Configure Board" which gives me far fewer options. I guess because this is a team managed project and not a company managed project? I see "Board Settings" in a different company managed project.

Andrew Berry

Instead of "Board Settings" I see "Configure Board" which gives me far fewer options and doesn't match any of the relevant documentation I've seen. I guess because this is a team managed project and not a company managed project? I see "Board Settings" in a different company managed project.

Joe Pitt

Most boards when you move it to done, it either automatically sets the resolution or asks you to put one in. It appears it happens automatically for you. A JIRA admin can fix this. Often if you reopen the issue the transition clears the resolution field.

Andrew Berry

I have full Admin access to our Jira instance. I just don't know what the heck I have to do to fix it.

Jakub Sławiński

@Andrew BerryCan you show some screenshots of your board and workflow configuration?

I created a completely new team-managed kanban project and everything seems to work fine. I can move tickets back and forth between statuses and the resolution is changing correctly. Moreover, I can always see the tickets on the board regardless they are in done or other statuses.

Have you done any custom modifications to project/workflow/board settings?

Andrew Berry

So I went back to this to try a couple things one last time, and the issue is showing up as it should now. No idea what happened. Random back end caching issue? Something really dumb on my end? Who knows. I appreciate all of the help.

If nothing else I've learned that Team managed projects are extremely limited in their capabilities (I get that simplicity is part of their point, but it seems like they're missing too much functionality) and are poorly covered in documentation, so we'll be taking that into account as we move forward.

Thanks everyone for your input.

Valen Cardozo

Pleasure to have tried to help you! @Andrew Berry
Cheers

Jakub Sławiński

No problem @Andrew Berry

Please remember that Jira Cloud is a living product and you cannot assume that if something works today will also work tomorrow

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud