Skip to content

feat(ACI): Hide team metric alerts triggered component in workflow engine UI #114504

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.

Sign up for GitHub

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

Merged
ceorourke merged 1 commit into from
Apr 30, 2026
+17 −13
Merged

feat(ACI): Hide team metric alerts triggered component in workflow engine UI #114504

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 17 additions & 13 deletions static/app/views/organizationStats/teamInsights/health.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,19 +100,23 @@ export default function TeamStatsHealth() {
/>
</DescriptionCard>

<DescriptionCard
title={t('Metric Alerts Triggered')}
description={t('Alerts triggered from the Alert Rules your team created.')}
>
<TeamAlertsTriggered
organization={organization}
projects={projects}
teamSlug={currentTeam!.slug}
period={period}
start={start?.toString()}
end={end?.toString()}
/>
</DescriptionCard>
{!organization.features.includes('workflow-engine-ui') && (
<DescriptionCard
title={t('Metric Alerts Triggered')}
description={t(
'Alerts triggered from the Alert Rules your team created.'
)}
>
<TeamAlertsTriggered
Copy link
Copy Markdown
Contributor

@saponifi3d saponifi3d Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 should we just update the url to get the workflow fire histories?

not sure how many folks use this page / data. it doesn't seem like a lot since it's broken tho...

Copy link
Copy Markdown
Member Author

@ceorourke ceorourke Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah that was our thought (Nick and I), see if anyone even notices it's gone and if they do we can update

organization={organization}
projects={projects}
teamSlug={currentTeam!.slug}
period={period}
start={start?.toString()}
end={end?.toString()}
/>
</DescriptionCard>
)}

<DescriptionCard
title={t('Number of Releases')}
Expand Down
Loading