nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

add properties to not allow epic creation

Mélanie Liguet

Hi,

It is possible to add a properties to authorize only admin to create Epic.

I try jira.permission.create.denied or jira.permission.create.projectrole=administrators on first transition of Epic workflow

but it is always possible to create an epic.
Is it a jira bug, or an error in my properties?

regards,

Accepted answers

Jack Brickey

Hi @Mélanie Liguet ,

Why not have a unique workflow for the epic issue type and add a validator on the create transition restricting it to a specific user or group of users.

All comments

Jack Brickey

Hi @Mélanie Liguet ,

Why not have a unique workflow for the epic issue type and add a validator on the create transition restricting it to a specific user or group of users.

Mélanie Liguet

Hi,

I have a specifique workflow for the epic issue type.
I tested to add a validator on the create transition restricting it to a specific role but the user can fill all fields on epic's creation screen.

the error message appears after the validation of the screen (click on create button)
I would like the epic not to be offered in the list of available issue types.

thanks,

Jack Brickey

If you wish to hide the issuetype you will need an addon app. If you happen to have Scriptrunner here is a reference on this topic - behaviours-restricting-issue-types

Mélanie Liguet

for information, suggestion opened on the same subject : https://jira.atlassian.com/browse/JRACLOUD-44557

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud