Activity Stream Updates Incorrectly When Using Renamed Reopened Status

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Summary

      When the Reopened status is renamed to another name and it is included in the workflow, the activity stream will recognize the status still as Reopened and update the activity stream with: User X reopened Issue-Key: 40 when the it should show: User X changed the status to Production Sample on Issue-Key: 40.

      Steps to Reproduce
      1. Go to the statuses page > Rename the Reopened status to something else
      2. Open an existing workflow > Copy the workflow
      3. In the copied workflow > Remove the previous status and insert the renamed Reopened Status within it
      4. Add a Scheme to the Workflow > Update the project with the newly modified workflow
      5. Proceed to transition the issue to the newly renamed Reopened Status

      6. Check the Activity Stream > It will show: User X reopened Issue-Key: 40

      Expected Results

      The activity stream should reflect the User X changed the status to Production Sample on Issue-Key: 40.

      Actual Results

      Still shows the Reopened status activity update: User X reopened Issue-Key: 40

      Workaround

      1. Rename the Status with id=4 that show reopened in the Activity Stream back to Reopened.
      2. Create a new status with the desired correct status name.
      3. Copy the existing workflow > Edit the workflow remove the renamed reopened status and put in the newly created status
      4. Replace the workflow and make it the new active workflow > Ensure all the transitions are correct
      5. The activity stream will update correctly now.

        1. reopen1.png
          20 kB
          Niro
        2. reopen2.png
          16 kB
          Niro
        3. Screen Shot 2017-11-23 at 9.59.02 am.png
          28 kB
          Klaus

            Assignee:
            Unassigned
            Reporter:
            Niro (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: