Jira Data Center StrawberrySomeone still has to update sprint partially. It does not have to be you
A companion works the 24 operations your Jira Data Center account exposes. It can update a sprint partially and update a sprint fully, and every one of those waits on an approval card showing the board before it changes.
Open the board. Check it against something else. Write the change. Move to the next one. That is the Jira Data Center afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a board until you approve it.
What it can do is exactly what Jira Data Center exposes to an account you authorise and nothing beyond it: 24 operations, 16 reads and 8 writes. In practice that means it can update a sprint partially, update a sprint fully and move an issues to sprint, and work across the boards, issues and sprints.
The Jira Data Center API stops at Jira Data Center. 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.
Which Jira Data Center boards does a companion see?
16 of the 24 operations are reads.
Your account, not a guess at it: a companion can list worklog ids actions, list sprints and list sprint issues, and the full list below is the whole list, with nothing inferred from Jira Data Center's documentation.
The boards are what most of this inventory is about, alongside the issues. A companion can hold all 24 of these operations and forty open tabs in the same pass, which is how an afternoon of Jira Data Center admin becomes a queue you review.
- List Worklog IDs Actions
- List Sprints
- List Sprint Issues
- List Resolutions
- List Issues Without Epic
- List Epics
- List Epic Issues
- List Boards
- List Board Issues
- Get Worklogs by ID
- Get Updated Work Logs
- Get Sprint
- Get Server Info
- Get Resolution
- Get Issues From Backlog
- Get Board
What happens before it can update sprint partially?
All 8 write operations wait for you.
A companion can update a sprint partially, update a sprint fully and move an issues to sprint, and each one is staged on an approval card first: you see the board, the field and the new value before it lands in Jira Data Center.
Nothing in Jira Data Center is sent, changed or deleted on your behalf without that click, and a rejected card leaves the board exactly as it was. The gate is the same one on every surface, described at security.
- Update Sprint Partially
- Update Sprint Fully
- Move Issues To Sprint
- Move Issues To Backlog
- Delete Sprint
- Create Future Sprint
- Create Filter
- Create Board
Can the boards pass run every Monday?
Yes.
Saved as a routine, the Jira Data Center boards 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 operations, the Jira Data Center boards 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