There is no ScreenApp Jira integration
ScreenApp does not connect to Jira. There is nothing to install in Jira, nothing to connect under Settings, and ScreenApp does not post, sync or create anything in Jira on its own. Anything that ends up in Jira gets there because you put it there.
That is worth saying plainly, because the rest of this page is about the part that does work.
What you can actually do
- Record the meeting in ScreenApp, or upload a file you already have.
- Wait for the transcript and the AI summary.
- Copy the text, or export the transcript as PDF, DOCX, TXT, SRT and VTT.
- Paste the summary into the issue description and add the share link so a developer can watch the reproduction.
- If people need to watch the recording, send them a share link. Share links are not password protected, so only send them to people who should see the recording.
Why this is still worth doing
Record the bug happening and talk through it. ScreenApp transcribes the voiceover and the AI writes it up as a summary you can drop straight into the description. The AI also reads the video frames, not just the audio, so what was on screen makes it into the write-up. ScreenApp does not capture browser console logs.
For developers
ScreenApp has API keys and a public API. You can generate an API key and pull a recording, its transcript and its summary, then write them into Jira with Jira’s own API. Use the API to retrieve recordings. ScreenApp does not offer webhooks, so your code or automation service checks the API for finished recordings and writes them to the destination; this is not a native integration.
Frequently asked questions
Can a recording create an issue automatically?
A custom workflow can do this. ScreenApp does not offer webhooks, so your automation polls the ScreenApp API for finished recordings, retrieves the summary, and creates the Jira issue. Configure authentication and field mapping for your Jira project.
Do I have to upload the video to Jira?
No. Paste a share link. Share links are not password protected, so treat them as readable by anyone who has the URL.