Task

What is a Task?

Tasks are single to-dos, assigned to one employee, and planned in a specific sprint. Tasks are oftentimes part of a story and cross-linked.

Understanding Tasks

• Tasks are being used to plan specific tasks which should not take more than 1 working day.
• They could be part of a bigger project or planned by themselves.
• Tasks can be separated into subtasks.
• Tasks can be assigned to a responsible employee (aka assignee).
• Tasks are part of a sprint or scrum.
• They are being worked on actively, can be forwarded to someone else for feedback, and can be marked as done when finished.
• Tasks can be cross-linked and can block each other.

Creating a Task

Keep track of the things that need to get done with tasks. With the ability to give each task an assignee and due date, and plenty of ways to see your tasks, you can make sure nothing slips through the cracks.

Workflow

Example of a Task

Tasks usually are related to small actions or activities that can be done with a specific topic in mind. Can be, for example, creating a generic component (code or visual), fixing a bug or error, checking some piece of information, meeting with someone, writing a report, etc.

Important fields:

It is important to have in mind that some fields in a Task are required and important to fill:

1. Summary: a brief description about the objective and context of the work.
2. Components: is a field that indicates the design team that will be responsible for the work.
3. Initiative: sometimes a Task can be related or linked directly to a greater initiative.
4. Priority: how important or urgent the work is at that moment;
5. Assignee: the person who is going to be responsible for the work.
6. Reporter: the person who had the initiative to ask or is requesting the work.
7. Liferay Watchers: one or more stakeholders that will be informed over the Task updates.
8. Due Date is the time limit or deadline for finish that specific work.
9. Description: a more detailed text giving important information over the work to be done.
10. Attachment: any imporant docuemnt should be attached to this issue
11. Linked Issues: if there is one or more issues that may have a direct impact over the Task, then it can be listed here.
12. Labels: is a complementary way of organizing by topics or themes all the work that should be done.
13. Epic Link should be the Epic that this piece of work is related to.
14. Sprint: if the Task is related to a team that works in running in sprints.