We want to limit who has access to create an Initiative within a project?

[Neil Wills]

We want to limit who has access to create an Initiative within a project?

It makes sense to allow the general team to create Story, Tasks, etc

We want to limit the Initiative issue type creation to a set of individuals.

Goal:  day-to-day the scrum team do not create initiatives or any issue types higher than an epic, so when the create issue lists those at the top of their issue type list when they select create issue that can be frustrating for them to have to go down a list top select bug, story, task

I do not want product getting in the way of the scrum team.

My organization is not ready to use another project for strategy, planning, portfolio issue types so I am creating them in the same project

[Fabio Racobaldo _Herzum_]

Hi @Neil Wills ,

in order to limit Initiative creation you should define a specific workflow and assign it just to initiative in the project workflow scheme. That specific worflow should have a validator on creation (User Permission Validator) in order to allow creation just to a project role within a project.

Hope this helps,

Fabio

[Neil Wills]

thx