--- title: "JIRA Workflows" canonical: "https://documentation.chaos.com/space/DOCSGUIDE/113289260/JIRA%20Workflows" format: markdown --- This article details the common Jira terms and workflows used in Chaos Software LTD. Guide on how to log Jira issues in the Documentation project: [https://sites.google.com/chaosgroup.com/cginternalguides/home/how-to-jira-in-the-documentation-project](https://sites.google.com/chaosgroup.com/cginternalguides/home/how-to-jira-in-the-documentation-project) ## **Issue Types** --- ### **Documentation Team** These are the main issue types and their definitions for the documentation team: **Epic **– A ticket (issue) holder for numerous tickets related to a particular release or task. **Task **– A general task for documenting - new features, modified features, technical errors for correction, etc. **Sub-task **– A smaller, detailed piece of work that is part of a larger task. By default should have a task as a parent. > ℹ️ The Documentation project allows for the creation of Tasks, Sub-tasks, Epics, New Features, and Incidents. However, the documentation workflow requires only **Tasks**, **Sub-tasks**, and **Epics**. General tickets should be marked as Tasks and related tasks for a project could be gathered in an Epic for easier management. ### **Dev and QA Teams** These are the main issue types and their definitions for the development teams: **Initiative** – A larger body of work, a strategic effort or project that aligns with long-term goals, often encompassing multiple epics. Initiatives are created rarely and are most likely to come from product planning activities in [Aha.io](http://Aha.io). **Epic **– A large body of work containing stories, bugs, tasks, etc. Epics are created in [Aha.io](http://Aha.io) by Product managers or Product owners and are transferred to Jira. **Story **– A user-centric requirement that describes a specific functionality or feature from an end-user perspective. Often written in the format "As a [user], I want [function] so that [benefit]." Stories are usually created by Product managers or Product owners in [Aha.io](http://Aha.io) and are then transferred to Jira. Must have acceptance criteria. **Improvement **– Used to extend or improve existing functionality. **Bug **– An error, flaw, or fault in the software that causes it to produce incorrect or unexpected results. **Crash **– A specific type of bug where the software abruptly stops functioning and closes. Crashes usually have critical priority and need to be resolved quickly, but in case they are too rare and specific, the reporter can decide to lower their priority. **Internal bug** – A defect that can’t be observed and tested by QA. **Task **– A general unit of work that could be or could be not a part of the feature or product scope. This includes purely technical work, e.g., refactoring, API implementation, performance optimization, etc., or any other work that is not coming from the PM/PO and needs to be logged and worked on as a Task, e.g., documentation, design, etc. **Sub-task **– A smaller, detailed piece of work that is part of a larger task. By default should have a task as a parent. **Internal Task** – Work that needs to be done for internal purposes, such as infrastructure or maintenance, not visible to end-users. **New Feature** – Is deprecated. Existing New Features in open/active status will be converted to Stories. Existing New Features in Closed/Done status will remain as they are. **Spike **– A time-boxed research task aimed at investigating or prototyping to gather information, reduce uncertainty, or explore a potential solution. ## **Status Types** --- ### **Documentation Team** These are the main issue statuses and their definitions for the documentation team: **To do** – The task has been created and is awaiting assignment.  **In progress** – Active work is being done on the issue. **QA **– The task awaits revision by a QA specialist. **Blocked  **– The issue cannot proceed due to a dependency or impediment. Action is needed to remove the blocker before the issue is returned to In Progress status and work can continue. > ℹ️ If important details are still not provided, the ticket will be moved to status **Blocked** until the ticket receives the expected update from the Reporter. **Publishable **– The task has been revised by a QA specialist and has been approved for publication. **Done **– The tasks has been published and is completed. ### **Dev and QA Teams** These are the main issue statuses and their definitions for the development teams: **Open **– The issue has been created and is awaiting triage or assignment. It has not yet been analyzed or prioritized and should not be considered ready for work by development teams. **Selected for development** –** **The issue has been reviewed and prioritized. It has been chosen for development and is ready to be worked on by the development team in the near future, next sprint or as otherwise planned. **In progress **–** **Active work is being done on the issue. A developer has started working on it and is making progress toward completion. **On Hold** – Work on the issue has been temporarily paused. This could be due to waiting for external information, resources, or decisions. **Blocked  **– The issue cannot proceed due to a dependency or impediment. Action is needed to remove the blocker before the issue is returned to In Progress status and work can continue. **Code review  **–The coding for the issue has been completed and is now undergoing review by other developers to ensure quality and adherence to standards. **QA  **– The issue has passed code review and is now being tested by the Quality Assurance team to verify functionality and detect any bugs. **Closed  **– The issue has been resolved, all work has been completed or the issue has been closed due to other reasons reflected in the issue resolution. **Reopened  **– Work on the issue has been completed and and it has been closed but now something additional is needed. Reopened status should not be confused with Open, which indicates that no work has been done on the issue yet **Rejected  **– Indicates that the request is not relevant to the team priorities or the issue can’t be reproduced. ## **Workflows** --- ### **Documentation Workflow** --- The following workflows show the development processes: ### **Epic, Initiative, Spike** --- ### **Story, Improvement, Bug, Crash, Task, Sub-task, Internal Task** --- ### **Internal Bug**