Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bulk Archiving Issues

I'm looking to archive a subset (tickets created 7+ years ago) of tickets within a project.  I have the filters written...and when I try the bulk archive feature....because of the 1000 limitation (or current page)...there is a good possibility that the parent and all it's sub-tasks are not in the same selection and it prevents me from archiving any tickets.

Without purchasing plugins (as we'll not do this often) is the best approach to archive the parent tickets individually and then once all the parent tickets are done... do a bulk archive?

Time consuming but is that the best approach without plugins or scripts?

Thanks for viewing...

1 answer

0 votes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 05, 2023

Hi @Kelly Hawke ,


You can remove the 1000 limitation but should do so with caution.


Another thing can be done is move all the tickets you want to archive to another project. Then just add a permission scheme with all the permissions removed. 

If you are on datacenter version of Jira, you can archive the project:

Thanks Ben.  I read about removing the 1000 limitation but I'm cautious to do so.  

The tickets should stay silo'd in their respective projects.  Although I like that idea!!!  It has merit.  I may think more about that suggestion!!!

Like Benjamin likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events