MOR-PROC-018 Last Update Date: Nov, 2024

Bug Template - Performance Issue

Notes

• Urgency also needs to be added to the Tag field
• Related tasks (User Stories or Bugs etc) should be added as a link in the Related Work section
• See Raising Urgent Issues (opens in a new tab) for details on how to identify and action an urgent issue.

Template

Urgency: [ P1 - Urgent (Inside BH) | P2 - Urgent (Outside BH) | P3 - High Priority (72 Hours) | P4 - Medium (7 Days) ]
Environment: [ Prod | cmms-test | cmms-demo | cbc-post ]
Platform: [Portal/App (iOS/Android)]

Frequency: [Intermittent | Consistent]
(Optional) User Types Affected: [All/Role/Parent Type/Specific User etc]
(Optional) First Occurrence: [If known, detail when the issue began]

Location of issue: [Name Location of issue] - [URL to issue]

Affected API Calls:
[list of api calls]

Duration of issue:
(Optional) Previously known duration of call: [data]

Steps that cause the slowdown:

1. Step 1
2. Step 2
3. Step 3

Ideal response time:
[example: 5 seconds, under 10 seconds]

Freshdesk:
[Link to freshdesk ticket(s)]

Work Item:

Attachments:
[Indicate if any screenshots/videos/documents have been attached to the task]

Screenshots:
[screen shots]