Skip to content

fix: Prefix "Possible" in Incident Title Based on is_candidate Value#6517

Merged
shahargl merged 2 commits into
keephq:mainfrom
PrometheRus:fix/incident-prefix-possible
May 20, 2026
Merged

fix: Prefix "Possible" in Incident Title Based on is_candidate Value#6517
shahargl merged 2 commits into
keephq:mainfrom
PrometheRus:fix/incident-prefix-possible

Conversation

@PrometheRus
Copy link
Copy Markdown
Contributor

@PrometheRus PrometheRus commented May 20, 2026

Closes #6516

📑 Description

This PR fixes a logical error in the Incident Header UI regarding the "Possible" prefix.

Currently, the logic is inverted:

  • Incidents with is_candidate = false (not requiring validation) are incorrectly prefixed with "Possible ".
  • Incidents with is_candidate = true (requiring manual approval/AI-suggested) do not have the prefix

The Fix:

Updated keep-ui/app/(keep)/incidents/[id]/incident-header.tsx to correctly apply the prefix based on the is_candidate flag:

  • If is_candidate is true → Show "Possible " (indicates validation needed).
  • If is_candidate is false → Show no prefix (indicates confirmed incident).

✅ Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed

Additional Information

The term "Possible" implies uncertainty. In the current implementation, confirmed incidents were labeled as "Possible," while unverified (candidate) incidents lacked this warning. This caused confusion for operators managing incidents.

@dosubot dosubot Bot added size:XS This PR changes 0-9 lines, ignoring generated files. Bug Something isn't working UI User interface related issues labels May 20, 2026
Copy link
Copy Markdown
Member

@shahargl shahargl left a comment

Choose a reason for hiding this comment

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

lgtm

@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label May 20, 2026
@shahargl shahargl merged commit 7df2910 into keephq:main May 20, 2026
11 of 12 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

ghost commented May 20, 2026

🎊 Well done @PrometheRus! Two PRs merged already! 🎉🥳

With your second PR, you're on a roll, and your contributions are already making a difference. 🌟
Looking forward to seeing even more contributions from you. See you in Slack https://slack.keephq.dev 🚀

@PrometheRus PrometheRus deleted the fix/incident-prefix-possible branch May 20, 2026 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files. UI User interface related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[🐛 Bug]: Incorrect Prefix "Possible" in Incident Title Based on is_candidate Value

2 participants