Tasks
Last updated
Last updated
The main structural element of a project is a task. The project finishes when all the tasks are completed.
In Project Manager, there are three types of tasks that a user chooses on creation. A user cannot change the type afterward.
You are free to use all these types or just Tasks. But consider using all the advantages of the Aitheon Project Manager tool.
Another name: User Story. This type of task in a project describes the desirable user experience. The project aims to create a product that meets user's needs or expectations. A story is a description of what exactly a user gets. For example, 'a customer easily signs up' - a short 'story' of what we have to achieve.
Stories on a board have special marks, but all behavior and properties are the same as of other types.
Stories answer the question 'what?', while tasks answer the question 'how?'
We may consider tasks as specific actions to make the user story real.
From this point of view it would be reasonable to create tasks as sub-tasks of specific stories. In our example the story has the following description:
In other words, we need tasks to make the flow where a customer appeals to the support service, points their request type, then gets a choice of topics, and if the problem is not solved - gets a human support.
In the bottom-left corner there is a button to add subtasks. We consider, how exactly we can implement this flow and make the subtasks:
The only type you can give a subtask is Task. It's not obligate to make tasks as story's subtasks. You can make an independent task or don't use stories at all.
Usually a task takes a span to fit in one sprint or less. If the tasks are too small, they will overwhelm the board, if the tasks are too big it will be harder to work in sprints.
You can add tasks of Issue type to the board. But if you enabled Issue Board on the project creation these issue tasks will appear there, not on the main board.
Issues have a special mark and all other properties of a task.
You can create a task directly on the main board or from any page of the project by using the CREATE TASK button.
On creation there are the properties to set up:
To create a task its enough to type its name (1).
Note that you will be able to update every property of the task later, except its type (2). Default type is TASK but don't forget about STORY and ISSUE types.
All Attachments (4) to tasks will be available in the Media tab of the project.
If you are creating a task using the CREATE TASK button it will go to the BACKLOG Column (5) by default. If the task is Issue type and the Issue Board is enabled the task will appear in the Issue Board Backlog column.
There are four Priority levels (6) with own arrow mark each. By default its Medium.
You can assign a task to one or more Assignee (7). To do this start typing their name in the field. You can assign the task only to members of the project team, no matter from your or side organization. Add needed people in the project Settings tab.
You can choose Labels for the task (8) or create a new one. You can create labels in project Settings tab.
Also you can choose an Epic (9) or create one directly from the task.
There are some additional options when you open an existing task:
You can send a direct link (1) to the task to a project team member.
Add a subtask (2). All subtasks have the Task type.
Delete the task (3).
Add a comment (4).
Also, you can update every other property except the project type.
