-
Suggestion
-
Resolution: Timed out
-
1
-
Summary:
Due to the nature of our business, we have a corporate policy that only application administrators can make configuration changes in our production environment. As a result, we do not allow JWM project admins to make project config changes in production.
Request:
We need a systemic way to allow JWM project admins to manage access and automations while restricting them from updating project config changes.
Expected Behavior:
- Allow admins of JWM projects to continue:
- Manage access to their project
- Create / update Jira automations specific to their project
- Disallow admins of JWM projects from being able to:
- Make project configuration changes to (workflows, screens, fields, issuetypes, etc)
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management