Create SDLC Tasks

A task is the main entity of the whole development process since it contains information about the requirements for the responsible person, work progress, and result.

The article contains information about the access level required to work with the tasks, the creation of tasks of different types, and about the creation of articles from defects.

Access to tasks

---

Operation	pda_admin	pda_user	Other roles
Create	+	The operation is allowed but the user can only fill in the Project field with the projects in which they are a team member or a team leader.	-
Write	+	The operation is allowed for any user with the role, if the Project field is empty. If the Project field is filled in, allowed for: Team leader. Team member. The user specified in the Assigned to field. If the field Product or Product module is filled in, allowed for the product and product module owner. The user can only select a project where they are a team member or a team leader.	-
Read	+	+	+
Delete	+	Allowed for the team leader of the project to which the task is related.	-

Create a task

---

To create a task, complete the following steps:

1. Find the required task type in the SDLC → Tasks section of the navigator. Open the list for the required task type.
2. Click New and fill in the form fields.
3. Click Save or Save and exit to apply the changes.

tip

You can also create new tasks in the backlog management widget (for Kanban projects) or sprint planning widget (for Scrum projects).

Task form fields

General

Field	Mandatory	Description
Name	Y	Specify the task title.
State	N	Select the task state. The available options vary depending on the current task state. The field appears after saving the record and is automatically filled in with New.
Blocked	N	Select the checkbox to prohibit the transition of task to another state. When the checkbox is selected, the State field is read-only and the task card cannot be dragged between the columns. The field appears after saving the record.
Block reason	N	Specify the task block reason. The field is displayed if the Blocked checkbox is selected, and it is not available for Subtasks. When the checkbox is cleared, the field is hidden but not cleared.
Parent task	N	Specify a higher level task that includes this task. Depending on the type of the created task, the following types are available for selection: Feature: only Epics are available. User story, General task, Defect: Epics and Features are available. Subtask: all task types are available apart from other Subtasks. The field is not available for Epics.
Priority	N	Specify the task priority. Available options: Low Medium High
Rank	Y	Specify the task rank. The lower the rank is, the higher the task priority is. The field is not available for Subtasks.
Description	N	Add the task description.
Assigned user	Y/N	Specify the employee responsible for the task. The field is mandatory in the Development, Review, Testing, Done, and Released states. You can only specify an employee with the pda_user or pda_admin role.
Work notes	N	Add work notes.
As a	Y	Specify the consumer of the functionality that will be implemented in the User story. The field is available only for User stories.
I want	Y	Describe the functionality that will be implemented in the User story. The field is available only for User stories.
So that	Y	Specify the consumer pains that will be solved by the functionality implemented in the User story. The field is available only for User stories.
Acceptance criteria	Y	Specify the parameters that the task must comply with to be considered completed. The field is available only for Features and User stories.

Planning

Field	Mandatory	Description
Planned start date	N	Specify the date to start working on the task.
Planned end date	N	Specify the date when the task needs to be completed.
Story points	N	Estimate the task in story points – standard units of task complexity, amount of work, and involved risks. The field is not available on the Subtask form.
Planned time to spend	N	Specify the planned amount of time required to complete the task.

Additional

The tab is not available for the Subtasks.

Field	Mandatory	Description
Project	N	Specify the project to which the task belongs.
Release	N	Specify the release that will include the task result. The field is only available for the tasks related to the projects dedicated to product development (the Product development checkbox is selected on the project form).
Related article	N	Specify an article that contains information on the defect. For instance, it could be the conditions triggering the defect or a workaround. You can create an article using the corresponding UI action in the burger menu . The field is available only for Defects and appears on the form after the first saving of the record.
Product	Y	Specify the product to which the task is related. The field is only available for the tasks related to the projects dedicated to product development (the Product development checkbox is selected on the project form).
Product module	N	Specify the product module to which the task is related. The field is only available for the tasks related to the projects dedicated to product development (the Product development checkbox is selected on the project form).
Detected in release	N	Specify the release in which the defect was found. The field is only available for Defects.
Sprint	Y/N	Specify the sprint that includes the task. The field appears only if the task belongs to a Scrum project. The field is mandatory in all states except New and Canceled. The field is not available for Subtasks.

Developer Panel

This section contains the data on the current task received from the Git integration module. Read the detailed description of the panel in the Developer Panel article.

Related lists

caution

No related lsits are displayed by default for custom task types. You can add them manually if necessary.

For Epics and Features:

• Child Tasks – the list of tasks for which the current task is the parent task.

For the tasks of all types except for Subtasks:

• Subtasks – the list of subtasks related to this task.

For the tasks of all types:

• Task Dependencies – the list of dependencies in which this task is selected as the initial or dependent task.