Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4881

Dependency shows as committed without committed date

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      The customer removed the committed date from a dependency that already has been set as committed, and changed to Proposed date? field to No and saved. However the dependency is still shown as Committed

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Step 1. Created the dependency - Set Needed by = 12/Apirl/2023 and Set Committed by = 12/Apirl/2023. The dependency is set as Committed
      2. Step 2. Go To the dependency and remove the committed date and set NO in Proposed date? field
      3. Step 3. Click Save & Close
      4. Step 4. Dependency is still set as Committed, Even the committed date is empty

      Expected Results

      Committed status should be changed when the committed date is removed.

      Actual Results

      Dependency is still set as Committed, Even if the committed date is empty

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            dfuller@atlassian.com Don Fuller
            965b37518492 Rachel Kim
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: