nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Question about required field

Diatta Harris

"Reproduction Steps" is not on the Story screen layout at all, but is on the Bug layout and is required.

This is perfect.

But, now it turns out that when we create a new Story, the system displays an error and tells us that we need to fill in "Reproduction Steps." Of course we can't do that since the field isn't there. Any thoughts on why this is happening?

Accepted answers

Robert Wen_Cprime_

One question before we associate the User Story Field Configuration scheme to the CRM Salesforce project: Are Bugs and Stories the ONLY issue types in the project (including subtasks). If not, Reproduction Steps will then be required for ALL issue types (except Stories).

All comments

Robert Wen_Cprime_

Have a look at the project's field configuration. Chances are someone has marked the Reproduction Steps field as Required.

Field configurations are managed by field configuration schemes. For your different issue types you need to do the following.

1. Set up a copy of the field configuration.

2. In the copy, remove the requiredness for Reproduction Steps.

3. Go to the Field Configuration scheme for the project, associate the new copy to your Story issue type or set as default. If you're setting as default, go to step 4.

4. Associate the original field configuration to the Bug issue type.

This may get more complex if field configuration schemes are shared, because you don't want to affect other projects.

Hope this helps

Trudy P Claspill

Hello @Diatta Harris

Another possible explanation is that the Create transition in the Workflow has a Validator to ensure the Reproduction Steps field has a value, and both issue types use the same workflow.

In that case you would need to make a copy of the workflow, remove the Validator, and then update the Workflow Scheme to use the new Workflow for the Story issue type.

Diatta Harris

Hello Robert. I'm a little confused with what you are instructing. Upon review the "Reproduction Steps" is a required field and is only assigned to the bug screen.

Robert Wen_Cprime_

Hi @Diatta Harris .

Can you show me where it's set that Reproduction Steps is a required field? Also, s far as it being assigned to the bug screen, is that assignment done by adding the field to the screen for the bug, or are you setting field context?

Screenshots are best.

Diatta Harris

I added the field to the screen for the bug.

Field configuration screenshot.png

Trudy P Claspill

Based on the screen image posted in @Robert Wen_Cprime_ 's Answer thread, my answer doesn't apply to this situation.

Diatta Harris

Hello,

I don't see a validator upon creation of user story. Please see below.

User story workflow.png

Robert Wen_Cprime_

Diatta Harris

Here are the issue types.

Issue types.png

Diatta Harris

Here's the workflow.

Robert Wen_Cprime_

If you want Epics and Tasks to have Reproduction Steps as required, you're good to go: just associate the User Story Field Configuration Configuration Scheme to the CRM Salesforce project.

If not, you'll need to tie Epics and/or Tasks to the User Story Field Configuration and then associate the Configuration Scheme to the CRM Salesforce project.