-
Suggestion
-
Resolution: Fixed
-
52
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks again for all your votes and comments on this suggestion.
In JIRA platform 7.3, we allowed project administrators to edit their project's workflows under specific conditions. Now, we're happy to announce that with JIRA 7.4, we added more fine-grained control to the Administer Projects permission, and added a few more perks for the project administrator. When granted, the Extended project administration permission will allow project administrators for the associated projects to edit the project's workflows and screens.
You can learn more about it here: https://confluence.atlassian.com/adminjira/jira-platform-releases/jira-7-4-x-platform-release-notes
As the next step, we’d like to hear your feedback about these new capabilities, and the most important features you’d like to see in the Project Level Administration moving forward.
For this purpose, we've created a new suggestion focused entirely on collecting feedback and ideas for further improvements: https://jira.atlassian.com/browse/JRASERVER-65574. We’ll use it to keep engaging with you on this topic, so please drop all your thoughts there.
To avoid having multiple suggestions about the same topic, we’re closing this one as fixed. It doesn’t mean that no further work will be done in this area, quite the opposite actually. This will help us streamline your feedback and identify some missing parts that we still need to incorporate into JIRA.
Thanks,
Jakub Lazinski
Product Manager, JIRA Server
Original request description:
As a JIRA Administrator I find it more difficult to manage JIRA configuration as my organisation grows. I need to be able to share some of my administrative powers with other people, but I do not want to give them all the management rights, because I am afraid they are going to break things. Each of the projects run in JIRA has its own manager and it would be best if I could give the configuration permissions related to the projects to the respective project managers.
- duplicates
-
JRASERVER-16437 Assigning someone to Administrator role on a specific project only does not enable him to edit roles to add developers and users to his project.
- Closed
-
JRASERVER-16801 Restrictions to User/Group Administration Console - Project Administrators may require RO access
- Closed
-
JRASERVER-32343 Be able to delegate user group administration to users
- Closed
- incorporates
-
JRASERVER-6467 Update notification scheme to allow emails to be sent off of issue priority or add ability for notification scheme turn on/off configuration via a permission that can be granted to a project administrators
- Closed
-
JRASERVER-14336 Allow project admin to manage (create and modify) users only for their project
- Closed
-
JRASERVER-42462 Allow Project Administrator to create/edit Workflow of his own project.
- Closed
-
JRASERVER-63684 Ability to disable Project level administration
- Closed
-
JRASERVER-1431 Provide a new seperate global level permission for Create New Project
- Gathering Interest
- is duplicated by
-
JRASERVER-1688 Create 'User Management' permission
- Closed
-
JRASERVER-4211 Group maintenance features for "Project Admins"
- Closed
-
JRASERVER-5749 maintenance of custom field parameters
- Closed
-
JRASERVER-10073 Enable project administrator edit project notification scheme.
- Closed
-
JRASERVER-10208 Project lead should have ability to add users to project
- Closed
-
JRASERVER-10262 Make administration more fine grained so some admin tasks can be moved to project administrator
- Closed
-
JRASERVER-11562 better Isolate administrative configuration of a project from other projects
- Closed
-
JRASERVER-12127 delegate admin tasks to the project level
- Closed
-
JRASERVER-13076 Project Administrator Role should be able to Create Custom Fields to Specific Proejcts
- Closed
-
JRASERVER-20729 Allow non-Administrators to be able to modify workflows
- Closed
-
JRASERVER-21221 It should be possible for a project admin to create or modify a "Custom Field Configuration scheme".
- Closed
-
JRASERVER-24409 As a developer or release manager I want to be able to create and manage versions in JIRA without having to be given project admin permissions
- Closed
-
JRASERVER-26163 permission to edit workflows to single person
- Closed
-
JRASERVER-26682 Project Admin Configurable Fields
- Closed
-
JRASERVER-32067 Add ability to create a new workflow for each project
- Closed
-
JRASERVER-32695 RBAC for granular control of administration section
- Closed
-
JRASERVER-34355 Separate Workflow management permission
- Closed
-
JRASERVER-34643 Jira Administator Privileges
- Closed
-
JRASERVER-34882 Allow project administrators to configure more project settings
- Closed
-
JRASERVER-36472 As a JIRA project administrator I want the ability to change my own workflow if the system admin has allowed me access to that workflow so that I am in control of my project
- Closed
-
JRASERVER-36869 Split up admin role into new specific admin roles each with their own assigned admins
- Closed
-
JRASERVER-37862 Allow creation of custom JIRA Administrator
- Closed
-
JRASERVER-43290 Global Admin Be Able To Make The Assignment On A Project Basis ?
- Closed
-
JRASERVER-43291 Global Admin Be Able To Make The Assignment On A Project Basis ?
- Closed
-
JRASERVER-45415 Separate Administrator Role and Project Management
- Closed
- is related to
-
JRASERVER-4176 Project "sub-commanders"
- Closed
-
JRASERVER-6374 admin permissions
- Closed
-
JRASERVER-7296 Add a Project creator permission for individually selected users
- Closed
-
JRASERVER-11125 JIRA 4.0 Enterprise Requirements
- Closed
-
JRASERVER-12724 New global permission "create projects" (CLONE of Project Administrator should be allowed for creating projects)
- Closed
-
JRASERVER-14718 Issue Type Schemes Available to Project Administrators
- Closed
-
JRASERVER-15863 Separate permissions granted by the "Administer Projects" Permission
- Closed
-
JRASERVER-20524 Permission to edit project role membership
- Closed
-
JRASERVER-28442 Customfields that behave like Components
- Closed
-
JRASERVER-29027 Allow Project administrators to create FishEye repo mappings
- Closed
-
JRASERVER-34015 Separate Project permissions for Version Management
- Closed
-
JRASERVER-44638 Add an "Associate" operation to Fields, Screens and Workflows
- Closed
-
JRASERVER-11884 Security Violation: Manage Project Role Membership needs a Global Permission
- Gathering Interest
-
JRASERVER-40315 Personal Projects
- Gathering Interest
-
JRASERVER-62237 Provide ability to restrict Delete Project permissions
- Gathering Interest
-
JRASERVER-64036 Ability to Configure Resolution In Workflow by Project Administrator
- Gathering Interest
-
JSWSERVER-15452 Way to disable the modification of a workflow by project admins
- Gathering Interest
- is superseded by
-
JRASERVER-65574 Feedback on Project Level Administration
- Gathering Interest
- relates to
-
JRASERVER-28184 User with Project Administrator permission not able to change Notification scheme.
- Closed
-
JRACLOUD-3156 Required: Project Group Administrator
- In Progress
-
JRASERVER-20524 Permission to edit project role membership
- Closed
-
JRASERVER-33573 Distinquish the ability to edit project membership from other admin permissions
- Closed
-
JRASERVER-35125 Option for showing project lead/project administrators on permission violation screen
- Closed
-
JRASERVER-43180 Managing Project Permissions so that project admins do not have rights to add groups in projects
- Closed
-
JRASERVER-43368 Allow 'Assignee' field to be required when 'Allow unassigned issues' is turned ON in General Configuration
- Closed
-
JRASERVER-12891 New permissions item - version maintenance (v3)
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...