question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add ability to resolve an incident

See original GitHub issue

Scenario

AS A user who has the ability to resolve an incident

I WANT A button that I can click that sets the incident’s status to resolved

SO THAT I can determine when an incident is no longer needed to be opened.

Acceptance Criteria

GIVEN A user who has the ability to resolve an incident and an incident that is in the reported status

WHEN I navigate to the incident that is in the reported status

THEN I should see a required text field and a button at the bottom of the page that says Resolve.

GIVEN The incident

WHEN I click on the resolve button

THEN The incident’s status should be set as resolved and the resolvedOn date should be set to the current time.

GIVEN The incident

WHEN I click on the resolve button

THEN The incident’s status should be set as resolved and the resolvedOn date should be set to the current time.

GIVEN The incident

WHEN I click on the resolve button and there is no content in the Resolution text field

THEN An error message should appear stating that the incident could not be resolved and the Resolution field should have feedback stating that it is required.

Technical Notes

  • New, required, text field called resolution should be displayed when viewing an incident
  • New permission ResolveIncident should be added
  • New redux thunk named resolveIncident

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
blestabcommented, Jul 8, 2020

Hi @jackcmeyer I see this is back to needing an assignee? You can put it on my name.

1reaction
christiantgoldencommented, Jun 9, 2020

Oh wow. I didn’t know draft PRs were a thing! Thanks for offering to review. I’ll submit a draft PR soon.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Incident Management Process: 5 Steps to Effective Resolution
The Five Steps of Incident Resolution · 1. Incident Identification, Logging, and Categorization · 2. Incident Notification & Escalation · 3.
Read more >
Incident resolution and closure
An incident is considered resolved when you provide the user with a temporary workaround or a permanent solution for the issue.
Read more >
ITIL incident management process: 8 steps with examples
Escalate unresolved incidents to the Tier 2 service desk. Gather all required information from the requesters and send them regular updates on the...
Read more >
Manage and resolve an incident - xMatters Online Help
Initiate an incident; Review an incident's details; Explore potential root causes and recent changes; Link to related active and historical incidents; Add ......
Read more >
Transforming Your Incident Management Process - YouTube
Incident response teams are evolving, thanks to DevOps, agile, ... Resolve Incidents Faster: Transforming Your Incident Management Process.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found