Risk - Error Message Indicates Required Selection for Risk Occurrence/Impact/Critical Path Dropdowns Despite Not Being Set as Mandatory

XMLWordPrintable

      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

      1. Create a brand-new Risk
      2. Leve Occurrence/Impact/Critical as not set and complete all the mandatory fields
      3. Note that a red toaster will appear saying the dropdown values are invalid
      4.  

      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

            Assignee:
            Bhanu Vanjaku
            Reporter:
            Victor Fragoso
            Votes:
            17 Vote for this issue
            Watchers:
            21 Start watching this issue

              Created:
              Updated:
              Resolved: