Changing approvers on an issue with multiple approval steps appears to change approval history for earlier approvals

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Component/s: Approvals
    • None
    • 8
    • Severity 3 - Minor
    • 2

      Issue Summary

      This is reproducible on Data Center: no

      We have been progressively rolling out a new feature that allows admins to exclude reporters or assignees from approving requests. This changed the way we calculate lists of valid approvers, and introduced a bug in how we display of approval history. This bug only affects requests that go through more than one approval status and use the same field for approvers. In later approval steps, removing an approver from the approvers field will cause that approver's decisions to disappear from history on earlier approvals.

      Steps to Reproduce

      1. Modify an existing workflow to include two or more approval statuses. Make sure that it's possible to send a request through both statuses.
      2. Apply this workflow to a request type and create a new request.
      3. Add approvers to the configured approvers field (if necessary)
      4. Progress the request through the first approval
      5. Progress the request to the next approval status
      6. Remove one or more users from the approvers field who approved the earlier status

      Expected Results

      The request should display all the valid decisions recorded for the previous approval.

      Actual Results

      The decisions made by earlier approvers will disappear after they are removed from the approvers field

      Workaround

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

            Assignee:
            Brian Doidge (Inactive)
            Reporter:
            James Sinclair (Inactive)
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: