Every individual task has the following information:
- Status: indicates whether the task is "TODO" (the task is incomplete), "Done" (the task is complete), or "Not Applicable" (the task does not apply to this project). Permission required to change task status: Project Roles->Tasks->Mark tasks done/todo
- Priority: score that indicates how important the task is relative to other tasks. 10 is the highest and 1 is the lowest. Use the Priority to help select which tasks to carry out if you do not have sufficient time to do all of them. Agile teams can use the priority field to help enter SD Elements task appropriately into the backlog.
- Task Title: the title of the task. The number, such as "T133" is the unique number of the Task in SD Elements.
- Verification: The verification "ribbon" on the right side of the task indicates its verification status: pass, partial pass, or fail, as discussed below. Clicking the ribbon will open up a small verification "widget", where the user can manually set the verification status of a task.
- Note: a comment from a project team member about the task. For example, where to go to find audit evidence that the task has been completed. You can add and edit the note. Permission required to add and edit notes: Project Roles->Tasks->Write notes on tasks
- Assigned User: you can assign users to tasks, and filter the tasks page by assigned users. Once assigned, users will receive an email notifying them that you have assigned them a task in SD Elements. Permission required to assign tasks to users: Project Roles->Project Management->Assign tasks to users
Clicking on a task title will provide more information about it:
- Solution: specifies what to do.
- Problem: explains why the task needs to be completed. In some cases, the Problem will include links to training modules to learn more information. Many problems also include link to the 'Common Weakness Enumeration', which is an industry-standard reference of all well-known software security weaknesses.
- Related Tasks: are all the other tasks in the system that relate to the same underlying Problem. This allows you, for example, to link a requirement to its corresponding test case.
- How Tos: are code samples or detailed instructions on how to achieve the desired solution with a specific technology. For example, how to perform input validation with the Java Struts framework
- Verification: indicates the verification status of a task, as indicated by an automated scanning solution or manual verification. The verification section provides assurance that a task has actually been completed. For example, using automated scanning solution Veracode to check verify that the application binds variables in SQL statements to prevent against SQL injection. Each verification tool leaves a note in the system with the following fields:
- Status: Fail, pass or partial pass
- Date Tested: When the test results were imported
- Report Reference: Where in the report to find more details
- Findings: Number of findings identified and the exact reference, in the case of a Fail status
Basic task view:
Expanded task view: