You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Why project admins cant configure project settings such as workflows and screens
However, Jira admins can edit the settings
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.
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/).
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,
Hey @Tejasvini_Apraj It is because
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? :)