Hey Everyone,
I just came across this post Jira MCP Explained: What It Does, What It Doesn’t, and How to Use It - Atlassian by @Olga Cheban _TitanApps_ today, and I liked it so much, I decided to do a little remixing on it that I can hopefully share at an AUG meeting in the near future.
On this one I selected infographic and let remix select which one for me.
I took this text -
6 Tips for using Jira MCP effectively
Once your team is past the setup phase, the difference between getting decent results and great results usually comes down to how you write prompts and structure your usage:
- Give the AI default context to avoid repeating yourself. Jira MCP works best when the AI already knows your project key, your account ID, and your usual filters. Add these defaults to your AI client's system instructions or rules file. After this, prompts like "show me my open work items" or "create a bug in the current project" will work without you having to specify the project key or your email every time.
- Be specific about the scope. The AI assistant works far better with narrow questions than broad ones. “List all bugs in the Payments project from the last 14 days” is a good prompt. “Tell me about our bugs” is not. AI translates your request into a JQL query under the hood. The more specific your prompt, the more accurate the query. Include project keys/names, time windows, and labels whenever you can.
- Ask the AI to search before creating. Duplicate work items clutter the backlog and confuse the team. Before creating a new ticket, instruct the AI to search for existing ones first. A good prompt is: "Check if there is already a work item about login errors on mobile. If yes, add a comment with the new details. If not, create a new bug." This pattern prevents duplicates and keeps related context in one place.
- Use MCP for triage and reporting, not just ticket creation. Many teams start with Jira MCP to create work items faster. The bigger win is in reporting and triage. You can ask for velocity trends, cycle time per engineer, overdue work items by team, or unestimated stories across multiple projects. These reports usually require building JQL filters and exporting to a spreadsheet. With MCP, you get them in seconds with a single prompt.
- One MCP server per goal at first. If you are new to MCP, start with just the Jira server before connecting others. It is easier to debug a single connection, and you will build a clearer sense of what the server can do before adding more sources.
- Watch the rate limits. Jira uses a points-based quota, and a single MCP prompt often fans out into multiple API requests in the background. Wide-scope queries and bulk writes drain the quota quickly. It can be helpful to split bulk writes into smaller batches.
and used the timeline feature to produce -
It originally had step 1-6 along the left-hand side, but as these weren't steps, and because I was in edit mode for the page, I could ask rovo to remove that text, and get what you see before you.
That's the biggest take away, experiment in edit mode even with remixes you don't think would necessarily work, ask rovo to modify, you might just be surprised on the results.
Name: Clint Young
Job Title: Senior Project Manager
Company Name: SEL
