
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2022 12:37 AM
Hello all
Have an interesting issue in the Agile Development module. The field "Acceptance criteria" is mandatory, but the asteriks is not displayed in the form. For the Short description this is displayed correctly.
If you leave the field empty and save, the asteriks then appears briefly and of course the message that the record could not be written.
The asteriks then disappears again immediately and is no longer displayed (good timing on the print screen below was required to capture the asteriks).
It does not help if the field label is shortened, I have already tried this.
Any idea?
Thanks for inputs and greetings
Alex
Solved! Go to Solution.
- Labels:
-
Agile Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2022 12:53 AM
Hi Alex,
Have you checked for a Client script or UI Policy that is making it not mandatory? The timing you describe could be that shortly after load a Client script f.e. starts and sets the field (on your screen) to not be mandatory. Example script to search for would be:
g_form.setMandatory('<acceptance criteria field>', false);
Or any UI Policy for this specific view could also cause this.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2022 01:11 AM
Great hint, thank you very much! It was ä UI Policy and now the asteriks is displayed properly.
Regards Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2022 01:13 AM
You are welcome Alex, happy to help! 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2022 07:10 AM
Please note that Acceptance Criteria is set as non-mandatory in draft state so that it is possible to write a draft of a story.
Making acceptance criteria mandatory on draft will just cause users to write acceptance criteria like "-", "TBD" or ":)" and start ignoring the quality of the field when changing state from Draft to Ready.
In general, you don't want to have many mandatory fields on submit, because that makes people less likely to write down the stories and eventually use some other tool instead.