How to have a field in one screen as required and in another as optional?

How to have a field in one screen as required and in another as optional?

3 answers

1 votes

In workflow screens, you can use "Field Required" validator.

Thank you. I am not sure. Maybe an example helps. I would like to have the field "due date" mandatory for tasks, but only for them. Currently I get error messages when I create other issues, even if "due date" is not assigned to the screen. I would not know how to solve this with workflow screens.

If you want to make it mandatory only for certain issuetypes, you need to look at field configurastion schemes. Not screens.

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour#SpecifyingFieldBehaviour-Managingmultiplefieldconfigurations

What are you asking can be achieved by ScriptRunner (groovy, free) or JJupin (mine, commercial, a simple scripting language) or some other plugins. There are countless plugins containing validators, conditions and postfunctions, just search to see if one suits your needs.

I maanged to solve the problem with field configuration schemes. Thank you!!!

How did you solve this with a field configuration schemes? I've been rereading the docco and I still see no way to make a field required in one screen and option in another.

Steffens solution is like this: a field configuration for tasks where due date field is required and another field configuration for all other issuetypes where it is not required.

So it is actually not in different screens but for different issue type.

Rob, could you manage with Udo's answer?

@Steffen2 if you can elaborate I would be grateful  on @Udo Brand's answer. 

 

I only want a feild to be manadatory at a Epic level 

Joe Pitt Community Champion Jul 26, 2017

Epics are an issue type so the field configuration based on different issue types is the cleanist way to go. 

Screen Shot 2017-07-26 at 14.54.38.pngCorrect me if I am wrong @Joe Pitt at the following set up under "Feild COnfiguration Schemes"  so if I add an issue type  Epic and ammend as necessary that will solve my problem?

 

Joe Pitt Community Champion Jul 26, 2017

Yes. I usually have a different field configuration for each issue type in a project. For instance, 'steps to recreate' is needed for bugs, but not for tasks. 

Thank so much Joe much appreciated. I did some major changes and then it keeps asking for my mandatory feild on Tasks, driving me bananas. 

Joe Pitt Community Champion Jul 26, 2017

You need to change the field configuration on tasks to not flag as required

Okay thank you @Joe Pitt will try finish changes today. 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,755 views 11 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot