Customer Actions: Easy ticket edits

We’ve all been there: you hit “Submit” on a request only to realize a split second later that you misspelled a critical license key or attached the wrong log file. Usually, this leads to a messy trail of “oops” comments or, worse, a duplicate ticket. By using customer actions to enable an Edit Request button, a standard Jira portal becomes a truly reactive customer self service portal.

The Scenario: The “John” Incident

John is a Jira Admin who is currently updating an app. He’s juggling three different tasks and accidentally mistypes a license key when submitting a support ticket.

Without an edit option, John would have to add a comment - which might be missed by an agent - or wait for the agent to ask for the correct key. With customer actions, John simply clicks a button, fixes the field, and moves on with his day. No clutter, no confusion.

How to set it up: 4 simple steps

Building this workflow within Jira Service Management takes just a few minutes:

1. Design the action: In the app configuration, create a new form named Edit Request.

2. Select the fields: Choose which fields John should be able to change (e.g., Description, License Key, or Priority).

3. Assign to portal: Add the action to the relevant project and request types so the button appears on the request details view.

4. Automate the sync: (Optional) Set up a quick automation rule so that when John updates the portal, the internal ticket reflects the change immediately.

Why it’s a game-changer

Zero uncertainty:

Users no longer have to wonder if an agent saw their “correction” comment. The data is updated right at the source.

Clean queues:

Agents spend less time deciphering contradictory information in comment threads and more time on actual incident management in Jira.

Empowered users:

Providing the tools for self-correction makes the self service customer portal feel more professional and reliable.