Termiyo
Cloud Login
← All solutions

Solutions

Link a terminal session to a Jira issue

The proof of what you did on the server lands on the ticket, without copying terminal output by hand or pasting a secret by mistake.

Termiyo can link the terminal session you are working in to a Jira issue. When the session ends, it shows you the output, cleaned and with anything that looks like a secret withheld, and attaches exactly that text to the issue only when you press Attach. Use it when a ticket needs proof of what was done on a server. Withholding is best effort, so read the output before you attach it.

Link the session to the issue you are working on. When the session ends, Termiyo shows you its output, cleaned and with anything that looks like a secret withheld, and attaches exactly that to the issue when you say so — or nothing, if you discard it.

Recorded in Termiyo against a test server and a stand-in for a Jira site, both on the recording machine, with a test token. No real Jira site, issue or account is used.

Steps

  1. Connect your Jira site

    Press “Link to a Jira issue” — the Jira button on the server’s tab bar, or its row in “All tools”. The first time, fill in the site, your email and an Atlassian API token and press “Connect”; the token is kept in your vault.

  2. Link the session to an issue

    Search by key or words, choose the issue and press “Link”. The Jira button then says which issue the session is linked to, with “Unlink” beside it.

  3. Review what will be attached

    When the session ends, “Attach this session to SER-1?” (with your issue’s key) opens by itself with the output cleaned and secret-looking matches withheld, and says how many were. Nothing is sent until you press “Attach”; “Discard” sends nothing.

  4. Attach it

    Press “Attach”. The file on the issue is exactly the text you reviewed. Tick “Also add a comment: host, times, how it ended” to say where it came from.

Good to know

  • Withholding is best effort: only known secret shapes are caught, so read what is left before attaching.

Transcript

The proof of what you did on the server lands on the ticket, without copying terminal output by hand or pasting a secret by mistake.

Connect your Jira site once, with your own API token, kept in your vault.

Link the session to the issue you are working on. The Jira button then says which issue it is.

When the session ends, secret-looking text is withheld before anything leaves your computer.

Attach it, and the ticket gets exactly the text you reviewed.