...
User Documentation
Update all relevant user and deployment documentation, including scripts and packaging instructions.
Configuration and Build Scripts
All configuration files, Docker files, and build scripts must be updated and tested to reflect changes.
Personal Data Disclosure
The personal data disclosure form must be updated as needed to comply with data handling policies.
...
5. User Story Workflow
...
Jira Workflow Columns
Todo
Blocked/Questionable
In Progress
In Code Review
In Deployment
In QA
In PO Review
Done
Status Transitions
Blocked/Questionable: Move the story here if some impediments or uncertainties need resolution.
In Progress: Move the story to In Progress when development begins. During the development process, a developer should move the story to the most relevant project in JIRA. There shouldn't be any stories in the EUREKA project that have PRs. If there is a need to make the code changes in multiple projects - create a story per project and link them to the main bug or story.
In Code Review: Move the story to In Code Review after development is complete and a PR is ready. If it is a bug, a developer should fulfill the RCA field.
In Deployment: After deploying the code to the Kitfox Dev Rancher Environment for developer testing and validation, move the story to “In Deployment” and merge the PR to the master branch. Before the merge, all comments in pull requests should be marked as resolved.
In QA: After deployment to the Kitfox Testing Environment, and when the QA team begins testing, move the story to In QA.
In PO Review: Once QA has verified the story and it's ready for Product Owner (PO) review, move the story to In PO Review.
Done: Move the story to Done after the PO has accepted the story and no critical issues are remaining.
Acceptance Criteria
All acceptance criteria outlined in the user story must be fully met.
Critical Bugs
Ensure there are no open critical bugs associated with the user story before moving it to Done.
...