It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

created field configuration and workflow specialized for project affecting all projects Edited

have custom fields that need to be required on specific issue type.

created field scheme and screens and workflow specific to and issue type; this is for a specific special project

 when applied it worked once then all of a sudden on different issues (in different project and scheme) started requiring those fields to be filled.

What did I miss?

1 answer

0 votes

One of your admins has changed the field configuration for the project, making the fields required.

The admin did set this up to give one project the proper permissions to have these fields required in their project only.  So why did the other projects impacted. The one project has special screen and its own field configuration and its own workflow as documented in Atlassian documentation.

I suspect if you check the configuration for the projects, you will find they are using the same "Field configuration scheme" and/or the same "Field configurations".

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you