Bump
No archiving yet?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Adding as another voice for this feature...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any news about project archiving?
I'm evaluating to move to another tool for agile development....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is available now with premium access. Also on next-gen project the issues auto archive after 14 days closed or done. I would check but it is ready. I don't think its ready for Service desk yet though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Coudn't believe it's a "premium" feature. just remove the project from the project list. You can easily do it with hide/show thing feature, it's a wa btw. Not changing permissions imo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From what I know the next-gen projects you will be able to but not the classic. But there are some work arounds. For service desk I build our first service desk HD. Then when we started to need to archive I build another one called HDA and I put all the issuetypes, screens, custom fields etc and associated them to HDA from HD. This allowed to make an automation to send these issues to that other archive project, Then set it for read only. This is what I have done. There are other options for security levels also.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I´m still waiting this feature on Cloud version. :-(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm really missing this feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jason Maye @Gilles FREGONESE @Jay Sayers @Kevin Campbell @Garry Partington @Eric Veal @Clayton Mathis @Hamit Gurakar @Noel Rocha
We are actively working on this now per my other response however we are looking to speak to as many people as we can to understand the deeper level use cases beyond just hiding projects.
As part of that work we may define requirements that will can ship to Standard and Premium if I can get your help. So book some time in my calendar https://calendly.com/jira-software/meeting let's chat so I can better understand your perspective here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ben Jackson not being funny but what information do you still need to get from us it has been 16 years we have been asking for this feature if you don't have all the information after 16 years what the hell have you been doing it doesn't take 16 years to learn the public want to be able to achieve a project so it is hidden from everyone but the site admins of the site.
This is actually the least unfunniest joke going you really need a competitor that is about to overtake you in revenue and users so you have the kick up the ass the actually start implementing features the public has been asking for and not waiting over a decade to add it in think about how many project people will have after 16 years of working with Jira they will have 100's this service is unacceptable and I am sure I am not the only one to agree that your customer service is piss poor when it comes to requested features.
please point me to a ticket that was requested by the public and implemented i am curious in how many more years i have to wait for the most basic and mandatory feature
your's sincerely
Many pissed off Atlassian customers (i may have written this but 1000's of people are thinking this)
I know this thread was created on in 2018 but this is not the only thread on this feature there is at least 5 that i have found the earliest one going back to 2003 and no doubt this was requested before then
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Corey_Tabb the Permission based solution has been available for many years, and we have been upfront that nothing beyond that was officially on our roadmap.
That being said I understand that is not a full solution and acknowledge this feature request has been around for a frustratingly long period of time.
We are looking at this now. You ask what more feedback do I need? 90% of the current feedback (I have read 160+ comments) can be categorised as 'I'd like to be able to hide projects'. This is the simplest and clearest use case.
We'd like to delve into the 2nd and 3rd order use cases to fully understand the needs which is why I'm inviting people to book time to speak with us directly. So far I have conducted nearly a dozen interviews on this subject and learned a great deal about the dimensions of Archiving beyond that simple use case.
I also mentioned above that with these discussion we may identify enough use cases that allow our team to deliver archiving into standard and premium editions.
Happy to chat with you on your use cases :) and maybe any other areas of Jira you'd like us to work on. Ben
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd like to be able to hide projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
well if people want them hidden and people want them achieved how about you introduce the archive part of it and people can use that as to hide projects and also I don't get why hiding projects is a high priority then archive you can already hide projects with the security issue schema you just make security groups for users to only see certain projects rather then wasting time on coding for a hidden function you should create documentation in how to hide a project using the security.
also, most of these people that comment saying they want to hide a project are not very technical users I am sure 90% of them that say they want to hide projects mean archive them there is no difference from hiding a project and archiving a project they get the same end goal of them being hidden to all normal users but Admins can still see them.
and if users only want people to see certain projects and tickets and the rest hidden then you already have a feature that does this the security permissions. over 10 years is outrageous for an archive feature to be added to Jira so you telling me out of all the businesses that use Jira they would rather have a hidden feature implemented in first??
I'm sorry but that is complete bullshit so you're telling me the company's of the likes of 3M would just want to hide project instead of archiving them.
also doesn't make sense for users to be going on an archive chat to say they want a hidden feature this just screams to me that you completely miss understood the people need user comments on an archive project thread saying I want to hide a project (this is the same as archiving a project is it not?
what's the difference between hiding a project to archiving it also who are you hiding it from just one user all the user's everyone but the admins???
all these questions arise from I want to hide projects so those comments shouldn't even be taken on board if people want to just hide from certain users they should make a different comment thread that relates to what they want not filling up threads like this with crap and making this function get pushed further down the list.
so can I just ask what do you do with old projects then as Atlassian is a huge company I am sure you have lots of completed projects that you would like to keep the data for but not see on a daily basis of all your projects so what do they do or do they not use Jira do they use an alternative that has this functionality introduced already or do you just delete the project once it's done( i know this is a no as no company DELETES data?
I look forward to hearing what Atlassian's uses and does with it's complete projects
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This needs doing ASAP. Most urgently required feature in Jira. Too busy developing Next Gen whilst stripping away features.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Adam Rawlinson thanks for your post. Archiving has never been available in cloud and only relatively recently added in Data Center edition.
We are actively working on this now per my other response however we are looking to speak to as many people as we can to understand the deeper level use cases beyond just hiding projects.
As part of that work we may define requirements that will can ship to Standard and Premium if I can get your help. So book some time in my calendar https://calendly.com/jira-software/meeting let's chat so I can better understand your perspective here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Marre d'Atlassian JIRA cloud, la fonctionnalité d'archivage manque cruellement
:(:(:(
je vais finir par trouver une autre solution Plus complète et moins chère aussi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is so ridiculous. It's such a simple thing to implement. Just do it and stop the madness.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this really still not possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Subscribing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.