Product Admin vs. Global admin for Company Managed Projects

[Gwen Coveny]

Newbie here: In Jira Work Management, can a Product Admin initiate Company Managed Projects and configure issues, settings, automations, etc. within those projects?

Company Managed projects appear to have some features not present in Team Managed such as the ability to update the project's description as needed, and possibly the ability to copy/duplicate issues from a previous project (to be determined...)

Do you need to be a Global Admin or a Jira Work Mgmt Product Admin to create/configure a Company Managed project?

If Global Admin, is it possible to have more than one Global Admin in a company instance?

Thanks!

[Trudy Claspill · Accepted solution]

Hello @Gwen Coveny 

To create Company Managed projects and manage the configuration elements (issue types, fields, workflows, etc.) requires that a user be a Jira Administrator. Within the Jira product itself there is an area for configuring Global Permissions. Listed there is a permission for Administer Jira. A user has to have that permission in order to be a Jira Administrator with access to create and manage the configuration for all Company Managed projects, as well as access to other Global configuration options that apply to the entire Jira instance.

Within a Company Managed project there are permissions assigned, and one of those is Administer Projects. A user with that permission in a specific Company Managed projects has some limited administration options for that specific project, such as changing the project's description. They generally don't have the ability to create custom fields, change the issue types, etc.

More than one person can be granted each of these permissions.

[Gwen Coveny]

@Trudy Claspill - Thanks very much for your response.

On a related topic, do you know if it's possible for a Global Admin to add a card to the board of a Company Managed project? It's easy to do on a Team-Managed project but I don't see the plus symbol (highlighted below), within a test Company Managed Project that I initiated as a Global Admin.

 

[Trudy Claspill]

Let's clarify some terminology.

A "card" in a board is equivalent to an issue.  The item in your image that includes "SP2-1" on it is a card/issue on that board.

The + button that you have highlighted is for adding a Column to a the board.

In a board a Column maps to a Status that can be assigned to issues.

In Team Managed projects the button is present because the workflow and statuses of such a project can be administered by anybody with admin access, and those changes apply only to that project and don't affect any other project.

With Company Managed JWM projects the workflow can be managed only by a Jira Administrator, and it is not managed directly in the project. Workflows may be shared between multiple Company Managed projects, so the management of those workflows is separated from the direct management of the project. 

For more information about managing workflows in JWM projects refer to this resource:

https://support.atlassian.com/jira-work-management/docs/understand-project-workflows/

...and the topic therein relating to Company Managed projects.

[Gwen Coveny]

@Trudy Claspill - Thanks for clarifying on the terminology and workflow differences between the project types. I was looking to add a column to the board of a test Company Managed project as a global admin, and was incorrectly referring to the column as a card. The resource you sent is very helpful. Much appreciated!

[Oshimarr Myhan]

You're Welcome