-
Suggestion
-
Resolution: Unresolved
-
15
-
110
-
The ability to archive is only available to premium plan users at double the cost per month. Archiving is a natural way to manage projects for small businesses that do a number of projects across many customers. Asking to archive inactive projects should be a standard feature.
Workaround
As a workaround, it is possible to hide the project from the project listing for end users through the following process (for company-managed projects):
- Create a permission scheme with all permissions set to empty (so no one would have access to it).
- Associate the projects you want to archive with this scheme.
This would make the project disappear from the project listing for end users (Jira admins and Site admins would still see the projects in the list).
In addition to that, you can also create a project category called “Archived” to associate with the selected projects. That way, the Site and Jira administrators would see projects with that category and understand they were “archived” for end users.
For further details about the categories, check our documentation: Add, assignee, and delete project categories.
- derived from
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
- relates to
-
- Closed
- mentioned in
-
Page Loading...
[JRACLOUD-77966] Ability to archive projects in Standard Plan
I totally agree that it is ridiculous not having this functionality and we are certainly not paying extra to be able to perform a basic function.
To get round this I have created another permission for a limited few, called it archived and changed all projects not in use to this permission.
Majority of our users can no longer see these projects but if require access to view details from an old project, I add them to the permission group temporarilly.
It might help some people although not the best solution
It's such a basic feature for any paid-for plan state. At present, we will effectively have to double our monthly payment for the entire team to access this one obvious function, which is not something we're willing to do.
We will continue to research alternatives to Atlassian, which is a shame as we're largely happy with all other aspects over the past near-decade. But we've reached a limitation that needs a solution.
Assuming non archived projects are included in auto re-indexing, imagine all that cloud transaction bandwidth that could be saved if this was a standard feature 
I would love to see this included in the Standard Plan. The ability to archive old projects should not be gated as a "premium" feature. No reason why this shouldn't be included in a standard plan.
+1 I also believe that as Jira users, we are supposed to use the Platform as much as possible which includes creating content (projects, tickets, data, etc.)
The more content we create, we need to have an easy way to navigate through it which should be a standard functionality allowing you to see your achievements [what initiatives have been closed, which are the active ones, etc.]
We recently migrated from Assist/HALP and had the ability to archive a queue. The ability to archive queues (Projects) after moving to JSM should be a standard feature and including (no pun intended) on the standard pricing plan.
Yeah agreed. Congratulations Atlassian, you've lost $10,000 annual spend from us because of this, and we've migrated to Azure Devops. Its a BASIC feature.
Unfortunately this is a great example of the economics of Atlassian changing from being yesterday's challenger to the behemoths of IT, to being one of the behemoths of IT and just looking to squeeze dollars in every way. Still have some great products, but this sort of thing is not a good look - making it harder to use your tools without paying for basic functionality.