Custom Field validations applying to other Issue Types and Screens

[David Thomson]

I have a custom Issue Type with a custom Screen with some Custom Fields that I put some validations on, but now input to Custom Fields are being required on different Issue Types with different Screens that do not have the Custom Fields on them, so I cannot create other Issues Types other than the one with the validated Custom Fields.

Please advise, much appreciated. Good morning

[Walter Buggenhout · Accepted solution]

Hi @David Thomson,

It depends how you implemented your validations. That would be possible via the field configuration or via workflow validators.

In both cases, it seems that your configuration is being shared across issue types. I have all reason to believe that you used workflow validators from your description, so in order to fix this, you should:

• create a copy of the workflow you modified when you implemented the new validators;
• remove the validators from that copy;
• add that copy to the workflow scheme that is linked to your project(s), making sure to associate that workflow with your other issue types
• publish the changes to your workflow scheme.

That way, you apply different workflows to your issue types, which should resolve the issue.

Hope this helps! 

[David Thomson]

I appreciate that, thank you. Not sure if it's workflow, because I can't make any Issue type in any project without the validations stopping the Issue creation.

I'm looking now for the page I did it through. I messed with both workflows and validations last night but it's all kind of a blur.

..... seems I did it in the 'default field configuration'.  I guess that's global field settings overrides everything, obviously don't want that.  I've got 4 projects that are basically the same.

• I copied the board 3 times from the first project, moved them to the other 4 projects, changed their names and filter to be applicable to their new project. Then I changed the Screen on each to the custom screen I am using (for some reason I have to do that the first time, and then afterward I can Associate Screens, otherwise I can't.)
• I replaced the workflow scheme of the other 3 with the original project workflow scheme

So I will now look into validating from the original workflow scheme unless I hear back otherwise, thank you

[Walter Buggenhout]

Aha, well ...

Because you mentioned validators I made the assumption that you updated your workflow. That turns out to be a wrong assumption.

However, field configurations can be used in the same way. Copy you default field configuration and - yet again - adjust the copy so you end up with a restricted configuration and one without the restrictions.

As soon as you have a second field configuration, you will notice that you can now edit the field configuration scheme that your project(s) is/are using. You will now be able to associate different field configurations with different issue types. And - similar to my first suggestion - you should then be able to differentiate between different issue types.

On a final side note: field configurations are less flexible than workflow validators. As you have noticed, making a field read only in a field configuration is a hard stop across every project using that field. Workflow validators apply to transitions, so they allow you to make a field required only at a certain step in your workflow. Keep that in mind for making the most feasible choice for what you are trying to accomplish!

[David Thomson]

I appreciate that, thank you. I'll watch some workflow videos now because the concept is still grey and will proceed from there based on your recommendations