Hello,
I'm currently testing out Jira Service Management as a potential IT ticketing solution.
I created Account A using Email A (my work email address) to set up and configure a new IT service project. To test what the experience would be like for non-admin agents, I invited Email B (my personal email address) to become an agent on that project - naturally, I was prompted to create an account, so now I have Account A and (temporary) Account B.
While I'm on Account B, I have no issues navigating through the project I invited myself to as an agent. However, if I try to create my own project using Account B, I see a message that only a Jira admin can create new projects.
Obviously using my own test accounts this is no big deal, but I'm concerned about the implications if we do roll out Jira Service Management within my company. Will inviting my colleague to act as an agent on my project prevent them from creating any projects of their own? Or is there a way to do both?
Thank you.
Hello @Amira Mohamed
Welcome to the Atlassian community.
There are two types of projects that can be created - Team Managed and Company Managed.
Company Managed projects can be created only by Jira Administrators.
Team Managed projects can be created by other users if they have been granted that Global Permission.
For more information on Global Permissions refer to
https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/
If you don't grant the invited agents Jira Administrator permissions they will not be able to created the Company Managed type of Jira Service Management project. Depending on how the Global Permissions are set, they may be able to create the Team Managed type of JSM project.
For more information about Team Managed vs. Company Managed projects refer to
https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/
Company Managed projects leverage globally defined configuration and customization options that are managed by Jira Administrators.
Because of this, typically creation of Company Managed projects and the available configuration and customization options is restricted to Jira Administrators so that the proliferation of these can be managed.
For organizations where more autonomy is needed at the team level, Atlassian developed Team Managed projects. The configuration and customizations for Team Managed projects are scoped to the individual project and can be managed by the Project's Administrators. However this can impact other elements of the Jira environment because those projects can have custom fields and status values that are named identically to the same items in other TM project and similar items defined globally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.