Jira SCRUM board: Difference between revisions
Jump to navigation
Jump to search
Added category Jira management |
No edit summary |
||
| Line 1: | Line 1: | ||
In order to manage properly project tasks, Jira board need to have the following columns: | In order to manage properly project tasks, Jira board need to have the following columns: | ||
== To do == | == To do == | ||
Tasks that have to be completed during the current Sprint start here. Tasks are not assigned to anybody. | Tasks that have to be completed during the current Sprint start here. Tasks are not assigned to anybody. | ||
== In progress == | == In progress == | ||
When a developer has started to work on the task, the task is transitioned to this column, to make everybody know the development has started. | When a developer has started to work on the task, the task is transitioned to this column, to make everybody know the development has started. | ||
== Dev completed == | == Dev completed == | ||
| Line 19: | Line 15: | ||
* '''NoQa''': task has not been validated by QA Team | * '''NoQa''': task has not been validated by QA Team | ||
== QA == | == QA == | ||
Revision as of 12:10, 22 October 2025
In order to manage properly project tasks, Jira board need to have the following columns:
To do
Tasks that have to be completed during the current Sprint start here. Tasks are not assigned to anybody.
In progress
When a developer has started to work on the task, the task is transitioned to this column, to make everybody know the development has started.
Dev completed
Once the task is completed, is transitioned to this status. Within this status, the task can have these labels:
- Pull request: the task is being reviewed by other developer
- NoQa: task has not been validated by QA Team
QA
Task is ready to be tested by the QA team
Ready to deploy
Task has been validated and can be deployed
Deployed
For those tasks that are already in Production