Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-13306

Unable to copy PIR Template for re-use in Request Type Configuration for Post Incident Review

XMLWordPrintable

      Issue Summary

      This is reproducible on Data Center: NA

      Steps to Reproduce

      • When a PIR (Post Incident Review) Request Type is enabled for a given project for the first time, a 'Description' field containing the PIR template is added to the 'Request Type Configuration' -> 'Create a Post Incident Review' > 'Request Form' under 'Project Settings' > 'Request Types' > 'Post-incident Reviews' > 'Create a Post Incident Review' (Screenshot attached to this ticket)
      • Please note that the 'Use preset value and hide from portal' button is enabled

       

      Template available under 'Description' by default:

      {
      "content": [
      {
      "type": "heading",
      "attrs": {
      "level": 4
      },
      "content": [
      {
      "type": "text",
      "text": "Leadup"
      }
      ]
      },
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Describe the circumstances that led to this incident",
      "marks": [
      {
      "attrs": {
      "color": "#7a869a"
      },
      "type": "textColor"
      }
      ]
      },
      {
      "type": "hardBreak"
      }
      ]
      },
      {
      "type": "heading",
      "attrs": {
      "level": 4
      },
      "content": [
      {
      "type": "text",
      "text": "Fault"
      }
      ]
      },
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Describe what failed to work as expected",
      "marks": [
      {
      "attrs": {
      "color": "#7a869a"
      },
      "type": "textColor"
      }
      ]
      },
      {
      "type": "hardBreak"
      }
      ]
      },
      {
      "type": "heading",
      "attrs": {
      "level": 4
      },
      "content": [
      {
      "type": "text",
      "text": "Detection"
      }
      ]
      },
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Describe how the incident was detected",
      "marks": [
      {
      "attrs": {
      "color": "#7a869a"
      },
      "type": "textColor"
      }
      ]
      },
      {
      "type": "hardBreak"
      }
      ]
      },
      {
      "type": "heading",
      "attrs": {
      "level": 4
      },
      "content": [
      {
      "type": "text",
      "text": "Root causes"
      }
      ]
      },
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "Run a 5-whys analysis to understand the true causes of the incident",
      "marks": [
      {
      "attrs": {
      "color": "#7a869a"
      },
      "type": "textColor"
      }
      ]
      },
      {
      "type": "hardBreak"
      }
      ]
      },
      {
      "type": "heading",
      "attrs": {
      "level": 4
      },
      "content": [
      {
      "type": "text",
      "text": "Mitigation and resolution"
      }
      ]
      },
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "What steps did you take to resolve this incident?",
      "marks": [
      {
      "attrs": {
      "color": "#7a869a"
      },
      "type": "textColor"
      }
      ]
      },
      {
      "type": "hardBreak"
      }
      ]
      },
      {
      "type": "heading",
      "attrs": {
      "level": 4
      },
      "content": [
      {
      "type": "text",
      "text": "Lessons learnt"
      }
      ]
      },
      {
      "type": "paragraph",
      "content": [
      {
      "type": "text",
      "text": "What went well? What could have gone better? What else did you learn?",
      "marks": [
      {
      "attrs": {
      "color": "#7a869a"
      },
      "type": "textColor"
      }
      ]
      },
      {
      "type": "hardBreak"
      }
      ]
      }
      ],
      "type": "doc",
      "version": 1
      }
      • Hence, when a PIR is triggered from an incident using the 'Add PIR' button, a template shows in the 'Description' field

       

      Issue

      • A case wherein the 'Description' field is modified (Template removed or Description Field removed or any other methods)

      Actual Results

      • The template is lost and currently, there is no mechanism to generate the same template again

      Expected Results

      • The user should be able to get the template back by copying the text from 'Project Settings' > 'Incident Management' > 'Post-incident reviews (PIRs') > 'Templates' and then pasting it in the 'Description' field settings in the Request Type configuration page

      Workaround

      • Manually copy the above template and paste it into the 'Description' field settings in the Request Type configuration page. Also, ensure that the 'Use preset value and hide from portal' button is enabled
      • Create a new project > Access Post Incident Review request type configurations > Copy the template and paste it to the original project

              Unassigned Unassigned
              884b494b5045 Jigar Solanki
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: