This guide will help you set up Jira to automatically organize Marker.io issues into the correct stories or epics. Whether you're managing bugs, tasks, or design notes, this setup simplifies the process so you can focus on solving problems.
Prerequisites
Before you start, make sure the following are ready:
Marker.io Integration: Marker.io must already be connected to your Jira project.
Permissions: You need the right permissions to access and modify Jira’s automation settings.
Project Structure: Know how your project is organized, including existing stories and epics.
Setting Up Jira Automation Rules
Jira’s automation tool allows you to automatically sort Marker.io issues into the right stories or epics based on conditions like keywords or URLs.
Step 1: Open Automation Settings
In Jira, go to the Project Settings of the project where Marker.io issues are sent.
Select Automation from the menu on the left.
Step 2: Create a New Rule
Click Create Rule and choose Custom Rule.
Step 3: Set the Trigger
Define the trigger as When: Issue Created.
Step 4: Add Conditions
Click Add Condition to specify when the rule should apply.
Example Conditions:
Issue Type is Bug.
Description contains specific text, such as a URL (e.g.,
www.website.com/about) or a keyword (e.g.,about.php).
Step 5: Define the Action
Add an action: Edit Issue Fields.
In the Additional fields (JSON) section, use the following code to link the issue to a specific story:
{
"update": {
"issuelinks": [
{
"add": {
"type": { "name": "Relates" },
"outwardIssue": { "key": "STORY-123" }
}
}
]
}
}Replace
STORY-123with the issue key for the story or epic you want to link.
Save the rule once the action is set.
Testing and Tweaking the Automation Rules
Step 1: Run Test Cases
Create sample Marker.io issues and check if they are routed correctly.
Step 2: Check the Execution Log
Use Jira’s Rule Execution Log to troubleshoot errors or confirm the rule is working as expected.
Step 3: Refine the Rules
Get input from team members and adjust the rules to fit your project’s needs.
Tips for Managing Stories and Epics
Use Clear Labels: Add descriptive labels to stories and epics (e.g., “Frontend Bugs” or “API Issues”) to make routing easier.
Organize URLs: If your rules depend on URLs, ensure your site or app uses consistent, structured URLs.
Test Your Rules: Run tests with sample Marker.io issues before relying on automation.
Review Regularly: Update rules as your projects evolve to ensure they stay relevant.
Quick Summary
Integrate Marker.io with Jira: Ensure issues are being sent to your Jira project.
Set Automation Rules: Use triggers, conditions, and actions to route issues to specific stories or epics.
Test and Refine: Verify your rules work and adjust them based on feedback.
Stay Organized: Use labels, structured URLs, and regular reviews to keep your Jira workspace clean and effective.