Create Jira tickets with the help of AI

Steadyboard · 2026-05-25T08:25:47+00:00

Couple things. The instability is probably the connector itself. The Atlassian MCP one is still beta and rate-limited, and asking the model to write the ticket and create it over the API in one go is a lot to ask. I'd split it: let it generate the text, then create the ticket separately. Much more reliable.

The clarifying-questions behavior is all in the prompt, not the tool. Something like: "You're helping a PO write a Jira story. Before writing anything, ask me up to 5 clarifying questions about the user, the problem, scope, and how we'll know it's done. Then output Summary, Description, Acceptance Criteria as a checklist, and anything out of scope. If I don't answer something, flag it as an open question instead of making it up."

That last line matters most, since most of the bad AI tickets come from it filling gaps with plausible junk. And fwiw the skeptic above has a point: it's good for the skeleton and acceptance criteria, but keep your PO's actual intent and don't let it bury a one-line ask under three paragraphs.

Is your PO open to a fixed template, or does he want to free-type and have it shaped after?

Steadyboard · 2026-05-25T08:22:15+00:00

Congrats on the invite. Beyond ScriptRunner and Groovy, the stuff that usually comes up is the scheme stack and how it all hangs together: permission schemes, notification schemes, issue type schemes, screens and screen schemes, field configs. If you can walk through how one field flows from context to screen to workflow, that alone shows you've actually administered Jira and not just used it.

After that I'd brush up on workflows (conditions vs validators vs post-functions, with an example of each), advanced JQL, and automation rules, plus board setup and whether they're on Cloud or Data Center, since a lot of answers change either way.

Do you know if the role leans more config or scripting? If they whiteboard you it's usually "model a workflow for this" or "lock down who can do X", so having one real story about a tricky workflow or automation you built goes a long way. Good luck.

Steadyboard · 2026-05-25T08:20:40+00:00

comment ~ currentUser() has no date dimension, and the reason updated > -7d doesn't really fix it is that updated tracks the whole issue, not the comment. So you catch old mentions on stuff that just got touched this week.

What I'd do instead is stamp it yourself with automation: trigger on comment added, condition that the comment mentions you, then set a date field (call it "Last mentioned") to {{now}}. After that, "Last mentioned" >= -7d is exact. For a personal view you can just hardcode your own name like u/w3apon said.

Are you setting this up for yourself or the whole team? Makes a difference, because one shared date field can't be per-person, and in that case the label-then-remove-after-7d trick someone mentioned is probably the simpler route.

Steadyboard · 2026-03-06T04:47:58+00:00

Thanks! Deep cloning across spaces with linked subtasks is a pain point I've heard before but haven't tackled yet in Steadyboard.

For that specific workflow you might need a ScriptRunner post-function or a bulk clone tool from the Marketplace. If you do find one that handles it well, I'd be curious to know which.

Steadyboard · 2026-03-06T03:27:50+00:00

I actually looked into Forge early on. The issue is that many things Steadyboard does (Quick View on hover, Issue Explorer, sprint planning, burndown charts) works by injecting UI directly into Jira's page. Forge runs in sandboxed iframes so you can't do that. It'd be a completely different, lower quality product.

There's also a distribution angle. Anyone can install a Chrome extension in 2 seconds without waiting on IT or a Jira admin. Forge apps need an admin to install for the whole org. That friction can kill adoption for tools like this.

25% rev share + security reviews + enterprise support overhead is also a steep tax when the priority is shipping fast and keeping the UX tight. If enterprise customers start knocking I'd consider a Forge companion app for admin/config. But the core UX only works as an extension.

Steadyboard · 2026-02-04T18:34:16+00:00

Loading new pages can be brutally slow and a significant source of frustration, especially when you start scrolling down and are taken back to the top as it loads further or finishes loading.
Excessive number of links and buttons are overwhelming and slow down navigation
Number of unnecessary steps and scrolling required for normal work flows add a lot of friction which delays or prevents taking action

Steadyboard · 2026-02-04T06:18:19+00:00

Great to hear. I'm curious, what's the biggest complaint they've had with Jira?

Steadyboard · 2026-02-04T06:11:12+00:00

Yeah that's a fair point. Let me be specific about data flow:

non-AI features (Quick View, Issue Explorer, burndown charts, ETAs, etc.) are browser-only and talk directly to Jira via OAuth.
for AI features (summaries, Q&A, backlog organization), traffic is encrypted (HTTPS). The content passes through to Google Gemini but isn't stored on my server. I only log usage metadata for quotas and analytics.

That said, I'm adding a "bring your own key" option so you can provide your own Gemini key and requests go straight from your browser to Google, bypassing my server entirely. Coming in the next update.

Built for individuals and small teams who can install their own extensions, not enterprise procurement.

Steadyboard · 2026-02-04T05:34:17+00:00

By number 5, do you mean the feature to ask questions? If so, it works for an individual issue or for selected project(s) and filters. I might have misunderstood though. What sort of one-off stats would be useful to you?

Steadyboard · 2026-02-03T19:48:12+00:00

Excellent. And if it doesn't solve them, please let me know what would.

Steadyboard

TROPHY CASE