It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I give a user permission to delete bugs and tasks without giving them Admin rights

I have Project Managers who run implementation projects in our JIRA application. As requirements change over  during the early stages of a project, they wish to be able to delete tasks that are no longer relevant. Currently only users with admin rights have access to the Delete function. Can I give these users the ability to delete issues without giving them full admin rights to our entire JIRA platform?

14 answers

24 votes

Hi Richard,

Please follow the steps below:

  • Login to JIRA as administrator
  • Click on Cogwheel icon
  • Click on Projects
  • Select the project you need
  • Click on Permissions (left menu)
  • Click on Actions button
  • Select Edit permissions
  • Search for 'Delete issues' permission, then click on 'add' next to it
  • There you may add the group or user that should have the permission

Hope this works for you.

Thanks and regards,
Paula Silveira

Great ..works well

Like Chandresh Khambhayata likes this

not working for me

Like # people like this

Same here, these instructions don't match up with the current UI.

 

It's as though up-to-date documentation, rather than outdated chat logs, would be super helpful.

Like # people like this

It is 5 years old.  I'd suggest looking at the current docs instead of looking at old forum posts.

(I keep asking to have old conversations like this shut down so people are encouraged to look in better places)

Like # people like this

This is the first thing Google returns when searched. Perhaps Atlassian should do a better job allowing search engines to index their help files?

Like # people like this

If nothing works, there is one simple way to do this

  1. Create a clone of this project
  2. Move all the tasks from the original to the temp project
  3. Delete the temp project
  4. :cool:

Or, better, amend the permissions as above.

There is a Permission Helper menu option:

Click on JIRA Icon in far upper left

Click on JIRA settings in menu tab

Click on System in next menu tab

Scroll down to Admin Helper, Click Permission Helper

Enter the info of the person and project you want to grant administrator permissions to

Follow the link and instructions of how to grant access

 

* For JIRA developers, make this feature much more intuitive to access from a project board or other.

 

 

Important to highlight that the Permission Helper does not override settings defined by the Permission Scheme (which applies to projects configured in the system)

So what the hell is the purpose of going to https://admin.atlassian.com/ then clicking on Product Access and then giving people access to Administration if that ISN'T REALLY ADMINISTRATION?? oi vey

Deleting issues is not a administration action, changing permissions is.

Yes it is.  It clearly states that "delete issue" is a project permission, and you don't need to give Jira admin rights to people if you want to let them delete.

Could you have another look at the line that covers "delete issue" and the title of the section it is in?

Can you link where you are seeing that, please? I HAD to make my user a JIRA admin before it would let them delete issues. The permission helper said the EXACT SAME THING and only when I made them an admin would it it allow them to delete. I'm just stating observations. 

Note: I accidentally linked the JIRA Service Desk documentation, but I meant to link this: https://confluence.atlassian.com/jirasoftwarecloud/overview-of-permissions-in-next-gen-projects-959283605.html

In the permissions matrix, you can clearly see that "Delete Issues" is an Administrator action and not able to be done by Member or Viewer roles.

In the doc you already linked to - the "delete issue" is in the project permissions.

However, you're absolutely right and really I should have thought of this.  So I offer you a complete apology for going down totally the wrong route.  Next-gen projects do not use permission schemes the same way all the other project types do.  Only admins can delete from Next-gen projects.

Like blair.gemmer likes this

Ah that explains it, I was utterly confused by the documentation because I didn't think about the differences that the NextGen has brought upon us haha! Thanks for your help!

After creating a Jira project, you must to ensure to add the members and set their permission in the project settings. The default Jira setting allows any members to add tasks, and create sprints in the new board even though I had not added any members. I was erroneous using the board, add issues and creating sprints without being a member of the project. So when I tried to delete an issue (a test issue by the way) it didn't allow me, even though I'm the Site Administrator. So I spent an entire work the reading forums to figure it out how the permission system works, when my problem was only to add the member in the project and set myself as the administrator, so I can have the "luxury"of deleting an issue.

1 vote

You've got two good answers already, but I'd like to add a note of warning.  Delete issue in JIRA really is delete.

