Updating Issues

Updating Issues

Most of the work on an issue happens after it is created. Quickly handles those updates from the conversation where the news actually arrived.

Changing Status

@Quickly move PROJ-123 to In Progress
@Quickly mark PROJ-123 as Done
@Quickly resolve PROJ-456

Status changes go through your project's workflow transitions, so the target status has to be one your workflow allows from the current state. If it is not, Quickly tells you which transitions are available rather than failing silently.

Adding Comments

@Quickly comment on PROJ-123: root cause is the expired session cookie, fix is in review

Comments are the most common way teams keep a ticket current from a thread, because the context is already written and only needs forwarding.

Reassigning

@Quickly assign PROJ-123 to michael@example.com
@Quickly unassign PROJ-456

The assignee is matched by searching your Jira users for the name or email you provide. Email is the unambiguous option when two people share a first name.

Changing Fields

@Quickly set PROJ-123 to Highest priority
@Quickly rename PROJ-123 to "Session cookie expires early on Safari"
@Quickly update the description on PROJ-123 with the timeline from this thread

Summary, description, and priority can all be updated in one request or separately. Priority accepts Highest, High, Medium, Low, and Lowest.

Related Issues and Time

Quickly can also link issues to each other, add watchers, and log work against an issue:

@Quickly link PROJ-123 as blocked by PROJ-99
@Quickly add me as a watcher on PROJ-123
@Quickly log 2 hours against PROJ-123 for the Safari investigation

What Is Not Supported

Quickly updates issues one at a time. It can create several issues in a single request, but there is no bulk edit across a query result. For a change that has to sweep dozens of issues, use your tracker's own bulk change tool.

Approval and Logging

Updates are write actions. In Conservative mode each one shows a confirmation card with the issue key and the exact fields being changed before anything is sent. In Balanced mode routine single-issue updates run automatically.

Whichever mode you use, the update lands in Action Logs with the tool call, the outcome, and a link to the issue. When a status change is rejected by the workflow, the log carries the tracker's error, which usually names the transition that was not permitted.