Create WM Task

Creating a WM Task

A WM Task breaks down a user story or issue into smaller, actionable work items that team members can complete. Tasks represent the day-to-day to-dos within your sprint. Each task can be assigned to a team member, prioritized, and tracked through completion. Tasks are linked to a parent story or issue and help your team manage work at a granular level.

✏️ Create a New WM Task

Follow these steps to create a task within a story or issue:

1. Open Agile Manager
   Click the App Launcher (9-dot grid icon) and select Agile Manager.
2. Open a Parent Record
   Navigate to the WM Story or WM Issue that will parent this task. You can access these via Sprints, Releases, or search.
3. Scroll to the WM Tasks Section
   On the parent record detail page, scroll down to find the WM Tasks related list.
4. Click New Task
   Click the New button in the WM Tasks section to open the task creation form.

5. Fill in Task Details
   Enter the following information:
   • Task Name/Title: A clear, specific description of the work (e.g., "Set up database schema for user accounts")
   • Task Description: Provide additional context or implementation details if needed
   • Assigned To: Assign the task to the team member responsible for this work
   • Priority: Set as High, Medium, or Low based on dependencies and urgency
   • Status: Mark as Not Started, In Progress, or Completed
   • Due Date (optional): Set a target completion date for the task
6. Save the Task
   Click Save. The task is now created and automatically linked to the parent story or issue.

📋 Task Hierarchy & Relationships

Tasks sit at the bottom of the work breakdown structure in Agile Manager:

• Release → Sprint → Story/Issue → Task

Each task belongs to exactly one parent (a story or issue), and that parent belongs to a sprint. This hierarchy helps teams organize work from high-level initiatives down to actionable daily tasks.

🎯 Best Practices for Creating Tasks

• Keep tasks small: A task should be completable by one person in a few hours to a day, not days
• Be specific: Avoid vague descriptions. "Implement login" is too broad; "Add OAuth2 redirect for SSO" is better
• Assign immediately: Tasks are most effective when assigned to a team member at creation
• Set realistic priorities: Not every task is High priority. Use a clear priority scheme so team members know what to focus on first
• Update status regularly: Move tasks to In Progress when work begins, and mark Completed when done so sprint progress is visible

📌 After Creating a Task

Once your task is created, you can:

• Update task status: Change from Not Started → In Progress → Completed as work progresses
• Add task comments: Leave notes or updates for the assigned team member
• Reassign if needed: Move the task to another team member if priorities change
• Link to test cases: Associate test cases with tasks to define and track quality criteria
• Track in sprint views: See all tasks in your sprint board or backlog to monitor team capacity