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

[Danyal Iqbal]

So I guess Im asking can Jira permissions levels be set for individual Fields in a project - personally I don't believe it is possible but I thought I'd ask to make sure :-)

No not per se, but consider the following workaround:

* Remove the field from the edit screen .

* Create a global transition "set field A" and add "field A" to the screen associated with this transition.

* Set condition on this transition to allow only a specific group to make this transition and add your users to this group.

neat?