Skip to content

feat(stovepipe): Record project issue attribution - #1050

Closed
prathshenoy wants to merge 1 commit into
prath.shenoy/feat/stovepipe-project-issue-controllerfrom
prath.shenoy/feat/stovepipe-record-project-issues
Closed

prathshenoy wants to merge 1 commit into
prath.shenoy/feat/stovepipe-project-issue-controllerfrom
prath.shenoy/feat/stovepipe-record-project-issues

Conversation

@prathshenoy

@prathshenoy prathshenoy commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

What:

  • Record per-request issue/project associations and their completion during validation recording.

Why:

  • Populate both lookup directions for request-level issue and project queries; storage support alone does not produce attribution.
  • Avoid recording attribution from an unfinished issue set. Build outcomes and terminal issue analysis arrive independently, so recording waits for the final analysis and retains completion only after every association is durable.

Test Plan

  • Add unit tests.

Revert Plan

  • Revert this PR. It changes no schemas; any associations already recorded can remain as historical data.

Issue Links

## Summary
**What**:
- Record per-request issue/project associations and their completion during validation recording.

**Why**:
- Populate both lookup directions for request-level issue and project queries; storage support alone does not produce attribution.
- Avoid recording attribution from an unfinished issue set. Build outcomes and terminal issue analysis arrive independently, so recording waits for the final analysis and retains completion only after every association is durable.

## Test Plan
- [x] Add unit tests.

## Revert Plan
- Revert this PR. It changes no schemas; any associations already recorded can remain as historical data.

## Issue Links
- [CODEM-607](https://linear.app/uber/issue/CODEM-607)
@prathshenoy
prathshenoy force-pushed the prath.shenoy/feat/stovepipe-record-project-issues branch from a62c76e to 7d4c975 Compare November 9, 2026 17:02
@prathshenoy
prathshenoy removed this pull request from stack #1052 November 9, 2026 17:09
@prathshenoy
prathshenoy changed the base branch from prath.shenoy/feat/stovepipe-project-issue-materializer to prath.shenoy/feat/stovepipe-project-issue-controller November 9, 2026 17:11
@prathshenoy
prathshenoy added this pull request to stack #1055 November 9, 2026 17:15
@prathshenoy prathshenoy closed this Nov 9, 2026
@prathshenoy
prathshenoy removed this pull request from stack #1055 November 9, 2026 18:57
Tmwakalasya pushed a commit to Tmwakalasya/submitqueue that referenced this pull request Nov 11, 2026
## Summary
**What**:
- Define project attribution for confirmed build issues.

**Why**:
- Identify which failures affect each project. Existing project-status
results describe a project's health but do not identify the individual
issues behind that result. This contract provides the per-issue project
associations needed to build project issue views.

## Test Plan
- [x] Add unit tests.

## Revert Plan
- Revert this PR. No runtime wiring or stored data changes depend on
this contract yet.

## Issue Links
- [CODEM-632](https://linear.app/uber/issue/CODEM-632/projects-issues)

## Stack
1. uber#1046
1. uber#1047
1. uber#1048
1. uber#1049
1. uber#1053
1. uber#1054
1. uber#1050
1. uber#1051
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.

1 participant