Issues still show on watch/assigned board after marking 'done'

[Dustin Strange]

We have various project sections, most follow the same workflow (to do-in progress-done).  We changed the workflow for one, adding in a 'in review' step between being in progress and done.  

After doing this, those issues still show up on watched and assigned boards for users.  Hoping to get an answer as to what we can do to correct this.  Other projects with the unchanged workflow still work the same and the issues no longer show on boards once they are marked as 'done'.  

[Jack Brickey]

The answer depends on the type of board and whether we are talking next-gen project or not. That said, I am guessing you are using Kanban boards and recommend you compare the filter and sub-filter between the board that is working and the one that is not. I suspect on one your sub-filter is aging the Done issues but just a guess at this point.

[Dustin Strange]

Thanks, Jack...good questions.  Unfortunately I'm a bit lost with a lot of it. We were using Jira Core until about a month ago, and then we switched to Jira Software at the guidance of a new employee.  With that said, I am unsure about a lot of what you said.  Not sure that it will help at all but including a screen shot of one of the 'working' boards. 

[Jack Brickey]

YNo worries, glad to assist. So from the screenshot a) you are using a business project and b) you are viewing the default board. The default boards are not configurable. Which means that there are not editable filters. Done issues will age off over time to keep the board manageable. If you wish a control the behavior you may wish to create a Kanban board that will allow you to configure the behavior more completely. If you decide to do so please note that with a Business project you must use your profile as the “Location “ to associate the board. That is, it will not appear in the sidebar associated with the project. However, you can add a link to the board using the “Add item” link in the sidebar.

i thing there is more to discuss here but need to run to house closing. In the meantime I would refer you to the documentation for a bit of research. 

[Dustin Strange]

Thanks Jack - sorry, brain fart for a moment.  It's on my own personal dashboard for issues I'm watching (and also other employees, where they are assigned issues on their own personal dashboards) - those are the ones where 'done' issues are not disappearing!  

I'll certainly dig through the link you sent though!

[Jack Brickey]

Ok so is it a dashboard you are wanting to use and where you want Done Issue to not appear? If so then you need to create a filter that excludes Issues with status of Done or you can place an age limit on them, e.g. you want to see all issues including those done within say the last 7d but then disappear. Note that if you are using the “watched issues” gadget and if you do not select the “include resolved issues” then they should not show up IF the Resolution value is not “none”.

[Dustin Strange]

Correct, dashboard using the “watched issues” gadget, but also for other users on their dashboard where they are seeing issues assigned to them. But the problem is that both circumstances worked correctly until we changed the workflow on that one project, and now only that specific project is behaving differently. No settings or filters were changed on our dashboards to illicit this; the only change was adding a review step in the workflow between “in progress” and “done”. 

[Jack Brickey]

Please send screenshot of new WF.

[Dustin Strange]

First one is the problem workflow, second is one that works as expected and has not been changed.  

[Dustin Strange]

Not sure if we just need to eliminate the review step and only stick with the three original process steps since nothing else was changed to cause the issue. May just be out of luck.

[Jack Brickey]

One more request - can you send an image of your dashboard and watched gadget that is showing an issue that you believe would not have been shown in the previous workflow? As a test it would certainly be easy enough to  re-associate the previous workflow.

[Dustin Strange]

The second line, with key UA-49, has been completed but still shows.  Second screen is the details of that issue.

[Dustin Strange]

Any thoughts/suggestions?