HI all,
As this option doesn't exist i would like to advise and hear ideas from people that found workaround for this need.
In many cases we do not want to allow users the permission to delete.
What i do in most cases is set a status & Resolution that the issue moves to if the user would like to delete an issue. In the agile boards i update the board filter will not include issue in 'status\resolution=Removed'
Would love to hear other people thoughts about this and hear other solutions you found usefull
Thank you!
Shirley
I've seen several options, but the basic ones that work ok (sometimes combined) are
Setting the security level is my favorite.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks!
Can you explain a littlebit on how you set the security level ? on what conditions?
I Would truely like to setup a security level but i'm not sure how to work with it.
I want to maintain the deleted status and use a security level to hide these issues, not sure how can i achieve both
Thanks again
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, using both is probably slightly easier and neater.
First, you have status in the workflow for "deleted". You probably want a transition into it from all other status, and then a transition out, back to early on in the lifecycle of the issue.
With the security level, you can define a scheme that has a single line saying something like "project administrators are the only ones who can see this issue when the security level is set to 'deleted'". As you're using a workflow to the deleted status, you can use a post-function to set the security level to 'deleted' automatically as the user uses the transition, and another one to remove it when "undeleting"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the above solution doesnt work. So can i please know what i am missing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you need to explain what you mean by "doesn't work", because it works perfectly in the places I've seen it implemented.
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.
we have a subtask that i would like to hide using the issue security scheme. According to my understanding the subtask inherits the security level of its parent. So when i have assigned the issue security scheme on the subtask it does not hide from the board.
My implementation : Created issue security scheme and assigned it to role project-administrators
Created a workflow state deleted and added a post function to assign it to new issue security scheme i created
and I still see it on my board.
So i assume its the subtask that is causing the issue. Please do let me know
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
we have to assign issue security in project settings for this to occur...this was the step i missed due to which i could not get the issue security scheme working. It now works fine
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shirley,
I think, the way you done is correct workaround, there is no such option for soft delete in JIRA
Thanks,
Hemant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.