Changing Process Step to not-accepted on a Story in Accepted State saves the new Process Step but keeps Accepted State

XMLWordPrintable

      Issue Summary

      When a Story has Accepted State, changing Process Step to not-accepted saves the new Process Step but keeps Accepted State, creating a mismatch between Process Step and State.

      Steps to Reproduce

      1. Have a Story with Process Flow Process Steps mappings on
        • It is a non-integrated, unparented, standalone Story
      2. Change Process Step to one mapped to Accepted state, save
        • State should update to Accepted automatically
      3. Change Process Step to one mapped to any other state
        • State remains in Accepted while Process Step is saved as not Accepted

      Expected Results

      States and Steps should keep in sync per mapping.

      Actual Results

      Changing Process Step to not-accepted saves the new Process Step but keeps Accepted State, creating a mismatch between Process Step and State.

      Workaround

      Make sure to change State manually if a Story needs to be un-accepted.

      If the Story is synced with Jira, change the State from Jira.

            Assignee:
            Don Fuller
            Reporter:
            Kirill Duplyakin
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: