Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,522
Community Members
 
Community Events
175
Community Groups

Why project admins cant configure project settings such as workflows and screens

Why project admins cant configure project settings such as workflows and screens

However, Jira admins can edit the settings

4 answers

0 votes
Trudy Claspill Community Leader Dec 14, 2022

Hello @Tejasvini_Apraj 

Welcome to the community.

Project Administrators can configure Workflows for Team Managed projects.

For Company Managed projects, Project Administrators can configure Workflows under very specific circumstances:

- the board uses a Simplified workflow

- the workflow transitions do not include any Conditions, Validators, or Screens

Project Administrators are not permitted to modify screens, fields, or other configuration schemes of a Company Managed project as those may be shared with other projects, as noted by the other folks who have responded to your post.

Workflows and permissions schemes are shared by many projects, and when a project administrator updates one according to their needs, it will have an impact on all other projects as well. That's why two different roles available in JIRA

1-JIRA Administrator - JIRA Admin manages the complete Product for the organization.

2-Project Administrator - Project administrators manage administrative tasks for projects like board management, user and group roles, and board access.

0 votes

Hi @Tejasvini_Apraj ,

welcome to the Atlassian community!

Probably you are talking about Team-Managed projects (here a brief exaplanation about differences with Company-Managed projects https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/).

Team-managed projects

Set up and maintained by anyone on the team, team-managed projects are ideal for autonomous teams who want to control their own working processes and practices in a self-contained space. Team-managed projects have simpler project configuration and give project admins more control over set up without involving a Jira admin (unlike company-managed projects, where one is required to configure schemes and screens).

 

Hope this helps,

Fabio

Hey @Tejasvini_Apraj It is because

  1. Workflows and Screens can be shared between many projects, thus affecting not only the projects you work with
  2. JIRA permissions are set in a way that being able to configure workflows also allows you to configure things like fields and statuses
  3. It requires a lot of knowledge about the JIRA itself and about the ways of work in your organization to do the changes - that is why only JIRA admins can do this, with the assumption they are people who have enough knowledge and understanding.

How about reaching out to your JIRA administrator and asking  for a pairing session so you can get a workflow you need designed and also learn from them about the complexity of JIRA and how to handle it? :) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events