You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 30, 2024. It is now read-only.
Great job on this project! This ticks a lot of boxes for a project I'm working on.
The documentation states:
"Unresolved - status set automatically when a new incident is created or when a new event is received for a given incident"
However, in our testing, this is not the case. Existing incidents that have been marked as "Resolved" do not get reset to "Unresolved" status.
I have set up the project locally using the Dockerfile, and everything appears to be running normally. I have not seen any errors or log messages that would indicate an error.
I'll try and drum up a fix for this and submit a pull request.
The text was updated successfully, but these errors were encountered:
- reset incident status when new event is received
- use 82905 pattern in criteria when querying incidents by name, project_id, and message to 'avoid issues with escaping both single and double quotes'
- reset incident status when new event is received
- use 82905 pattern in criteria when querying incidents by name, project_id, and message to 'avoid issues with escaping both single and double quotes'
Great job on this project! This ticks a lot of boxes for a project I'm working on.
The documentation states:
"Unresolved - status set automatically when a new incident is created or when a new event is received for a given incident"
However, in our testing, this is not the case. Existing incidents that have been marked as "Resolved" do not get reset to "Unresolved" status.
I have set up the project locally using the Dockerfile, and everything appears to be running normally. I have not seen any errors or log messages that would indicate an error.
I'll try and drum up a fix for this and submit a pull request.
The text was updated successfully, but these errors were encountered: