Send beta tester feedback to Linear and Jira without retyping

A tester finds a bug in your beta build, takes a screenshot and sends it to you in a direct message with the words "this screen looks wrong". You forward it to the team chat. Someone creates a Jira issue from memory two days later, without the screenshot, without the phone model and without the build number. When a developer finally picks it up, the build has changed twice and nobody can tell whether the bug is still there.

This guide is about the step between a tester report and a tracker issue. It covers what gets lost when beta feedback travels by chat and email, what a Linear or Jira issue made from a tester report should contain, four ways to connect the two with honest trade offs, and a simple triage flow. At the end it shows how AppForShare sends tester reports to Linear and Jira with one button, from the dashboard, the CLI or an AI assistant.

Where testers report and where developers work

Testers report wherever it is easiest for them: clients by email, internal testers in Slack or Microsoft Teams, outside testers with screenshots in a direct message. Developers plan and fix work in a tracker such as Linear or Jira.

Every time a report is retyped or forwarded, details drop out. The ones that go missing most often are also the ones a developer needs first:

• Device and OS. "On my phone" is not a device. Many mobile bugs exist only on one OS version, one screen size or one manufacturer.
• Build. Without the version and build number, nobody knows if the bug was already fixed in a later build.
• Screenshot or recording. Images stay in the chat they were sent in. The issue gets a description of the image instead.
• Steps. The tester knew what they tapped. The person writing the issue a day later does not.
• Who reported it. When the developer has a question, there is no clear way back to the person who saw the bug.

The fix is to capture those facts once, at the moment of the report, and carry them into the issue without retyping.

What a good tracker issue from a tester report contains

An issue made from a tester report should let a developer start work without going back to the tester. That needs a few fixed parts.

• A title that says what and where. A useful pattern is a type tag, a short summary and the build, for example "[Bug] Checkout button does nothing (Shop 2.5 (121))". The type tag helps filtering, and the build in the title makes stale issues easy to spot.
• Steps to reproduce. Numbered, starting from a known point such as opening the app or signing in.
• Expected and actual result. What should have happened and what happened instead, with any on screen message word for word.
• Device, OS and build. Model, OS version, screen size and the exact build the tester had installed.
• Screenshots or a recording. Attached to the issue itself, not linked to a chat that half the team cannot open.
• A link back. To the original report or to the tester, so questions go to the right person.

Here is a template you can paste into a Jira issue description or a Linear issue:

[Bug] [what broke, where] ([app] [version] ([build]))

Reported by: [name or email], [date]
Build: [version] ([build number])
Device: [model], [iOS / Android version], [screen size]

Steps to reproduce
1. [open the app / sign in as ...]
2. [...]
3. [...]

Expected: [what should happen]
Actual: [what happened, exact message if any]
How often: [every time / sometimes / once]

Attachments: [screenshots / screen recording]
Original report: [link]

The guide on collecting tester feedback with screenshots has a tester side version of this template.

Four ways to get beta feedback into Linear or Jira

1. Copy and paste

Someone on the team reads each report and creates the issue by hand. It needs no setup and works with any tracker. It also gives a natural triage step, because a person decides what becomes an issue. The cost is time and accuracy: screenshots have to be downloaded and uploaded again, device details are easy to skip, and the work tends to pile up before a release.

2. Email to the tracker

Linear offers an email intake address, and Jira can create issues from email depending on your plan and setup, so reports can be forwarded from a shared inbox. Setup is light and attachments usually come along. The downside is that the issue is only as good as the email. Testers still forget the build and device, subject lines become titles, and every reply or out of office message can turn into noise in the tracker.

3. Webhooks and Jira Automation

If your build sharing or feedback tool sends webhooks, Jira Automation can receive them with an incoming webhook rule and create issues from the payload. Linear can be reached the same way through its API or an automation service. You choose the fields, the project and the rules, but you build and maintain the mapping, handle attachments yourself, and decide how to stop every single report from becoming an issue, which often defeats the triage step.

4. A direct send to tracker button

Some feedback tools connect to Linear or Jira and add a button on each report. A person still decides which reports to send, but the issue is created with the device facts, the build and the attachments already filled in. Setup is a one time connection by an admin. The limits are that you depend on what the tool puts in the issue, and most such links are one way: changes in the tracker do not flow back on their own.

A triage flow that keeps the tracker clean

Send what needs work, not everything

Not every report belongs in the backlog. Bugs that need a code change go to the tracker. Ideas can be collected and reviewed in batches, or added as one issue per theme. Duplicates, questions and "works as intended" reports should be resolved in the feedback inbox with a short note and never reach the tracker.

Check for duplicates first

Before sending, search the tracker for the screen or feature name. If an issue exists, add the new device or build to it as a comment instead of opening a second one.

Decide who owns it

Pick one person per beta round, often a lead developer or QA, who reads new reports daily and decides what to send. When everyone can send, issues get created twice or not at all.

Mark blockers early

Decide whether a report blocks the release when it arrives, not on release day. Crashes on main flows, data loss, and blocked sign in or payment usually do. Layout and wording usually do not.

Close the loop with the tester

When the fix ships in a new build, tell the tester and ask them to check it again. Most links between feedback tools and trackers do not do this for you, so it is a manual step.

How it works in AppForShare

AppForShare shares iOS and Android test builds through an install link and QR code. Testers send feedback from that install page, so there is no SDK in your app. A report holds a message, up to 5 screenshots the tester can draw on (every plan with an account) and, on Pro and Team, one screen recording. The device, OS, model, screen size and build come with every report. See tester feedback for the tester side.

Connect Linear or Jira

On Pro and Team, an Admin opens Dashboard, Integrations. For Linear, they paste a personal API key and pick a team. For Jira Cloud, they enter an Atlassian account email and an API token, then pick a project and an issue type. Only Jira Cloud sites at yourteam.atlassian.net are supported. Keys are stored encrypted.

Send a report

On any report in the feedback inbox or on a build page, a Developer presses Send to Linear or Send to Jira. AppForShare creates the issue with a title such as "[Bug] first line of the message (App 2.5 (121))". The description holds the full message, the device facts (app, platform, device and OS, screen, language, country, who sent it, when, and the install page link) and a link back to the report. Screenshots and recordings up to 20 MB each are attached: as attachments in Jira, and uploaded to Linear and embedded in the issue. The report then shows the issue key and a link to it.

A report is sent once. The link is one way: status changes in Linear or Jira do not come back to AppForShare, and resolving a report in AppForShare does not close the issue. Telling the tester about the fix is still up to you. More detail is on the Linear and Jira feature page.

From the CLI and AI assistants

The same step works from a terminal or a script:

npx appforshare feedback
npx appforshare send-feedback 1234 --to linear
npx appforshare send-feedback 1234 --to jira

The first command lists reports, and the other two send report 1234 to the connected tracker. The CI guide covers setting up the CLI. The AppForShare MCP server has the tools list_feedback and send_feedback_to_tracker, so an assistant such as Claude can read new reports and send the ones you choose. Sending asks for confirmation first. Setup is in the MCP docs.

Without an integration

On every plan, Copy for an issue on a report copies plain text you can paste into any tracker. On Pro and Team, the feedback.new webhook event can post new reports to your own endpoint. The Jira guide shows Jira Automation with an incoming webhook for new builds and store rejections, which you can use alongside the button.

Release blockers

On Team, a report can be marked as a release blocker. With a release checklist, open blockers hold the Live channel until they are resolved, so sending a blocker to Jira does not let the release slip past it. Plans and prices are on the pricing page.

Common questions

How do I send beta tester feedback to Jira?

You can copy each report into an issue by hand, forward reports to a Jira email intake, use a webhook with a Jira Automation rule, or use a feedback tool with a Jira connection. In AppForShare, an Admin connects Jira Cloud on Pro or Team and a Developer presses Send to Jira on a report.

Can tester bug reports go to Linear with screenshots?

Yes. When AppForShare sends a report to Linear, screenshots and recordings up to 20 MB each are uploaded to Linear and embedded in the issue, next to the message and device facts.

Does closing the Jira or Linear issue resolve the report?

No. The link is one way. Status changes in the tracker do not come back, and resolving a report in AppForShare does not close the issue, so update both and tell the tester yourself.

Does Jira Server or Data Center work?

No. The Jira connection supports Jira Cloud sites at yourteam.atlassian.net only. For other setups, Copy for an issue gives plain text you can paste.

Should every tester report become an issue?

Usually not. Send reports that need a code change, keep ideas for a batch review, and resolve duplicates and questions in the feedback inbox so the backlog stays useful.