# Archive Ticket **URL:** \ **Category:** Customer Feedback Tool\ **Created:** [July 17, 2018, 7:34pm UTC](https://community.hubspot.com/t/archive-ticket/9491 "2018-07-17T19:34:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kelseyhalverson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kelseyhalverson/32/44875_2.png) [@kelseyhalverson](https://community.hubspot.com/u/kelseyhalverson)\ **Post date:** [July 17, 2018, 7:34pm UTC](https://community.hubspot.com/t/archive-ticket/9491/1 "2018-07-17T19:34:09Z")
Our agency uses HubSpot Tickets to handle our internal projects between departments, similar to a scrum board or trello. The issue we have is that we don’t ever want to delete tickets permanently, however we have to move tickets off our pipeline once they’re completed otherwise it causes A TON of clutter. ---
**Author:** ![MFrankJohnson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mfrankjohnson/32/22490_2.png) [@MFrankJohnson](https://community.hubspot.com/u/MFrankJohnson)\ **Post date:** [July 19, 2018, 12:22pm UTC](https://community.hubspot.com/t/archive-ticket/9491/2 "2018-07-19T12:22:08Z")
\*\* ![_hubspot-button-accept-as-solution-gif-v00.gif](https://d2qpr2jzcazej7.cloudfront.net/original/3X/2/8/280f73986e0517a27aa4068d06718dbcda1a42a2.gif) \*\* **Help other HubSpot searchers find this post quickly by accepting the solution** **Excellent suggestion @kelseyhalverson. You may wish to add to a new or existing thread in [HubSpot Ideas](https://community.hubspot.com/t5/custom/page/page-id/ideaslandingpage).** You’ll typically get much more traction from the HubSpot Community AND the Ideas Forum is where HubSpot Product Teams monitor suggestions for popularity -- i.e., VOTES! 🙂 Does that help answer your question? If so, remember to accept this ‘solution’ so other searchers will find it. Best, Frank * * * * * * ![hubspot-solutions-signature-mfrankjohnson-v03.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/7/2/72932fb841989f2b32ea0f23364863c18e73a7ee.png) * * * [www.MFrankJohnson.com](https://www.mfrankjohnson.com/?utm_source=hs-forum) ---
**Author:** ![Wholesale-Solar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wholesale-solar/32/2555_2.png) [@Wholesale-Solar](https://community.hubspot.com/u/Wholesale-Solar)\ **Post date:** [September 6, 2018, 3:39pm UTC](https://community.hubspot.com/t/archive-ticket/9491/3 "2018-09-06T15:39:20Z")
I agree, there should be some standard archiving methodology to get stuff to drop off of boards. For now… 1. Add an Archived stage to your pipelines 2. Setup a tickets workflow 3. Enrollment Trigger Pipeline is any of Tech Support and Ticket status is any of Done (Tech Support) and Close date is more than 1 day ago THEN Set a property value Set ticket property Ticket status of the associated ticket to “Archived” 4. The you can filter your board/tables to exclude Archived ---
**Author:** ![JamesCousins](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jamescousins/32/1268_2.png) [@JamesCousins](https://community.hubspot.com/u/JamesCousins)\ **Post date:** [January 23, 2019, 6:33pm UTC](https://community.hubspot.com/t/archive-ticket/9491/4 "2019-01-23T18:33:57Z")
Hi there Wholesale-Solar, Thanks for this answer. I’m just getting started setting up the ticketing side and it’s nice to have this insight ahead of time. I think I’ll add in an “archived” stage right out of the gates. James ---
**Author:** ![BubblePPM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bubbleppm/32/43030_2.png) [@BubblePPM](https://community.hubspot.com/u/BubblePPM)\ **Post date:** [February 26, 2020, 10:33am UTC](https://community.hubspot.com/t/archive-ticket/9491/5 "2020-02-26T10:33:38Z")
We’ve found it easier to create a workflow that places the ticket in a separate archive pipeline with a single stage - saves messing with filters and creating unnecessary columns in the main pipeline: Ticket enrolment trigger: Ticket status is Closed and Last modified date has not been updated in the last 2 days Set property value Set ticket property pipeline and status to Archived (Archive pipeline) ---
**Author:** ![SSmith184](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@SSmith184](https://community.hubspot.com/u/SSmith184)\ **Post date:** [April 30, 2024, 1:05pm UTC](https://community.hubspot.com/t/archive-ticket/9491/6 "2024-04-30T13:05:10Z")
How do you handle preventing those Archived Tickets from reopening if a customer replies? Also what about reporting? Do you just combine reporting off your Archive Pipeline and “Active” Pipeline? ---
**Author:** ![LJam23](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ljam23/32/198752_2.png) [@LJam23](https://community.hubspot.com/u/LJam23)\ **Post date:** [July 5, 2023, 9:08pm UTC](https://community.hubspot.com/t/archive-ticket/9491/7 "2023-07-05T21:08:24Z")
Agreed, a built-in solution for archiving tickets is a must. Coming from Zendesk, we’re used to tickets going from solved to closed automatically after a few days, then automatically archiving in a separate searchable area after that. The fact that closed tickets stay on a pipeline indefinitely unless someone uses a filter or deletes the tickets is not ideal.