-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
None
-
Affects Version/s: 10.126.3, 10.128.2
-
Component/s: Obstacles - Risk|Impediment
-
7
-
Severity 3 - Minor
-
No
Issue Summary
If you create a brand new Risk and leave the dropdowns Occurrence/Impact/Critical as not set, Jira Align raises a red toaster indicating those fields are mandatory.
Even the dropdowns are not marked with a red asterisk * and the "Required" toggles are disabled in Administration > Details Panel settings > Risks

This is reproducible (yes)
Steps to Reproduce
- Create a brand-new Risk
- Leve Occurrence/Impact/Critical as not set and complete all the mandatory fields
- Note that a red toaster will appear saying the dropdown values are invalid
Expected Results
- If they were designed to be hard-required they are supposed to be marked as mandatory in the UI (Red asterisk).
- Their mandatory behavior should reflect the Risk required field configuration in details panel settings > Risk > field list
Actual Results
No mandatory marker on the fields (Red asterisk).
Configuration in Administration > Details Panel settings > Risks doesn't work, not allowing the users to choose if they are mandatory or not
...
Workaround
Adds any value to save the new risk
- is connected to
-
JALPM-3750 Loading...
- resolves
-
ALIGNSP-22081 Loading...
-
ALIGNSP-22360 Loading...
-
ALIGNSP-22577 Loading...
-
ALIGNSP-22908 Loading...
-
PS-156286 Loading...
-
PS-158950 Loading...