Convert Team to Company-Managed Project; if Issue Types are common will disrupt Company workflows?

[Philip Marvil]

I have experience with Company-managed Jira Projects in my past.  When I joined a new organization and had a look through existing Projects, I see that there are very simple, common workflows for common Issue types (User Story, Defects, Epics) that don't meet my needs.  

To be safe, I created a Team-Managed Project, but I'm finding the functionality very limiting.  I did set up multi-status, specific workflows for two Issue Types (User Story and Defect) that do meet my needs.   My workflows are very different than the simple ones in the company-managed projects for these Issue types.    

Can I convert my Team-Managed Project to a Company-Managed Project, carrying over the workflows I want to use for these common Issue Types without in any way affecting all other Company-Managed Projects?  

The only reason I chose Team-managed to begin with is that I didn't want to risk messing up others' existing Company-Managed Projects.  

Thanks for any advice.  

[Mark Segall · Accepted solution]

Hi @Philip Marvil and welcome to the community!

As long as you're not creating a project from a shared configuration, when you create a new company managed project, the following schemes will be specific to that project:

• Issue Type
• Workflow
• Issue Type Screen

You can tell by navigating to Project Settings >> Summary.   The names of those three schemes will be prefaced with the Project Key.  For example:

XXXX: Software Simplified Workflow Scheme

If you see this, you can proceed with confidence that you won't disrupt other projects.  If you do not see something similar, you could create custom schemes by navigating to System >> Issues.  You'd just need to switch the existing schemes once your new schemes are configured.

Note - There are three schemes that are adopted from the system:

• Field Configuration
• Permissions
• Notifications

[Philip Marvil]

Thank you, @Mark Segall  I was really struggling to get a clear answer on this from Atlassian's documentation to be honest.  

Since I have only been a User in my past (including Advanced Roadmaps) and not an Admin, I'm not sure what I'll see during Project setup.   May I ask this follow-up question?   Will I be prompted during setup of a company-managed project to choose whether I want a shared configuration or not?  I'm assuming I just say, "no I don't want a shared configuration"? 

Also, from a permissions point of view, is there a way I can have admin privilege for just my Project and be "firewalled" from everyone else's?   Again, being new here, I really don't want to mess anything up for anyone else, but I already know that to use Jira proficiently, I'm necessarily going to need to make changes to some basics like addition of a few custom fields, page layouts for Issues, addition of other Issue Types, and Workflows.  Is there some permission type other than global Admin I can ask our true Admin to grant me in order to allow me control over these for my Project? 

I really appreciate your advice. 

[Mark Segall]

It's my pleasure to help out. To answer your questions...

Will I be prompted during setup of a company-managed project to choose whether I want a shared configuration or not?  I'm assuming I just say, "no I don't want a shared configuration"? 

During the setup, you'll see a checkbox to use a shared configuration.  Just leave it unchecked and it will automatically set the schemes as outlined above.

Also, from a permissions point of view, is there a way I can have admin privilege for just my Project and be "firewalled" from everyone else's?

Yes.  You would need to create a new permission scheme from Settings >> Issues >> Permission Schemes (Recommend copying one of the existing as a starting point rather than creating a new one from scratch).

Is there some permission type other than global Admin I can ask our true Admin to grant me in order to allow me control over these for my Project?

For the types of things you wish to do, you'll need to be a member of the Jira admin group.  A project admin will not be able to make system level configuration changes which includes creating/modifying anything under Project Settings >> Summary.