Skip to content

refactor(stovepipe): Reuse issue status in history - #985

Merged
mnoah1 merged 1 commit into
mainfrom
prath.shenoy/refactor/stovepipe-issue-log-status
Oct 29, 2026
Merged

mnoah1 merged 1 commit into
mainfrom
prath.shenoy/refactor/stovepipe-issue-log-status

Conversation

@prathshenoy

@prathshenoy prathshenoy commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

What:

  • Reuse the same open/closed statuses for current issue records and retained history.

Why:

  • Remove two vocabularies for the same issue lifecycle. Current records use open/closed, while history uses opened/resolved and requires a translation. Sharing the status type makes the records consistent without changing when issues open or close.

Test Plan

  • Add unit tests.
  • Verify issue-history persistence against a real MySQL database.

Revert Plan

  • Revert this PR before enabling issue-history writes. The table layout remains unchanged, with no existing history to convert.

Issue Links

@prathshenoy
prathshenoy force-pushed the prath.shenoy/refactor/stovepipe-issue-log-status branch from 692f4df to a871267 Compare October 29, 2026 04:26
@mnoah1
mnoah1 added this pull request to the merge queue Oct 29, 2026
Merged via the queue into main with commit 4db5cf1 Oct 29, 2026
19 checks passed
@mnoah1
mnoah1 deleted the prath.shenoy/refactor/stovepipe-issue-log-status branch October 29, 2026 13:30
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