How to restrict editing of certain issue types to specific groups?

[Ashley Honeycutt]

Is there a sustainable way to configure a project so that all logged in users can edit sub-tasks in a project, but only users in a particular group can edit the parent-level issues?

[Joe Pitt · Accepted solution]

I don't allow deleting issues and have a Deleted and Cancelled resolutions for those issues that would be deleted.  If you use JIRA for change control you would want something for those issues. I suggest using the workflow property to include just those resolutions you want the user to select from. Using the include function avoids needing to update the workflow if you add more resolutions. 

https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html 

[Nic Brough -Adaptavist- · Accepted solution]

I'd recommend using any resolutions that describe why you have closed an issue.  They're there to fit your purposes, and the language you use.  The default ones, fixed, won't fix, etc are not a bad starting point (I usually add "duplicate" quite quickly though), but the real answer should be driven by your reporting needs.  How do you want to report on "why did we close issues"?

[Gezim Shehu [Communardo] · Accepted solution]

Hi,

Really depends on what you use JIRA for.

If standard SDLC (Software Development Lifecycle) I think the already built ins are enough.

[Ender Akgün]

Thanks,

I think these resolutions are enough in SDLC: "Fixed", "Unfixed", "Cancelled" , "Rejected", "Won't Do",  and "Duplicate".