Jira — Triage, File, and Move Tickets From Chat

September 29, 2026

Connect Jira Cloud and the backlog lives in the conversation: search, file, comment, attach, and move tickets through your workflow, including boards and sprints. On the desktop app, a company Jira Server or Data Center behind a VPN works from a saved login — including a bulk export of a queue into files you can open in Excel.

What you can do

• Connect Jira Cloud from Integrations. Enter the site name — the part before .atlassian.net — and sign in. Up to three Cloud accounts. Alfrada OS starts from the signed-in user, so assignees and watchers resolve to the right Atlassian account.
• Search the way you already think. JQL, or plain filters: project, status, assignee, labels, text, dates, sprint. Count a set before you pull it. Open one issue in full, or several at once.
• File work from the chat. Create one issue or a batch, with Markdown in the description. Check the project's issue types and required fields first when the project is strict. Edit, assign, link, and delete are available; each change asks you before it runs.
• Move tickets through the real workflow. List the transitions that issue can take, then apply one. Status names and resolutions come from your site, not a guessed list.
• Comment, watch, and log time. Read and write comments, add or remove watchers, and read or add worklogs.
• Attach the file you already have. Upload a session file onto a ticket, or pull an attachment down into the conversation.
• Run the sprint from chat. List boards and sprints, open a sprint, create one, and move issues onto it.
• Reach an on-prem site from the desktop app. Jira Server and Data Center that are not on atlassian.net use a Vault login on your machine, so the call goes out over your VPN. Search accepts JQL or a pasted queue, filter, or issue link. A large pull uses export: every matching issue lands in the conversation as a CSV, a JSONL, and a zip — with an optional history file for time-in-status and cycle time — instead of paging the whole set through the chat.

Where this shows up

You open the day with a standup and no time to click through the board. Ask for the active sprint: what moved to Done, what is still In Progress and who owns it, and anything blocked or unassigned.

A QA report is sitting in the conversation. One Bug per defect, with steps in the description and priority taken from the report. The list is shown to you before anything is created.

The company tracker is support.company.com on the office VPN, not Atlassian Cloud. On the desktop app, paste the queue link. The matching issues come back as files in the conversation, ready to sort in a spreadsheet.

Try it

• "Show every open bug in PROJ assigned to me, sorted by priority, and move the two oldest to In Progress."
• "Pull the active sprint on the Platform board: what moved to Done since yesterday, what is still In Progress and who owns it, and anything blocked. Keep it to a standup."
• "Read the QA report I uploaded and create one Bug in PROJ per distinct defect — clear summary, steps to reproduce, priority from severity. Show me the list before creating them."
• "Download the latest screenshot on RD-6835 and summarise the comments since Monday."

Heads up

• Cloud and on-prem are different connections. Jira Cloud is an Integration (the site subdomain, then Atlassian login). Jira Server and Data Center are desktop-only: save a Vault login, and the machine has to be on the VPN. A connection error on an on-prem site usually means the VPN is off.
• Creates, edits, transitions, and deletes ask first. Comments, attachments, links, worklogs, and new sprints do too. Reads do not.
• Cloud attachments are capped at 10 MB per file. Larger files need to go up another way.
• Assignees are not display names. On Cloud, people resolve to an Atlassian account id. On Server, the assignee is a Jira username — look the person up before you assign.
• Bulk analysis of an on-prem queue uses export, not page-by-page search. The files land in the conversation. Turn on change history when you need who moved a status, and when.