Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to move done items into archive?

How to move done items into archive to avoid clogging the board? I have now moved items done to Backlog as temporary solution. Thanks.

1 answer

0 votes

What type of board is it?

If it is a Core business board, then issues will disappear 14 days after they have become "done".  If you are in a Scrum board, done items will go away at the end of the sprint, and on a Kanban, when you do a release (although if you're using Kanban and don't do releases, you might want to just change the board filter to add "and not (status = done and updated < -7d)")

Hi Nic,


It is a Kanban board. What I do now is create another Project called Archive and move the issues in Done list to Archive.


Ouch.  Moving issues between projects is a really bad thing to do as part of a day-to-day process.  It it good for re-organisations and housekeeping, but it should never be part of a working process.

May I ask what is wrong with "seeing 'done' for 14 days before the issues automatically drop off the board" for you?

The issues moved to Archive is the ones that are Done. For tracking history and past issues, we need to archive them and not automatically drop off the board.

Is there a board that allows Archiving?


No, your definition of "archiving" feels a bit wrong to me.  I archive things when I have confidence that they don't add a lot to immediate reporting, but might need to be kept for statistical reporting or audits.  The shortest time I've seen for an archive is "three months of inactivity"

Dumping "done" stuff into an archive just because you have done it this week sounds very wrong.  What are you telling your stakeholders here?  That you have binned stuff just because you think you might have done it?

So how do you archive?

I wait until a project is done, and then change the permission scheme does not allow changes.  On Data Centre, I wait until a project is done, and then hit the archive button.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

200 views 6 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you