I have attached different screens for Create and Edit issue operations in the Screen Scheme and there's one field configuration under the field configuration scheme. The issue type is same for Create and Edit issue operations.
Now the difference in the screens is 2 fields, which are not added to Create screen and they are required in Edit screen. The field configuration is validating the required fields at the create screen also and throwing error that those fields are required.
How to implement this scenario? I don't want to show those 2 fields in create screen and they are required in Edit screen.
If any field is set as mandatory in the field configuration scheme, then it should have a value assigned before the issue can be created.
You can have a workaround by setting a default value if they are custom fields there by skip the mandatory check while creating the issue, but you can modify the values later by editing the issue.
Usually, for such cases the custom fields will be prompted as required while a workflow transition by adding the fields to workflow transition screen, and not in the field configuration scheme. You will need to install add-ons like 'Jira Suite Utilities' for implementing the workflow field required validator.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events