How to Update Jira Tickets Automatically (Stop Doing It Manually)

Updating Jira tickets is one of those tasks that feels small but adds up fast. A comment here, a status change there, a new context note after a meeting. Done manually, it’s 30-60 minutes of work per day that most PMs and engineering managers didn’t sign up for.

Here’s how to do it faster, and how to stop doing most of it yourself.

Updating a Jira Ticket Manually (The Basics)

If you’re newer to Jira, here’s how the basic inline editing works:

Status: Click the status button at the top of the ticket (usually shows the current status like “To Do” or “In Progress”). A dropdown shows your available transitions.

Fields: Most fields on a ticket are inline-editable. Click on the assignee, priority, story points, or label fields directly to edit them. The changes save immediately.

Comments: The comment box is at the bottom of every ticket. Use @ to mention someone, and // to reference another ticket. Comments are visible to everyone on the project.

Description: Click the description area to edit. Jira uses a rich text editor with formatting support.

Bulk updates: If you need to update multiple tickets at once, use the backlog view, press Z to enter bulk select mode, and apply changes across all selected issues. See our guide on bulk editing Jira issues for the full workflow.

Updating Tickets from Jira Automation Rules

For recurring updates, Jira’s native automation engine handles them without anyone touching a ticket.

Status transitions on schedule:

Trigger: Scheduled (daily at 9am)
Condition: Status = "Waiting for Feedback" AND Updated <= -3d
Action: Add comment "Reminder: This ticket has been waiting for feedback for 3+ days"
Action: Assign to PM

Auto-update when a related issue changes:

Trigger: Linked issue status changes to "Done"
Condition: Link type = "Blocks"
Action: Transition current issue to "Unblocked" (custom status)
Action: Notify assignee

Update fields when an issue is moved:

Trigger: Issue moved from sprint X to sprint Y
Action: Update "Target Sprint" custom field
Action: Post Slack notification to assignee

These rule-based updates are reliable for predictable patterns. The catch: they only respond to events that already happened inside Jira. They can’t read your meeting notes or Slack messages.

The Bigger Problem: Context That Never Gets Added

The most expensive Jira update isn’t changing a status field. It’s the context update that never happens.

You had a standup where the team decided to deprioritize a feature. The ticket stays marked High priority.

You got new information in a customer call that changes the scope of a story. The ticket description still has the old requirements.

A Slack conversation in #engineering resolved a question about implementation approach. The ticket has no record of it.

These gaps aren’t solved by manual edits or automation rules. They require someone to connect the dots between what was said and what’s in Jira - and then actually update the tickets.

Automatically Updating Jira Tickets from Meetings

This is what Telos was built for.

After every standup, planning call, or product review, Telos:

Reads the meeting transcript and identifies which existing Jira tickets are relevant to what was discussed
Cross-references the discussion against your current backlog, previous meetings, and Slack context
Proposes specific updates - adding meeting context to a ticket’s description, changing priority based on what was said, updating acceptance criteria after a scope discussion
Sends a batch proposal to Slack - “Based on today’s call, here are 5 ticket updates I want to make. Approve all or review individually.”
Executes approved updates in Jira immediately

This isn’t a chatbot you have to prompt. Telos runs automatically after each meeting and pushes the proposed updates to you. You review and approve. The tickets get updated.

A Comparison

Approach	Good for	Not good for
Manual inline editing	One-off updates, adding comments	Anything that should happen regularly
Jira automation rules	Status transitions, notifications, scheduled tasks	Unstructured context from meetings/Slack
Telos AI agent	Capturing meeting context, cross-referencing decisions, bulk proposals	Simple field transitions

Getting Started

For basic updates: Jira’s inline editing is already there - no setup needed. The bulk edit mode (press Z in the backlog) helps when you need to update multiple issues.

For rule-based automation: Go to Project Settings - Automation - Create rule. Atlassian has a library of automation templates worth browsing.

For meeting-driven updates: Connect Telos to your workspace. It integrates with Jira, your meeting tool, and Slack. Setup takes about 15 minutes. After your next standup, you’ll get a Slack message with proposed ticket updates for your review.