No waste bins, undo, recall, rollback - if you delete an issue, it has passed on. It is no more.  It has ceased to be.  It has expired, it is pushing up the daisies. It's kicked the bucket, 'shuffled off its mortal coil, run down the curtain and joined the choir invisible.  You can only get them back from your backups.  

And hence, I always always always advise people to not allow issue delete to anyone other than a tiny handful of admins who can be trusted to delete after careful consideration (if that.  In some places it's a criminal offence to use delete)

Or:
The patient is not more
Elvis has left the building

Like Avneesh Singhal likes this
1 vote
Joe Pitt Community Leader Sep 14, 2017

This forum is full of people begging for ways to restore an issue they accidentally deleted. As Nic said don't allow deletes. I use a resolution of Deleted that is automatically set in a transition only the project lead can execute and requires a reason from a select list (entered in error, OBE, Other) and explanation text. 

Please update the user guide, it becomes very old. It's very difficult to get any help from this old article.

You must access the Permission Scheme used by the project and edit the permissions you want. If you've never changed anything related do permission schemes, then you should see this: https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions#ManagingProjectPermissions-PermissionSchemes

The steps given by Paula Silveria, don't seem to apply any more. This is 2018, and it seems like the UI has changed?

It has, a lot.

The principles are identical though, it's just the exactly "what to click" that has changed.  The things to click are all there, just maybe in different places.

Like Jessica Guerra likes this

Yeah, annoying that these articles aren't updated or archived when they are old. It's so hard to find any help on this knowledgebase

Like # people like this

I want to delete issues but I cannot find Permissions on the left menu and I am a Site Administrator.  Any help you can provide?

Are you also a Jira administrator?  Site admin does not have to grant you that.

Yes, I am a Jira and BitBucket Administrator. Cant find the Permission option... Are there different levels of Admin, by any chance?

I am a project lead and I can't access my project settings nor delete my project issues. Why?

Because the project lead has not got admin rights in the permissions.  Talk to your admins about getting that changed.

This doesn't even make sense. What can a project lead do that the others can't? Nothing?

It makes perfect sense to grant permissions (or not) to the project lead as your organisation desires.

Some places don't care what the project lead can do differently to other users of the project, some don't want them to have much power (because they're not people who need to understand the software), others want project leads to be able to do more than other users.

Like moussa.seck likes this

i'm an admin for our jira account but I still can't delete bugs can you tell me why?

Joe Pitt Community Leader Jan 23, 2019

As other have said, it is a permission scheme setting. HOWEVER, as a couple of us have 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.

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.

Rather it links out to the place for setting the permissions that you specify are needed.

We're using the newer version of Jira and for the life of us couldn't figure out how to delete issues. We had admin permission and admin's had delete permissions. We only got the option to delete after we added ourselves as administrative issues to the project.

Please check the permission scheme to see who has delete permissions.

0 votes

I need to delete an issue and a subtask, I'm the only member AND admin of the project but still can't delete it, it does not make any sense, and I create these issues by accident, so please tell me how can I delete it

Make sure your user is an admin on the BOARD too (not just the project). Also is yours a NextGen project? There are weird permissions on that one.

0 votes

Anybody else see the irony not deleting old posts from 2014 that lead people astray inside a complaint about not being able to delete an Epic. Pretty frustrating.

0 votes

I am having an issue with my Next Gen Project where in project settings/people Role "member" could not delete an issue. i have tried to set permission from permission schema but it didnt work either. i have tried to use permission helper - it pointed out to a Permission scheme: 2020 Permission schema, but when i clicked on it, it brought me back to "settings/people"

Anyone has any clue about this?

Joe Pitt Community Leader Oct 10, 2019

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.

There are some valid reasons for deleting issues. Rather than telling people not to, can you explain, how as an admin I can do this?

I totally agree, we have our own valid reason on why we need our user to delete and totally aware of what's the consequences on giving that permission. We just need to know as an admin, how we could configure the permission. 

Joe Pitt Community Leader Oct 11, 2019

Like all permissions, it is controlled in the permission scheme. Add the user to the delete issue permission. Admins don't get any permissions not in the permission scheme. 

Like Nic Brough {Adaptavist} likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

334 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you