Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-74750

Settings the assignee or resolution twice is not seen in issue history

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • High
    • Issue - Backend
    • None

    Description

      Issue Summary

      Change in assignee record is not seen in issue history

      Steps to Reproduce

      1. Add a post-function Assign the issue to the current user/ Set resolution to the transition 
      2. Add a screen to this transition with the Assignee/Resolution field.
      3. Publish workflow
      4. Create Issue
      5. Transition the status from To-do to In-Progress, update the Assignee/Resolution on the transition screen
      6. Check issue history, it doesn't show any records for the assignment of the issue or the resolution being set.

      Expected Results

      Show the record, Unassigned-> Username or Resolution Set.

      Actual Results

      The record is missing from the issue history. This affects the SLA stop condition leading the SLAs to continue running on the issues

      Notes

      • This bug might impact Jira Service Management SLAs:
        • If the SLA stops when the resolution is set, the SLA doesn't stop when the event is missing on issue's history.

      Workaround

      Remove the screen or the post function in the workflow.

      Attachments

        Issue Links

          Activity

            People

              ndoan@atlassian.com Ninh Doan
              74e7fd576f90 Prathiksha
              Votes:
              5 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: