Skip to content

Display event release lifecycle badges and details - #928

Open
alisawavezen12 wants to merge 8 commits into
masterfrom
feat/event-release-status
Open

alisawavezen12 wants to merge 8 commits into
masterfrom
feat/event-release-status

Conversation

@alisawavezen12

@alisawavezen12 alisawavezen12 commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Add shared release status badges beside event titles in the list and beside the event type in the header.
  • Show "New" only for events first introduced in the project's latest release.
  • Display "Resolved" and "Regression" badges, prioritizing regression over a previous resolution.
  • Use outlined badges without release names in the visible label.
  • Add hover explanations with the relevant release and clarify that automatic resolution is only a potential fix.
  • Show release lifecycle details, including the current occurrence's release even when it matches another milestone.
  • Hide missing, empty, whitespace-only, and placeholder release values.
  • Preserve the releases page's original new-events-only behavior and add explanatory text.
  • Keep badges attached to titles and prevent native text selection during Shift-click bulk selection.
  • Fix repetition table markup by placing rows inside thead and tbody.
  • Add English and Russian translations.

Related API: codex-team/hawk.api.nodejs#688
Related Worker: codex-team/hawk.workers#590

Снимок экрана — 2026-10-28 в 18 12 06

Always display the selected occurrence's release, even when it matches a
lifecycle milestone. Structure the repetitions table with table sections
and
bump the package version to 1.4.0.
Derive the latest release from the cached, timestamp-sorted releases
list,
independent of event queries. Share concurrent requests and prevent
stale
requests from repopulating the cache after a store reset. Add coverage
for
caching, failures, and reset races.
neSpecc

This comment was marked as off-topic.

Comment thread src/api/projects/index.js Outdated

if (response.errors?.length) {
response.errors.forEach(console.error);
throw new Error(response.errors.map(error => error.message).join('; '));

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm not sure we need to throw here. In GraphQL data can be successfully received along with some errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants