Created
December 3, 2025 13:31
-
-
Save Scheevel/0f79cf04c387a2e2a891c1f4784b4897 to your computer and use it in GitHub Desktop.
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
| ↳ sm | |
| *story-checklist @10.3 Don't try to do too much | |
| ↳ qa | |
| *test-design @10.3 and update the story with your scenarios | |
| ↳ po | |
| *validate-story-draft @10.3 and set status to for dev start, or decide if complexity needs it to be shard | |
| ↳ analyst | |
| At present, when the form is in read-only, the field values are gray, except for "Notes". What should the color scheme be, when in read? | |
| ↳ ux | |
| At present, when the form is in read-only, the field values are gray, except for "Notes". What should the color scheme be, when in read? | |
| - | |
| Prepare a new Dev Story based on fulfilling this spec and determine logical epic and story number from @docs/completed-epics.md | |
| ↳ dev | |
| *develop-story @10.3 you are authorized to begin and follow closely the QA guidance in the story | |
| ↳ analyst | |
| based on @ would you suggest `elicit` or `create-project-brief` to capture story details? | |
| ↳ sm | |
| *story-checklist @2.9 | |
| ↳ qa | |
| is a *test-design necessary for @2.9 ? | |
| ↳ deployer | |
| I've stopped all docker containers, now *smart-deploy-local @10.3 | |
| ↳ po | |
| *validate-story-draft @2.9 and set status to for dev start | |
| ↳ qa | |
| sorry, I forgot to *review and *gate based on scenarios in @10.9, we are already deploying to staging environment. Let me know if we need to reset. | |
| ↳ dev | |
| navigate to http://localhost:3000/reports and see all the errors | |
| ↳ analyst | |
| having completed @10.3, based on @ support-doc would you suggest `elicit` or `create-project-brief` to capture story details? | |
| - | |
| Prepare a new Dev Story adding a link to results. Previously we had a link to a the drawing and causing a bounding box to be displayed. I want that same link to be displayed along with each "Sample Cotext" record that is found under each "<TR>" element in "<TABLE>" with the label "OCR diagnostic results table" | |
| ↳ deployer | |
| I've stopped all docker containers, now *smart-deploy-local @2.9 | |
| ↳ sm | |
| *story-checklist @10.3.1 | |
| ↳ qa | |
| is a *test-design necessary for @10.3.1 ? | |
| ↳ po | |
| *validate-story-draft @10.3.1 and set status to for dev start | |
| ↳ dev | |
| continue *develop-story @2.9 for phases 2-4 completion | |
| ↳ analyst | |
| Rename "Search Components" menu item to "Search" on the `/search` route place 2 tabs. First tab, default is "Search Components" the current page, the 2nd tab "Search OCR" the page on the `search/diagnostic` route | |
| ↳ qa | |
| *review and *gate based on scenarios in @2.9 | |
| ↳ deployer | |
| I've stopped all docker containers, now *smart-deploy-local @2.9 | |
| ↳ sm | |
| *story-checklist @10.6 | |
| ↳ qa | |
| is a *test-design necessary for @10.6 | |
| ↳ po | |
| *validate-story-draft @10.6 and set status to for dev start | |
| ↳ dev | |
| *develop-story @10.6 you are authorized to begin and follow closely the QA guidance in the story | |
| ↳ qa | |
| *review and *gate based on scenarios in @10.6 | |
| ↳ deployer | |
| I've stopped all docker containers, now *smart-deploy-local @10.6 | |
| ↳ analyst | |
| We need to write a corrective story based on this e2e spec: | |
| - Navigate to http://localhost:3000/search?tab=diagnostic | |
| - in the input box input search term "plate" | |
| - click on any result | |
| - Expected: view of hyperlinks to `/drawing` results | |
| - Reality: redirection to http://localhost:3000/search?query=Plate | |
| This not the outcome intended, was this what was specified in the story? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment