Using JIRA Cloud "out of the box", without any add-ons/customisations, I can think of two options:
- Put your Epics in a separate project, linked to a permission scheme in which the "Create Issues" permission is only granted to your 'epic-creators' group.
- Similar to suggestions discussed in your duplicate question: in your workflow for Epics, put a validator on the "Create" transition to restrict creation.
Unfortunately (if I'm not mistaken) there is no validator "out of the box" in JIRA Cloud that can check if a user is in a particular group. But I can suggest a pretty clunky work-around:
Use the "Permission validator" to require that the user has a project permission that would usually be for admin only, but has only minor impact. "Manage Watchers" might be a good candidate, as by default only users with the "Administrators" project role have that permission.
So, this is effectively 'hijacking' the "Manage Watchers" permission to use it to control which groups can create Epics as well as manage watchers.
Of course, the side effect is that, if you give your 'epic-creators' group this permission, they'll be able to both create Epics and manage watchers on all issues (as will people with the "administrators" project role). It will also be difficult/risky from an admin point of view. There won't be anything to indicate the "Manage watchers" permission controls Epic creation, so beware! It's up to your judgement as to whether you think these are acceptable compromises.
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.