I have a problem with configuring some custom fields to be required on the Create Form.
They are marked as required in field configurations, but they are not validated on Create Form - they even don't have a characteristic red star.
I am able to create an issue without any value in those fields. It shouldn't happen.
Solutions I've tried:
A similar problem found:
Thanks in advance for any piece of advice!
Have a great day,
Thanks for doing some research and looking at other questions already.
I just gave it a try on my 7.7.1 instance and that does seem to work as expected.
The Field Configuration that you've adjusted, is that assigned to a Field Configuration Scheme. A Field Configuration Scheme basically says which Field Configuration to use for which Issue Type. Are you sure the Field Configuration that you've changed is assigned to the correct issue type in the Field Configuration Scheme?
Thanks for a fast response @Maarten Cautreels!
I have created a field configuration called Design Team, and I have assigned this configuration for a User Story Issue type (See the screenshot).
The second screenshot shows you a field with a required mark.
On a create form the field looks like not required (third screenshot).
Thanks for the screenshots that really helps. I tried myself with a User Picker and that does work immediatly:
There's only one piece of the puzzle I haven't seen in the screenshot. The Field Configuration Scheme should be configured on the project in which you're creating the Story in. Can you check the project configuration and make sure the right Field Configuration Scheme is configured?
Thanks @Maarten Cautreels!
Each time I created a new custom field I had to choose a context for them.
I choose for the field "Product Owner" project "Design Team", and a User Story as an issue type.
Is there a place in the project when you associate a field configuration? I have never done this before from the Project configuration.
The context defines on which project(s) the field will be visible/useable but that has nothing to do with the Field Configuration Scheme.
Associating a Field Configuration Issue Scheme described the steps you should perform.
The Configuration (Schemes) are a complex matter. This page describes pretty clearly how it all works. (in case you're interested)
@Maarten Cautreels that was the missing step from the configuration!
I skipped this because I had no idea that even projects in Jira have their own Field Configurations!
This is the knowledge I was looking for!
I am extremely grateful for your responses and for a patient explanation with links to documentation.
Everything works now - after adding the proper Field Configuration to the Project Required fields behave as required fields :).
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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