Inconsistent Behavior Saving 'Delivered Value' in Objective Terminating States"

XMLWordPrintable

      Issue Summary

      Jira Align presents an inconsistent behavior when customers try to save the 'Delivered Value' when Objectives are set to the "Missed" state.

      Steps to Reproduce

      1. In the OKR HUB, using the new Objective Experience
      2. Open a Program Objective with the Status set to "Missed"
      3. Modify the Delivered Value to 7 (can be any value)
      4. Click off the Delivered Value field to remove focus from the field 
      5. Hit Save
      6. Now switch to the legacy Objective details view and perform the same steps.

      I recorded this quick Loom demo of the behavior reported by the customer.
       

      Expected Results

      In both objective new and legacy experiences, the following messages are displayed:

      "You have set the delivered value but the status of the objective is not set to completed. Please update the status of the Objective or remove the Delivered Value"

      Upon clicking save, receive the error: Only completed objectives can have delivered value.

      Actual Results

      In the new objective experience the following messages are displayed:

      "You have set the delivered value but the status of the objective is not set to completed. Please update the status of the Objective or remove the Delivered Value"

      Upon clicking save, receive the error: Only completed objectives can have delivered value and the values are not saved.

       

      In the legacy objective experience, the orange warning message is received, however, on clicking save, we are able to save the "Delivered value" for the objective.

      Workaround

      Saving the delivered value works in the legacy objective experience.  That is the only workaround at the moment.

            Assignee:
            Don Fuller
            Reporter:
            Edvaldo Lima (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: