User Stories, Tasks, Bugs advised Workflows
Workflows
| Issue type | Workflow name in Jira | Workflow | Description |
|---|---|---|---|
| User Story | US: Basic SAFe team workflow_general v1.0 | User stories are a simple, concise method for defining pieces of functionality from the user's perspective. To Do - User story was created and is part of the backlog In Refinement - Functional and technical analyses should be done during this stage in order to prepare to the next step Ready for Sprint - All requirements are clear and user story is ready to planning. The definition of ready needs to be met on this stage. In Development - User story was planned and is in process of development by team Ready for testing - User Story is ready and awaits for QA to start testing it In Testing - User story in process of testing by team and validated by PO Ready for UAT - User story is in sandbox and ready for the start of User Acceptance Testing In UAT - User story is in testing by business/users and PO Ready for release - User story passed UAT and ready to be released. The definition of Done needs to be met. Released - User story was released to Production Closed - Final validation of delivered user story by PO Rejected - If user story in not relevant anymore it should be Rejected More information about User story can be found here. | |
| US: Basic SAFe team workflow_general v1.0 | US: Basic SAFe team workflow_Salesforce v1.0 | Technical request such as data upload, devops activities etc | |
| Sub task | Software Simplified Workflow | Small parts of work separated form User Stories or larger Task. | |
| Spike | Software Simplified Workflow | Research or exploration effort aimed at addressing a specific technical challenge or uncertainty. | |
| Bug | Bug_General_Basic SAFe team workflow | Error, flaw, or unintended behavior. |



