-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collection of bugs #1600
Collection of bugs #1600
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some questions/thoughts/things you may want to consider:
/incidents
will be redirected to/alert-groups
, correct?- is there any URL generation, for this route, happening on the backend that may need to be updated? (open question for the whole team)
plugin.json
still references the/incidents
route. does that need to be updated as well?- might be worth adding a very small e2e test that asserts that going to
/incidents
will still redirect you to the proper page
}, | ||
path: getPath('incident'), | ||
path: getPath('alert-groups'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is plural, the other one was singular. Is this on purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it is. We had inconsistency before, and I fixed couple of places to make it all consistent. We have page name like 'alert-groups' in plural and after it will be parameter {id}
@@ -762,7 +760,7 @@ function AttachedIncidentsList({ | |||
{alerts.map((incident) => { | |||
return ( | |||
<HorizontalGroup key={incident.pk} justify={'space-between'}> | |||
<PluginLink query={{ page: 'incident', id: incident.pk }}> | |||
<PluginLink query={{ page: 'alert-groups', id: incident.pk }}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, shouldn't be alert-group
?
@@ -256,12 +256,12 @@ class IncidentPage extends React.Component<IncidentPageProps, IncidentPageState> | |||
{incident.root_alert_group && ( | |||
<Text type="secondary"> | |||
Attached to{' '} | |||
<PluginLink query={{ page: 'incident', id: incident.root_alert_group.pk }}> | |||
<PluginLink query={{ page: 'alert-groups', id: incident.root_alert_group.pk }}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, there's only 1 bug remaining to be fixed.
Reverts #1600 as it makes Slack links not working correctly with the plugin UI.
# What this PR does List of fixes: - Incident word removed from the url to `/alert-groups` page and `/alert-group/{id}` - Incident word removed from other parts of UI (Maintenance page, Linked alert groups, Templates) - Sticky rotation form was fixed at Schedules (when you scroll down and open Layer 1) - Integrations linked to Escalations chains are displayed right after loading the page - Autoresolve condition link to Alert behaviour template ## Which issue(s) this PR fixes #1490 #1489 #1486 --------- Co-authored-by: Joey Orlando <[email protected]> Co-authored-by: Rares Mardare <[email protected]>
Reverts #1600 as it makes Slack links not working correctly with the plugin UI.
What this PR does
List of fixes:
/alert-groups
page and/alert-group/{id}
Which issue(s) this PR fixes
#1490
#1489
#1486