Hi there,
I am in quite the dilemma. I have multiple Jira projects setup and now my latest for some unknown reason people cannot delete tickets.
I already made my way to the "project permissions" and compared my newest project (the one I have trouble with) and an older one.
Old project
here "any logged in user" is selected
New Project
Here I cannot see the "any logged in user". (1st screenshot). If I go on edit I also cannot seem to select it from the list (2nd screenshot). Any idea why?
well first off... Do not do that! Deleting issues is almost always a bad idea. Giving everyone a gun is most certainly a bad idea.
off of my soap box...
looking at your images you are on the right track in that you would use "any logged in user" for each project - project settings > permissions > delete issues. I'm not immediately familiar w/ your final image here. Maybe something that has changed that I have not come across. But you could use "Application access" I would think.
Hi @lisa
Agreeing with Jack, an alternative many use rather than Delete is to create an Abandoned indicator (custom field, status, label, etc.) Mark things as abandoned rather than delete them, and then update board filters to not show abandoned issues.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Like @Jack Brickey said Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.
Deleting issues destroys historical data. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.
The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.
None of my users have delete permission.
If you insist on deleting issues you need the delete issue permission
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.
I agree with @Jack Brickey that granting Delete issues permission should best be restricted, as it can lead to a permanent loss of information.
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.