• 310
    • 57
    • Hide
      Atlassian Update – 25 October 2018

      Hi everyone,

      Thank you for your votes and thoughts on this issue.

      We fully understand that many of you are dependent on this functionality and we are actively working on addressing the need stated in this issues.

      Kind regards,

      Jira Server Product Management

      Show
      Atlassian Update – 25 October 2018 Hi everyone, Thank you for your votes and thoughts on this issue. We fully understand that many of you are dependent on this functionality and we are actively working on addressing the need stated in this issues. Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      We would like to have the ability to archive old issues. We currently have an installation of JIRA (3.0.3) that has grown to 50,000 + issues. Out of these, about 35k are closed issues. We would like to be able to remove these issues from the database so that our installation has a smaller amount of issues. As an example, all issues that are more than 90 days old would be removed from the database, but they would still be useful for a Knowledge Base.

      To summarise, a feature that would remove or export issues (with comments) of certain age would be very useful.

            [JRASERVER-5843] Archiving Old Issues

            rporteric added a comment -

            Closing this ticket annoying since we have on on-premise server and over 1M tickets with no easy or quick way to archive the closed tickets. 

            rporteric added a comment - Closing this ticket annoying since we have on on-premise server and over 1M tickets with no easy or quick way to archive the closed tickets. 

            This project is named "Jira Server and Data Center"

            Therefore it is not correct from the Atlassian side to mark this issue as Resolved, because this condition is not met

            Pavels Avens added a comment - This project is named "Jira Server and Data Center" Therefore it is not correct from the Atlassian side to mark this issue as Resolved, because this condition is not met

            Matt Doar added a comment -

            To be fair, this issue was resolved a year ago because it was shipped. However it is only in Data Center not Server, which has annoyed many customers.

            Matt Doar added a comment - To be fair, this issue was resolved a year ago because it was shipped. However it is only in Data Center not Server, which has annoyed many customers.

            NCATS LAB added a comment -

            This was closed with no comments - no acknowledgment?  This has been open since 2005 - over a decade. It has 298 votes - But Atlassian is going to just come in and close the issue with no comment whatsoever?

            Stay classy, Atlassian.

            NCATS LAB added a comment - This was closed with no comments - no acknowledgment?  This has been open since 2005 - over a decade. It has 298 votes - But Atlassian is going to just come in and close the issue with no comment whatsoever? Stay classy, Atlassian.

            We need this functionality for our Server instance. There are >1.2m issues and background indexing takes more than 1 day! Should we really buy Data Center to have this feature? 

            Leszek Czaplis added a comment - We need this functionality for our Server instance. There are >1.2m issues and background indexing takes more than 1 day! Should we really buy Data Center to have this feature? 

            Agreed with James. Yasin and other users who are using Jira Server, this feature is very much needed in Jira Server as well to help us in maintaining more clean and tidy environment, currently we have more than 1 million issue in our instance and our of which more than 60% are closed and we would like to archive issues those are older than 5 years to reduce the pressure on JIRA.

            Kulbhushan Mayer added a comment - Agreed with James. Yasin and other users who are using Jira Server, this feature is very much needed in Jira Server as well to help us in maintaining more clean and tidy environment, currently we have more than 1 million issue in our instance and our of which more than 60% are closed and we would like to archive issues those are older than 5 years to reduce the pressure on JIRA.

            James H added a comment -

            Yassin - we already did vote for it!  I would recommend raising via "feedback for the founders" https://www.atlassian.com/company/contact/contact-ceos

            James H added a comment - Yassin - we already did vote for it!  I would recommend raising via "feedback for the founders"  https://www.atlassian.com/company/contact/contact-ceos

            Yassin added a comment -

            This is totally unfair towards your Jira Server Customers.

            How can we vote to make this feature be considered for the server version?

            Yassin added a comment - This is totally unfair towards your Jira Server Customers. How can we vote to make this feature be considered for the server version?

            I also need this for server edition as well

            Harold Wong added a comment - I also need this for server edition as well

            Matt Doar added a comment -

            I see that the differences between Data Center and Server are listed at
            https://confluence.atlassian.com/enterprise/jira-server-and-data-center-feature-comparison-953651628.html
            Project archiving is not a feature in Server. I expect that Issue archiving just followed the same product plan at Atlassian.
            When I asked about this I was told basically that the idea is that if you have enough issues to need archiving features, then you're probably big enough to consider using Data Center.

            Matt Doar added a comment - I see that the differences between Data Center and Server are listed at https://confluence.atlassian.com/enterprise/jira-server-and-data-center-feature-comparison-953651628.html Project archiving is not a feature in Server. I expect that Issue archiving just followed the same product plan at Atlassian. When I asked about this I was told basically that the idea is that if you have enough issues to need archiving features, then you're probably big enough to consider using Data Center.

              msasinowski Marcin Sasinowski
              4f86d9b1e4f1 David Alonzo
              Votes:
              298 Vote for this issue
              Watchers:
              233 Start watching this issue

                Created:
                Updated:
                Resolved: