Issue Details (XML | Word | Printable)

Key: JRA-1431
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Patrick Peak
Votes: 38
Watchers: 17
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Create a separate permission for Create New project.

Created: 12/Mar/03 01:24 PM   Updated: 04/Mar/10 06:50 AM
Component/s: Permissions Security, Project Management
Affects Version/s: 2.1 Enterprise
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Part
 

Participants: Achim Uhrig, Alexey Rashevsky, Anton Mazkovoi [Atlassian], Benjamin Blakely, Giles Hinchliff, henry, John Young, Kevin Wilson, Kutsal Berberoglu, Michael Parmeley, Mikey Judd, Neal Applebaum, Patrick Peak, R Gopi, Richard Hansson, Roman Glebsky and Steve Warin
Since last comment: 1 week ago
Labels:
Support reference count: 5


 Description  « Hide

Currently, I need to give my project manager the jira-administor permission in order for him to create new projects. Unfortunately, this opens up the possibly of him doing other stuff, like changing the mail server. Not that he would, but when you give permissions...

Suggestion: Make Create New Project a separate global level permission.



Kevin Wilson added a comment - 21/Jul/03 05:06 PM

It would be nice if the pro version could have this feature as well.


Kevin Wilson added a comment - 02/Nov/05 03:05 PM

This should be extended to create a poweruser permission level. This level would allow superusers to assign powerusers the permission schemes they can operate under. This scenario allows the powerusers to fully operate as a data administrator thereby alleviating system admins from having to do data administration as is the case now.


John Young added a comment - 12/Feb/07 06:23 AM

I'd like to add my vote to this issue. I work in a large company, and we don't want to proliferate Big-Chair access all over the place. But we DO want lots of people to be able to create new projects. Is this a planned feature?


Giles Hinchliff added a comment - 18/Mar/07 11:52 PM

This would be a really useful feature


Neal Applebaum added a comment - 19/Mar/07 10:38 AM

This would be tricky, I think. Because obviously they would need the ability to edit the project to set schemes and so forth, and the current interface allows editing existing schemes too.


Mikey Judd added a comment - 26/Nov/07 02:33 PM

To me, JIRA Administrators have access rights to everything while Project Administrators have the abilities to create/delete/edit projects. I also believe that a Project Administrator should be able to select schemes, just not edit them.


Michael Parmeley added a comment - 13/Nov/08 02:08 PM

I would love to see this added. I have people I want to be able to create projects but I don't want to be able to edit various schemes.

It would be nice to have a permission that allows a user to create projects and assign existing schemes to them but not edit the schemes.

On project creation the creating user should be project lead.


Kutsal Berberoglu added a comment - 26/Nov/08 08:50 AM

I disagree with the priority (set to minor right now) of this.

We'd like to not grant jira-administrators privilege to project/technical managers who only need to be able to create projects and not necessarily see the rest of the administrative controls.

This was reported in 2003. Are you guys planning on implementing this anytime??


Anton Mazkovoi [Atlassian] added a comment - 28/Nov/08 12:05 AM

Hi,

Due to the large number of other popular requests we currently have no concrete plans to implement this feature.


Alexey Rashevsky added a comment - 21/May/09 07:29 AM - edited

In my opinion this is one of the basic features and must be implemented.
Even simple free CMS systems have possibilities to make several "admin" levels and specify what administration features will be available for particular user/group.
Why I should give administrator rights to the PM? Sounds really irrational.


henry added a comment - 30/Jul/09 09:47 PM

We have met that problem, there are many project need to be created by JIRA administrator. we also hope a seperate permission of create project , which can be assigned to project leader.


Richard Hansson added a comment - 11/Aug/09 08:11 AM

I have the same problem. This sounds like basics to me, why is there not any solution for it yet?


Steve Warin added a comment - 16/Oct/09 09:47 AM

I agree. I'm new to Jira, and just started setting up Jira 4 for use by my organisation. I have wasted a good bit of time looking for a way to allow project managers to add projects without giving them all the other permissions associated with system administrators, thinking "it must be there somewhere, why can't I find it?". I'm absolutely gobsmacked that this was first suggested six and a half years ago and still (even after a new major release) it has not been implemented. Surely it can't be that hard to implement?


Benjamin Blakely added a comment - 11/Dec/09 04:51 PM

Adding my vote for this feature. No need for non-sysadmins to have sysadmin level rights just to create a project.


Roman Glebsky added a comment - 24/Dec/09 12:58 AM

About six years Atlassian can't implement this simple feature...
So, I think Atlassian don't know about working with many small projects. It's bad, very bad...


R Gopi added a comment - 24/Jan/10 09:19 AM

Adding my vote for this feature. we need a role for creating a project.


Achim Uhrig added a comment - 04/Mar/10 06:50 AM

Addning my vote here. I don´t want to give administrator-rights to enable this function for users.