Jira Service Desk StrawberryThe comment work, done and queued for one look
Your Jira Service Desk, worked while you do something else: 7 reads to go through it, 4 writes to change it, and a card in front of every one of those changes.
Open the comment. Check it against something else. Write the change. Move to the next one. That is the Jira Service Desk afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a comment until you approve it.
What it can do is exactly what Jira Service Desk exposes to an account you authorise and nothing beyond it: 11 operations, 7 reads and 4 writes. In practice that means it can update issue fields, create request and create an incident, and work across the comments, current users and incidents.
The Jira Service Desk API stops at Jira Service Desk. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the comments or ask you for them?
7 of the 11 operations are reads.
Your account, not a guess at it: a companion can transition request, list sites and list request transitions, and the full list below is the whole list, with nothing inferred from Jira Service Desk's documentation.
The comments are what most of this inventory is about, alongside the current users. A companion can hold all 11 of these operations and forty open tabs in the same pass, which is how an afternoon of Jira Service Desk admin becomes a queue you review.
- Transition Request
- List Sites
- List Request Transitions
- List My Requests
- Get Request
- Get Request Status
- Get Current User
Can it change a comment without asking?
All 4 write operations wait for you.
A companion can update issue fields, create request and create an incident, and each one is staged on an approval card first: you see the comment, the field and the new value before it lands in Jira Service Desk.
Nothing in Jira Service Desk is sent, changed or deleted on your behalf without that click, and a rejected card leaves the comment exactly as it was. The gate is the same one on every surface, described at security.
- Update Issue Fields
- Create Request
- Create Incident
- Create Comment on Request
Does the comment sweep have to be asked for every time?
Yes.
Saved as a routine, the Jira Service Desk comments pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the ticket queue, the Jira Service Desk comments sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents