Add DSYS-616 cross-repo migration automation spec#1007
Draft
georgewrmarshall wants to merge 8 commits intomainfrom
Draft
Add DSYS-616 cross-repo migration automation spec#1007georgewrmarshall wants to merge 8 commits intomainfrom
georgewrmarshall wants to merge 8 commits intomainfrom
Conversation
Contributor
📖 Storybook Preview |
Contributor
📖 Storybook Preview |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Epic completion query misses issuetype filter causing deadlock
- Updated both epic completion JQL snippets to include "issuetype = Story" so the closure check matches the automation’s Story-only processing scope.
Or push these changes by commenting:
@cursor push 2afd5d2441
Preview (2afd5d2441)
diff --git a/.cursor/automations/dsys-616-migration-docs-cross-repo.md b/.cursor/automations/dsys-616-migration-docs-cross-repo.md
--- a/.cursor/automations/dsys-616-migration-docs-cross-repo.md
+++ b/.cursor/automations/dsys-616-migration-docs-cross-repo.md
@@ -116,7 +116,7 @@
After Story updates, evaluate epic:
```jql
-parent = DSYS-616 AND statusCategory != Done
+parent = DSYS-616 AND issuetype = Story AND statusCategory != Done- If zero remaining, transition DSYS-616 to Done and comment summary.
@@ -167,7 +167,7 @@
- After processing Stories:
- Query remaining:
-
parent = DSYS-616 AND statusCategory != Done
-
parent = DSYS-616 AND issuetype = Story AND statusCategory != Done- If none remain, transition DSYS-616 to Done and comment with summary.
- Output concise run summary:
</details>
<sub>You can send follow-ups to this agent <a href="https://cursor.com/agents/bc-5c80bc8a-0a6c-43bf-b7a0-b2f9d281e429">here</a>.</sub>
<!-- BUGBOT_AUTOFIX_REVIEW_FOOTNOTE_END -->
Contributor
📖 Storybook Preview |
Contributor
📖 Storybook Preview |
Contributor
📖 Storybook Preview |
Contributor
📖 Storybook Preview |
Contributor
📖 Storybook Preview |
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
1 participant
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.
Description
Adds a new Cursor automation spec for DSYS-616 that handles cross-repo migration-doc workflow and Jira transitions.
The spec introduces:
Fixes: DSYS-<id>PR-description matching as the source of issue linkage,To DotoIn Progress.Related issues
Fixes: DSYS-616
Manual testing steps
.cursor/automations/dsys-616-migration-docs-cross-repo.md.Fixes:matching rules are present.Screenshots/Recordings
N/A (documentation-only change)
Before
N/A
After
N/A
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Low risk documentation-only change that adds markdown specs for Cursor automations; no runtime code or production behavior is modified.
Overview
Introduces a new
.cursor/automations/directory as the version-controlled source of truth for Cursor Cloud Automation specs, including an operating model and conventions.Adds a DSYS-616 cross-repo automation suite split into three specs: MMDS migration-doc authoring (with lint/quality gates and feedback loop), and mobile/extension cron-driven “replace single instance + update
@deprecatedJSDoc” client workflows with deterministicMIGRATION_DOCS_VERSION/Processed MIGRATION_DOCS_VERSIONmarkers and Jira transition rules.Updates
docs/ai-agents.mdto document this new “Layer 2.5” automation-spec layer in the agent documentation structure.Written by Cursor Bugbot for commit 26a61ca. This will update automatically on new commits. Configure here.