You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I want to delete sub-task in Jira but I don't have the rights to do so .... The administrator says that if I get the rights to delete sub-tasks I will also be able to delete epics and other stuff and this will create problems for audits and stuff ... Is there a way to get authorization to only delete the sub tasks and nothing else ?
Hello,
It is not possible out of the box. Your Jira Administrator is correct.
So there is no workaround for this ? When you say out of the box do you mean that it could be done using some sort of extension ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes. don't delete stuff...bad idea. Simply move to Done and use the Resolution to indicate "won't do", "unnecessary" or whatever resolution value makes sense to you. Talk to your admin about adding a resolution code to meet these needs.
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.
Agree with Jack - we NEVER delete tickets. We use the status of Discarded with a resolution of Obsolete if the issue was never worked on (never left Backlog). Or we use Aborted, also with resolution of Obsolete, if the issue was started but it was decided it was not going to be done.
We use those even if it is a duplicate issue or a mistake of even creating it.
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.
The technical answer is that it is actually possible to do this, but
a) It's horrible to set up and maintain, and only works for certain types of project. You have to have at least two workflows in every project, and one of those workflows has to have every step edited, and every time an admin adds a new step they need to remember to add a workflow property that says "delete not possible"
b) I am going to repeat what the others have said - do not delete issues, it *will* hurt you, badly.
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.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.