Field "Story Point" still required for Issue type "Story" even if Story doesn't have "Story Point"?

[Casper]

I have Issue Type "Story", this issue type has a "Screen" named "Screen Level 0" because this screen is for all issues which are level 0 in the issue hierarchy
( Task / Bug / Story ) and that screen doesn't have a "Story Point" field.

For Sub-tasks I created a screen "Screen Level -1" and there are field "Story point" which is Required.

And the situation that, when I create a Story I can't create It because Jira sends me alerts that a Story points field is required but there is no Story point field.

How can I fix that?

[Tim Perrault · Accepted solution]

Hello @Casper 

You could create a new Field Configuration Scheme and new Field Configurations for the different grouping of issue types within the project. For the sub-tasks field configuration require the story point field and on the field configuration for the other fields don't require the field.

[Casper · Accepted solution]

I solve this by workflow, I just change the Story Point field to Optional in the Fields Configurations, and in the Sub-task workflow, I add the validator if the field Story Point is empty showing an error message.

Thank you, everyone guys!

[Mikael Sandberg · Accepted solution]

Have a look at the field configuration scheme for stories and see if story points is set to required, and you should also check the workflow used by stories to see if you have a validator on create that makes story points required.

[Kris Dewachter · Accepted solution]

Hi @Casper ,

Can you check in the Field Configuration screen of the project if the "Story POints" field is marked as a required field.

Can you also check in the workflow if the field is marked as required. Check the validator settings of the "Create" transition.

Best regards,

Kris

[Casper]

Hi @Kris Dewachter,

But the point that I want to have "Stort Point" Filed as required but just for issue types as Sub-Tasks not Story, so I delete the field "Story Point" for Story but not for Sub-Tasks, but you know it's still required for both. Even Sub-Tasks and Story have different "Screens" but as I say still required for both.

So in the Field Configuration screen of the project, it's marked as required.