JSM: Sandbox Development Restrictions

[Josh Drake]

Hello,

My company recently upgraded to JSM premium and is experimenting with the sandbox feature. I am curious as to why a sandbox project still locks down the "create a field" tool to only Jira administrators, as opposed to project administrators. To clarify, this is in a company-managed project.

This made me curious as to what other features the sandbox brings, as well as who has access.

Is it possible to change the access of jira-admin-specific features, such as workflow creation and issue creation, within the sandbox? I feel like the environment itself is designated for experimentation, and these access limitations hinder the applications of a sandbox.

[Walter Buggenhout]

Hi @Josh Drake,

The restriction to create fields to Jira Administrators in a company managed project is not related to sandbox vs production. This is expected behaviour in company managed projects, where most configuration is managed centrally.

Editing workflows is restricted in the same way and is also not linked to production vs sandbox. Here, there is a specific permission though, where editing a workflow can be granted to project administrators, as long as it is not shared with other projects.

Adding fields directly in a project (by a project administrator) is a feature you'd rather see in team managed projects.

Hope this helps!