Draft a Jira ticket without inventing the scope
Someone says "can we raise a ticket so we don't lose this?" and twenty minutes later there's a work item with an owner, a deadline and three acceptance criteria nobody ever agreed to.
What you'll make
one Jira work-item draft that keeps the reported problem, explicit commitments, unselected ideas and open questions in separate sections, checked before anything is created.
What you'll need
Rovo turned on for your Atlassian site (Rovo credits come with paid Jira and Confluence cloud subscriptions, and an organisation admin enables it), permission to use the conversation, and permission to create items in the Jira space. About 20 minutes.
Example result.
Summary: Investigate reported CSV export timeout
Commitment: Priya will check the logs. No deadline stated.
Proposal: pagination might help. Not selected.
Open questions: which account timed out; can it be reproduced; expected behaviour.1. Give Rovo the whole conversation
In Jira, select Ask Rovo in the top navigation near your profile picture (or the Rovo button at the bottom right). For a short discussion, paste the text with speaker names and dates. Include the replies that accepted, rejected or changed a proposal, not only the message asking for a ticket.
You can also add context with the + at the bottom left of the chat: a file, a link or the current page. Rovo can read most text, document and spreadsheet files, but not images, video, audio, archives or Apple Pages, Keynote and Numbers files. A screenshot of a Slack thread is, for these purposes, not a conversation. Reading a link depends on a supported connection, so a pasted URL isn’t proof that Rovo read it.
Leave out passwords, customer secrets and personal details the ticket doesn’t need.
Why this works: the replies are where a suggestion gets accepted or dropped. Without them, every idea looks equally agreed.
What you should see: the full thread in the chat, with names and dates.
2. Ask for a draft with sections that keep things apart
Draft one Jira work item from the conversation below. Do not create, assign, update or publish anything.
Use these sections:
- Problem reported: the observed or reported issue. Distinguish reports from confirmed findings.
- Explicit decisions and commitments: quote the message and name the speaker. A request or suggestion is not a decision.
- Proposed solutions: ideas that haven't been selected.
- Open questions: what's needed to establish scope or investigate.
- Source: conversation title, date range and link if supplied.
Do not invent an assignee, priority, estimate, deadline, performance target or acceptance criterion. Include an acceptance criterion only if the source explicitly sets one. Mark missing information as not stated.
Conversation:
[pasted messages]Why this works: acceptance criteria are where invented scope lives, because they’re the part of a ticket that most rewards fluent invention. Quoting each commitment lets you check it against the message.
What you should see: five sections, with a quote and a name beside every commitment.
3. Check the draft against the messages
For each line, ask:
- Is this a report, a confirmed finding or a hypothesis?
- Did this person accept investigation, implementation or neither?
- Is the number an observation or a target?
- Is the proposed solution actually selected?
- Has an open question been handed to someone without evidence?
Accurate quoting and correct interpretation are separate checks. A question can be quoted perfectly and still sit under “Agreed”.
Why this works: the risky errors look reasonable, which is why each line needs its source message.
What you should see: every line traced to a message, and anything unsupported marked for repair.
4. Create only the checked item
Rovo Chat can create one Jira work item at a time. It doesn’t create several at once or subtasks. Ask for the specific action:
Create one Jira work item in [space], using the checked draft above. Use work type [type]. Do not add an assignee, sprint, estimate, priority or due date beyond values I have explicitly supplied. Show any required fields that still need my choice.[space] is the Jira space or project, and [type] the work type, such as Task.
Check the destination, work type, required fields and content before confirming. Atlassian says skills typically ask for confirmation, but don’t rely on every workflow pausing. Then open the item, check it matches the draft, and keep the source link in the description. Your Rovo chat is private to you and kept for 30 days, so it’s no substitute for a source record in Jira.
Why this works: creating is the step with consequences. Doing it last, from a checked draft, keeps it small.
What you should see: one new work item that matches the draft, with no fields you didn’t choose.
Check the result
- Every commitment quotes its message and names the person who made it.
- No number appears as a target unless someone set it as one.
- Unselected ideas are under Proposed solutions, not in the work description.
- No assignee or deadline appears that the thread didn’t state.
The usual failure: a narrow commitment grows into ownership. “I’ll check the logs” becomes “owns the fix”, and an observed time becomes a target. Spot it by reading each commitment against the exact words in the thread.
The draft says "[line]". The source only says "[source wording]". Revise that item to match the source and keep [proposal, target or owner] unconfirmed. Show the changed sections without creating a Jira item.[line] is the draft’s wording, [source wording] is the message, and the last placeholder names what must stay unconfirmed.
Worked example: a timeout without a promised fix
Fictional example.
Rhys: Three people reported slow CSV exports this week. One reported a timeout.
Priya: Our largest account takes about 40 seconds, but I haven't reproduced the timeout.
Rhys: Do we know which account timed out?
Priya: Not yet. I'll check the logs.
Tom: Could pagination help?
Rhys: Possibly. Can we raise an investigation ticket so we don't lose this?The first draft’s commitments section said: “Priya owns a ten-second pagination fix by Friday.”
- The failure. Four inventions in one line: ownership of a fix, a ten-second target, pagination as the chosen solution and a Friday deadline. Priya only said she’d check the logs.
- The repair. The repair prompt, keeping “pagination, target and owner” unconfirmed, produced the draft in the example result. The 40 seconds stays as reported context, not a goal.
- The request. Rhys asked for an investigation ticket. Nobody in the excerpt accepted it, so the draft doesn’t say who will investigate.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: update the draft when the thread moves on
Two more messages arrive:
Rhys: Priya, can you own this?
Priya: I can look at it after the release on the 14th.That’s a conditional acceptance with a date: Priya will investigate after the 14th. It’s still not ownership of a fix, and there’s still no deadline for finishing. Update the commitments section with the new quote, and keep “fix owner: not stated” and the open questions as they were.
Optional training: separate investigation from implementation
An investigation can have a useful deliverable without presupposing the answer: affected cases, reproduction attempts, relevant logs and a recommended next decision. Once the team agrees those outcomes, Rovo can phrase them:
Turn the following agreed investigation outcomes into clear completion criteria. Keep their scope. Do not add implementation work or numeric targets. List any ambiguity separately.
[agreed outcomes]Optional training: split a thread that mixes several problems
If one conversation covers several issues, ask Rovo to identify the distinct problems and the messages behind each, without creating anything. Choose the split with the team. A longer backlog isn’t evidence of clearer scope. Turn a Slack discussion into a canvas of decisions and open questions covers keeping decisions and open questions visible before anyone raises tickets.