Can I deny custom fields

[Camila Gomes]

Hello everyone, 

I'm intance admin and would like to know...

Can I deny the authorization to create custom fields/workflows in "team-manage" type projects from my users?

Thanks in advance

[Trudy Claspill]

Hello @Camila Gomes 

A user that has the Administrator role in the Team Managed project will be able to create custom fields and manage the workflows of that project. You would need to remove the users from that role in each Team Managed project to restrict that functionality

If you have the global setting enabled to allow end users to create Team Managed projects then whomever creates such a project is automatically granted the Administrator role in the project the create. So you would have to monitor for creation of such projects and keep removing users from that role in newly created projects. 

But the point of Team Managed projects is to allow the team to customize them. If you don't want to allow that then why allow Team Managed projects to be created at all?

[Camila Gomes]

Hi @Trudy Claspill 

🙂

Thanks for your response. 

My wish would be to do better management/governance of fields and projects.

I have users creating fields with uppercase and lowercase letters, fields with the same context/goal (duplicity), among other cases.🙃🙃

I noticed that most of these fields are coming from projects created by teams. :/ 

[Camila Gomes]

My JQL queries are become insane 🙃🤣🤣

[Trudy Claspill]

That is a risk with Team Managed projects.

It has been my experience that if cross-project reporting is needed then it is a better practice to use Company Managed projects where the reporting elements (i.e. custom fields and workflows) can be managed by a small set of people (Jira Administrators).

A few things you can try to mitigate the problem:

1. Team Managed projects can now use Custom Fields that are defined with a Global Context, as created by Jira Administrators and typically used by Company Managed projects. Consider creating Global Context fields and working with the Team Managed  Project Administrators to replace the custom fields used in the Team Managed projects with the Global Context fields. And educate your Team Managed Project Admins to use Global Context fields and be more aware of the impact of proliferating custom fields.

2. Move the teams from using Team Managed projects to using Company Managed projects and disable the option that lets end users create Team Managed projects. If you are going to consider moving the teams to Company Managed projects, review this documentation:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/