How to archive issues which should not be Done/Resolved in Next Gen Project Board?

[Ben Golder]

I'm looking to archive tasks which ended up being dead ends/put into purgatory and want to keep them off my kanban to keep things clean.

I do not use sprints/epics/backlogs on the board and due to how the boards are designed, the right-most column will always be the official "done" one, so I can't even de-clutter by putting the things that aren't to have attention paid to them off to the side and out of the middle of the board.

What options exist in this case? Are any of them free/don't require any kind of admin/security review (built in, not plugin) or a paywall?

[Jan Bennett]

It's not healthy to hoard old tasks indefinitely and in increasing number.

If you put them somewhere you can ignore them they just pile up and create a profitless cognitive load.

It could make sense to retitle them - from "X" to "parked_review-X-July-2021" and then put them into the bottom of a DEEP backlog.

If you have the right to amend the workflow you can make a special column for "parked forever"..."parked indefinitely".  That does cut into the display of columns but it also means you can see them (again we get cognitive load).  But then re-instating them can be plumbed into the workflow too... Having them there allows people to up-edit them if they remain interesting options for the future - especially if they can be "transformed" or sucked into other work items later or the reasons for parking them were changeable.

If however you want to archive these things because you want to have some trace for your work.. archaeology, history, proof of work in patent disputes, proof of consideration in design production or proof of work in job-history / historic cost analysis - then I want that too!

[Ben Golder]

Yeah this is just for POW/historic purposes more than anything else - we still do analysis on tasks which are from churned projects/customers.


We have a sort of "temp-purgatory" column for things that are just pending issue resolution or negotiation and can easily be brought back to life/moved to another column to reinitiate work, but for things which are due to projects/customers becoming dead in the water, we don't want to lose all the history entirely, just wanna hide it out of view of the board.

[Jack Brickey]

There isn't a way to do this in NG board. You could consider creating a "classic" kanban board for the NG project. This would allow you to exclude issues via the board filter. for example you could have a field for 'won't do' issues and exclude all issues w/ that field set.

[Jan Bennett]

When will archive for history be easy?  I do a lot of R&D and for contested IP it is important to be able to proove when I did actually do the work / have the idea ...

If we want a business tool then we have to respect this requirement.  Why would I give Atlassian any business-relevant details if archive for 20 years is not a respected feature?  I know Atlassian is looking for a younger audience who can't remember back that long.... but anyway we know it's important.

[Jack Brickey]

I can’t say. You might wish to use the feedback link and/or check jira.atlassian.com to search for an open suggestion.

[Ben Golder]

Yeah, this isn't a big enough deal to warrant interaction with another board/that much more complexity. Maybe 1-5% of tickets end up going this route and we already managed to have a pretty streamlined flow without the need for things like epics, etc.

Classic boards are also controlled by company admin rather than the individual, which means any changes that need to be made are gonna be a protracted, painstaking process.