Browsing to completed projects

[Martin Ivanov]

Hello,

our team is trying to access old and completed projects (a few months old) but when we check the board - there is nothing there. I guess it has something to do with the status "Done". 

It is important to us so we could know what we have done with previous related projects. Currently, we found only a way to view old completed tasks by going into our mail notifications and entering a particular task from there. But if you access the project directly - there are no visible tasks. If we reactive a Done task to a In Progress, then we can see it.

Is there an easier way to view all tasks (Done included) in a project?

Thank you.

[Fabio Racobaldo _Herzum_]

Hi @Martin Ivanov

welcome to the Atlassian community!

If you are talking about a Kanaban Board, please review board settings. There is an option that, by default, hide tickets completed older than 2 weeks. You need to choose "Never mind, show all"

this should be the trick!

Hope this helps,

Fabio

[Martin Ivanov]

Hello, 

I am pretty sure this is the exact issue but I am not sure where is the setting in my JIRA Software.

I've tried looking into the Settings menus - Systems, Projects, Issues, but I couldn't find something resembling the screenshot you've provided.

Could you let me know where it could be found in a default JIRA interface?

[Jimi Wikman]

The green statuses have many functions and one is to mark completion, so issues are removed from backlog and active work period. Changing green statuses to an inactive or active status should not display them on the board, but it will screw up all reports...

If they show up when you change status, then you either have not mapped the closed status correctly, work in a Kanban setting where you do not release the board properly, so they end up hidden based on the board setting (this will slow things down a lot as time goes on) or your filter is not setup properly.

In Kanban, you will always have releases where you see old tasks and unless you work with continuous deliveries where releases become too much of a hassle, you should have them in a Scrum board as well.

You can also always user Filter to find any and all issues regardless of how old they are. At least the ones you do not delete annually as part of your maintenance cycle (I tend to remove everything older than 3 years).