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?

[Robert Wen_Cprime_ · Accepted solution]

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).

[Diatta Harris]

Here are the issue types.

[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.

[Diatta Harris]

Reproduction steps are only required for bugs.

[Robert Wen_Cprime_]

So good design suggests that your "Default" Field Configuration should have Reproduction Steps as Optional and a "one-off" Bug Field Configuration would have Reproduction Steps as Required.

Once you have that set up, you can associate that Field Configuration Scheme to your project (illustrated elsewhere in this question) and you should be good to go!

[Diatta Harris]

Thank you all for your patience.  I'm not configuring daily in jira which is why I am on the struggle bus.  I will pick this back up on Monday.  Thank you all again and I will be back here Monday.  

[Diatta Harris]

Here's the workflow.

[Robert Wen_Cprime_]

Workflow is not relevant here.  We need to see about associating CRM Salesforce project to your new Field Configuration Scheme.

1. Go to the CRM Salesforce project -> Project Settings -> Summary

2. Find the Fields section

3. Click the current scheme 

4. Select Use a different scheme

5. Find your new Field Configuration Scheme, select it, and click Associate

[Diatta Harris]

I believe I created a separate bug field configuration scheme but need help associating with the project.

[Diatta Harris]

I need to figure out how to associate this scheme with the project.

[Diatta Harris]

I'm trying to edit and disassociate the bug field with the default configuration as well.  Not sure how to do that.

[Robert Wen_Cprime_]

To associate a field configuration scheme with a project, look at my earlier response in this thread.

[Diatta Harris]

I think I finally figured it out.  Thank you.

[Robert Wen_Cprime_]

Excellent!  I'm glad it worked out for you!

Please feel free to mark this as answered!

Have a great day!

[Trudy 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.

[Trudy 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.

[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

[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.

[Robert Wen_Cprime_]

OK, @Diatta Harris so the field Reproduction Steps is set as required through the Field Configuration.

Can you give me a screenshot of the Field Configuration scheme associated to your "CS" project?

[Trudy Claspill]

Based on the screen image you provided you are viewing the Default Field Configuration. You can confirm that at the top of the screen.

When you set a field as Required in the field configuration, then that field becomes required for all issue types to which that Field Configuration has been associated through a Field Configuration Scheme that has been applied to a project.

It doesn't matter if the field is on screens for those issue types or not. If it is marked as Required here, then Jira will require it to be filled in.

The Default Field Configuration can be used in custom Field Configuration Schemes as well as being used in the System Default Field Configuration.

Notice in my image above it says that the Field Configuration is Shared by 22 projects. Any field set to Required in this Field Configuration will affect all 22 projects.

If you navigate to those projects and go to Project Settings > Fields, you will see the Issue Types that use that Field Configuration.

All the Issue Types that use that Field Configuration will be now require that field, regardless of whether it is on the screens used by those issue types.

If you want a field to be Required for only specific issue types, then you have to create a separate Field Configuration where you set that field to required, and in the Field Configuration Scheme used by the project associate that new Field Configuration to the specified issue types.

If your project is using the System Default Field Configuration, as shown in my image above, then you will have to create a new Field Configuration Scheme because the System Default can't be updated.

https://support.atlassian.com/jira-cloud-administration/docs/configure-a-field-configuration-scheme/

[Diatta Harris]

[Diatta Harris]

Is it possible we can hop on a call?

[Robert Wen_Cprime_]

OK, can you show the Field Configuration Scheme associated with your CS project?

@Trudy Claspill and I think you have only a single Field Configuration in your Field Configuration Scheme.  This means that the Field Configuration will apply to ALL ISSUE TYPES regardless if they're visible on a screen or not.

The solution is to create a separate Field Configuration that has Reproduction Steps set to required and associate that Field Configuration to the Bug issue type on the Field Configuration Scheme.

[Diatta Harris]

Thank you to everyone assisting me with this.  I'm trying not to tie myself up in knots.  This is the view field configuration schemes screen.  I created the User Story Field Configuration so what do I need to do from here?

[Robert Wen_Cprime_]

Looks like you have to change the configuration of the Workday field scheme.

1. Copy the Unified Project for Workday Field Configuration.

2. Change the name of the original Unified Project for Workday Field Configuration (my suggestion, Bug Field Configuration)

3. On the copy Field Configuration, set Reproduction Steps to Optional

4. Configure Workday field scheme to associate the original copy to Bug issue type, and the copy to all others.

[Diatta Harris]

Here is the field configuration scheme screenshot.  The default has Reproduction Steps as required.  The User Story version does not have that field as required.

[Diatta Harris]

@Robert Wen_Cprime_ Workday isn't my project.  My project is CRM Salesforce.