Repository navigation
feat(issues): Expose activation time for regression date ranges - #128271
Draft
roggenkemper wants to merge 1 commit into
Draft
roggenkemper wants to merge 1 commit into
roggenkemper wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
Scope: Backend
Contributor
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you add the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expose the stored
activeAttimestamp in issue details so the default date range can use the latest regression without relying on the truncated activity feed. Register the frontend-exposedorganizations:issue-details-since-regressedflag, which remains off by default.Frontend follow-up: #128272. Land and deploy this API change first. Endpoint coverage checks the initial activation and a later regression. Local endpoint tests are blocked because the Docker VM could not start; schema validation and type checks pass.