You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Issues / PRs are tasks. Draft tasks can also be created from the project and then converted to GitHub Issues.
Important properties
The levels of these may be adjusted to provide more details (or less) depending on the team's needs.
Status (Shown as columns)
The status of the task. The status have a description explaining which items fit in each category.
Week (Used to filter tasks)
Specifies the week this task will be worked on.
Other properties
Size (XS<S<M<L<XL)
How big the task is. Closely related to the effort required to finish the task.
Priority (P0>P1>P2)
How important the task is. Closely related to how important the task is to continue working.
Views
Views are different layouts for visualizing the project's tasks with different orientation, purpose and information.
In our project there are several views with self-explanatory names.
Workflows
The project can change the status of a task depending on an action on the issue / PR ie. closing, opening, requesting changes...
The text was updated successfully, but these errors were encountered:
Link
https://github.com/orgs/Arquisoft/projects/147
Brief onboarding
Tasks (Issues / PRs)
GitHub Issues / PRs are tasks. Draft tasks can also be created from the project and then converted to GitHub Issues.
Important properties
The levels of these may be adjusted to provide more details (or less) depending on the team's needs.
The status of the task. The status have a description explaining which items fit in each category.
Specifies the week this task will be worked on.
Other properties
How big the task is. Closely related to the effort required to finish the task.
How important the task is. Closely related to how important the task is to continue working.
Views
Views are different layouts for visualizing the project's tasks with different orientation, purpose and information.

In our project there are several views with self-explanatory names.
Workflows
The project can change the status of a task depending on an action on the issue / PR ie. closing, opening, requesting changes...
The text was updated successfully, but these errors were encountered: