Is it possible to archive a Jira issue (not delete it)?

I have one project & board, with multiple tickets in the backlog. We are not going to work on these tickets until late 2017. I don't want to delete them, since we'll need them in the future, but I also don't want to clutter my backlog with work that we don't need to discuss (or accidentally pull into a Sprint!). 

 

The only possible action that I can think of to "hide" these in the backlog view, without deleting them, is to do a bulk move to a new project that I could call "Archived Project." Is there an easier solution to hide/archive within the current project that I could restore in the future?

4 answers

1 accepted

6 votes
Accepted answer

Another project is one way to do it.

The other two options that spring to mind without coding are:

  1. Set a security level on the issues so that only you or admins or people in a certain group can see them.  Remove the security level when you're ready for them to re-appear
  2. Put a label or custom field on them to indicate "for later", then adjust your board filters to ignore that flag.  Remove the flag to get them back

You could combine those ideas too, although it's a bit of a faff - have a security level that uses the custom field flag to hide things (then you don't need to alter filters)

Another way to achieve this is configure issue security level to Archived. And set issue security level for issues to Archive issues.

Then you set users with issue security level "Archived" only to access these issues. Once your time has come to re-leave it to public, then you can remove security level of these issues and it will e open for everyone. When you start working on issue securities you'll e most happiest person.

You'll enjoy smile

Rangs

In other words, what the answer already said.

Like 2 people like this
1 vote
Joseph Pitt Community Champion Sep 27, 2016

You could create a status of 'On Hold' and move them to that status. When you configure the board don't show that status in any of the columns.

To create a new status, would I need to add it to the workflow? I suppose I could add it on the workflow, but not necessarily have anything move to or from it. I worry, though, that my users would "accidentally" move needed tickets to that status. I'll play around with it. Thanks!

If you want to use it with JIRA Software with Kanban (or kanplan), i like to use released version "Archive", because all issues with released versions are by default filtered out (by board sub-filter).

0 votes
kaszaq I'm New Here Dec 13, 2018

Depending what you mean by "need them in future" maybe archiving them using this tool would be sufficient for you? https://gitlab.com/kaszaq/jiratomkdocs/

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,284 views 5 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you