Customer Actions: Drafts for perfect tickets

There is nothing an agent dreads more than a ticket that says, “It’s broken,” with zero context. Often, the person reporting the issue doesn’t have all the technical details—they need a teammate’s help to fill in the blanks. By using customer actions to create a “Draft” workflow on the Jira portal, you ensure that by the time a ticket hits the queue, it is packed with every piece of data the agent needs.

The Scenario: The “Missing Info” chain

Tom, a Project Admin, needs to report a critical bug in a planning plugin. He knows it’s crashing, but he doesn’t have the SEN license number, and he isn’t exactly sure what the error logs say.

Instead of submitting a “half-baked” ticket that will inevitably lead to a week of back-and-forth emails, Tom starts a draft. He shares the request with Greg (the Site Admin) and Beth (the Dev Lead). They jump into the self service customer portal, add the technical specs and license info, and only then does Tom officially “Submit” the issue to the vendor.

How to set it up: 5 simple steps

Building a “One Source of Truth” within Jira Service Management is a game-changer for complex teams:

1. Set the expectations: Use an announcement banner on the Jira portal to remind users to gather all necessary info (like SEN or instance URLs) before moving a ticket out of draft status.

2. The initial draft: Tom creates the ticket. The workflow is configured so new requests land in a “DRAFT” status by default, hidden from the main agent queues.

3. Invite the experts: Tom uses the native Jira “Share” functionality to add Greg and Beth to the ticket.

4. Team collaboration: Greg and Beth use the Edit Request button (a customer action) to fill in the technical fields. Every edit is logged as a comment, so everyone knows who added what.

5. The big reveal: Once the info is complete, Tom uses a transition button to change the status to “OPEN.” Now, the agent receives a perfect “data package” ready for resolution.

Why it’s a game-changer

No more “Ping-Pong”:

Agents don’t get stuck waiting for basic answers because the data is already there. This is a massive win for incident management in Jira.

Faster SLA resolution:

Since the ticket arrives “ready to work,” the time-to-resolution plummets. Happier customers, happier agents.

Accuracy over urgency:

Allowing reporters to take their time with a draft prevents “rush decisions” and incorrect data entry.

One source of truth:

Side conversations in Slack or email are eliminated. Everything—from the initial bug report to the license details—lives in one place on the Jira customer portal.