Create WM Issue
Published on August 24, 2026 Agile Manager
Creating a WM Issue
A WM Issue is used to log, track, and manage blockers, bugs, defects, or unexpected challenges that arise during your projects and sprints. Issues help your team quickly identify problems, escalate them to the right people, and ensure nothing falls through the cracks. Issues can be created from sprints, stories, or anywhere in Agile Manager.
🛠 Create a New WM Issue
Follow these steps to log an issue:
- Open Agile Manager
Click the App Launcher (9-dot grid icon) and select Agile Manager. - Navigate to Issues
Click the WM Issues tab in the navigation menu, or locate the Issues related list on a sprint or story record. - Click New Issue
Click the New button in the top right corner to open the issue creation form.
- Fill in Issue Details
Enter the following information:- Issue Title/Summary: A clear, concise description of the problem (e.g., "Login page crashes on mobile")
- Issue Type: Select Bug, Blocker, Tech Debt, or Enhancement
- Description: Provide detailed context about the issue, steps to reproduce, and expected behavior
- Severity/Priority: Set as Critical, High, Medium, or Low based on impact
- Assigned To: Assign to a team member responsible for resolving the issue
- Status: Mark as New, In Progress, Resolved, or Closed
- Related To (Optional): Link to a story, sprint, or project that the issue affects
- Save the Issue
Click Save. The issue is now logged and can be tracked until resolution.
📌 Next Steps After Creating an Issue
Once your issue is created, you can:
- Add Comments: Team members can discuss the issue and share updates
- Create Tasks: Break the issue resolution into smaller tasks
- Link Related Records: Connect the issue to stories, sprints, or other issues
- Update Status: Change status as work progresses (In Progress → Resolved → Closed)
- Track in Dashboard: Monitor open issues and blockers in your sprint dashboard
💫 Issue Types and When to Use Them
- Bug: Unintended behavior or defect in the code that needs fixing
- Blocker: Something stopping progress on a story or sprint (e.g., waiting on external resource)
- Tech Debt: Refactoring, cleanup, or improvements to code quality
- Enhancement: Improvement or nice-to-have feature request
🚛 Issue Priority Guide
- Critical: Blocks the entire sprint or affects production. Must be resolved immediately.
- High: Significantly impacts functionality or user experience. Should be resolved this sprint.
- Medium: Noticeable issue but has a workaround. Can be addressed in the current or next sprint.
- Low: Minor cosmetic or edge-case issue. Can be addressed when capacity allows.
❓ Troubleshooting
Can't find the WM Issues tab? Make sure you have the Agile Manager User permission set assigned. See How to Assign Permission Sets in Agile Manager.
Can't assign the issue to a user? Only active users who have the Agile Manager User permission set can be assigned issues. Verify the user has the correct permissions.
Issue not saving? Check that all required fields (marked with *) are filled in. Issue Title and Priority are typically required. Contact support at info@codeylabs.com if issues persist.
Knowledge Article Number: KA-00362