Tester feedback straight into Linear or Jira
Pro and Team
Testers report in one place and developers work in another. Copying a report into an issue means retyping the device, finding the build number and dragging screenshots over, and some of it always gets lost.
Connect Linear or Jira Cloud once. Every report in the feedback inbox then has a Send button that creates the issue with everything the tester sent.
Example
Bug report, sent to Jira
- IssueQA-214
- Title[Bug] Checkout button does nothing (Shop 2.5 (121))
- Attached2 screenshots
Made for
- Teams that plan their work in Linear or Jira
- QA leads who triage tester reports before developers see them
- Agencies that keep each client in its own Jira project
What it ends
- Copying a report into an issue and retyping the device and build
- Screenshots saved from one tool and uploaded to the other
- Issues without a way back to what the tester actually wrote
How it works
Step 1
Connect your tracker
An Admin opens Dashboard, Integrations and adds a Linear API key and team, or a Jira Cloud site, email and API token with a project and issue type.
Step 2
Triage the report
Read it in the feedback inbox or on the build page and decide if it needs work. Ideas you will not build can just be resolved.
Step 3
Press Send
The issue is created with the message, device facts, a link back and the screenshots or recording. The report shows the issue key from then on.
What the issue contains
A title from the first line of the report with the app version, the full message, the app and platform, device and OS, screen size, language, country, who sent it and when, the install page link, and a link back to the report. Screenshots and recordings up to 20 MB each are attached in Jira and uploaded to Linear and shown in the issue.
From the terminal and AI tools
appforshare send-feedback <id> --to linear (or jira) sends a report from the CLI. AI assistants connected through the MCP server can list feedback and send a report after you confirm.
Good to know
- One way: changes in Linear or Jira do not come back, and resolving a report in AppForShare does not close the issue.
- A report is sent once. Jira Cloud sites only (yourteam.atlassian.net); Jira Data Center is not supported.
- Issues are created as the person who owns the API key or token.
Questions
- Is the API key safe?
- It is stored encrypted, used only to create issues and upload files, and never shown again. Disconnect at any time in Integrations.
- Can I still use webhooks for Jira?
- Yes. The Jira guide shows Jira Automation with an incoming webhook to open a work item for every new build or store rejection.
- Which plan do I need?
- Pro or Team.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications