When reporting feedback or bugs, you might encounter multiple related issues on the same page or within the same feature. To keep your reports organized and actionable for your team, it's crucial to link these related items together.
This guide outlines the best practice for organizing related issues in Marker.io using a parent-child structure with subtasks.
Moving to a Subtask Workflow
Previously, you might have used the "Attach to Existing" feature to link related reports. This feature is now being deprecated.
Why the change? We've found that most development and project management teams prefer a more structured parent-child ticket setup. Using subtasks provides a clearer hierarchy, improves organization, and prevents smaller, related issues from getting lost. This method aligns better with workflows in popular integrations like Jira, ClickUp, and others.
How to Group Related Issues (Parent-Child Style)
If you’re using Marker.io with tools like Jira, you can organize tickets using a parent-child structure. Here’s how:
Create a Parent Ticket
Start by logging the main issue. This ticket will act as the "parent."
For example, if you encounter a problem like a broken "Contact Us" button on your homepage, you could name the ticket "Homepage Issue."
Create Child Tickets for Related Problems
If you find another issue on the same page, like a broken link, create a new ticket for that specific problem.
Example:
Child Ticket Title: Broken link on Homepage
Issue Type: Sub-Task
Link it to the Homepage Issue ticket
Why Use the Subtask Method?
Adopting this parent-child structure for organizing issues offers several key benefits:
Keeps Everything Organized: It creates a clean and logical hierarchy for your issues.
Improves Clarity for Developers: Developers can easily see the full context of a problem and how different pieces of feedback are related.
Prevents Lost Issues: It ensures that smaller, but still important, problems that are part of a larger issue are not overlooked.
Streamlines Project Management: It aligns with standard practices in most project management tools, making it easier to track progress and manage workloads.