Download the App

The TestApp.io app is available on both platforms:

• iOS: Download on the App Store
• Android: Get it on Google Play

Sign In

Open the app and sign in using the same account you use on the portal. You can sign in with:

• Email and password
• Google
• Apple (iOS only)

If you don't have an account yet, you can create one directly in the app. Once signed in, the app will remember your last login method for faster access next time.

Join Your Team

After signing in, you need to be part of a team to see apps and releases. There are two ways to join:

• Accept an invitation: If a team admin has invited you, you'll see a pending invitation in the Notifications tab. Tap it to accept and join the team.
• Switch teams: If you belong to multiple teams, use the Team option in the side menu to switch between them.

Once you've joined a team, the dashboard will show your apps, recent releases, and team activity.

Browse Apps and Releases

From the dashboard, tap Apps to see all the apps your team is testing. Each app shows its name, platform (iOS or Android), and the number of active releases.

Tap an app to open its detail view, which has several tabs:

• Releases: All uploaded builds, sorted by date. You can filter by platform or status.
• Tasks: QA tasks assigned to this app. Filter by status, assignee, or priority.
• Comments: All feedback submitted by the team on this app's releases.
• Activity: A chronological feed of everything that happened on this app.

Install a Build

Tap any release to open its details. From there you can install the build directly to your device.

Android

On Android, tap the Install button on the release card. The app will:

1. Check that your device allows installations from unknown sources (if not, it will guide you to enable this permission).
2. Download the APK with a visible progress bar.
3. Open the system installer so you can confirm and complete the installation.

Once installed, the button changes to Open, letting you launch the app directly.

iOS

On iOS, the app displays a QR code or an install link. Scan the QR code with your camera or tap the link to begin installation through the standard iOS provisioning flow.

Note: iOS installations require that your device's UDID is registered in the app's provisioning profile. If installation fails, ask your team admin to add your device.

Receive Push Notifications

When a new release is uploaded, you'll receive a push notification on your phone. Tapping the notification takes you directly to the release so you can install it right away.

Push notifications are also sent for:

• New task assignments
• Comments on releases you're involved with
• Team activity updates

You can customize which notifications you receive in Settings → Notification Preferences.

Work on Tasks

If your team uses task management, you'll see tasks assigned to you in the app. Open any app and go to the Tasks tab to see:

• Tasks assigned to you or the whole team
• Task status (new, in progress, blocked, done)
• Priority and linked releases

You can update task status directly from the app — mark tasks as in progress, blocked, or done as you test. If a task is linked to a specific release, tap through to install and test that build.

Tasks synced from Jira or Linear will also appear here, with a link back to the original ticket.

Share Feedback

Found a bug or want to share feedback? Open the release and go to the Comments tab:

1. Tap the comment button to open the feedback form.
2. Write your feedback describing what you found.
3. Attach screenshots, screen recordings, or any other images and videos from your device.
4. Submit your comment.

Attachments upload in the background, so you can keep testing while files are being processed. Your team will see the comment with all attachments in both the app and the portal.

Compare Versions

Need to check if a bug exists in a previous build? The Releases tab shows your complete version history. You can:

• Install any previous release to roll back and verify issues.
• Compare behavior between versions by switching between builds.
• Filter releases by platform to find the specific build you need.

This is especially useful for regression testing — install the old build, reproduce the issue, then install the new build to confirm the fix.

Dashboard and Navigation

The app uses a side menu (accessible from the top-left icon) for navigation:

• Dashboard: Quick overview of your team's testing activity, top apps, and recent releases.
• Apps: Browse all apps you have access to.
• Team: View team members and pending invitations, and switch between teams.
• Notifications: See all alerts and pending team invitations. The bell icon shows your unread count.
• Settings: Manage your profile, notification preferences, theme (light/dark/system), and device information.

Related Articles

• Share Links: Distribute to External Testers
• Getting Started with TestApp.io — Portal setup guide
• Task Management
• Troubleshooting: Parsing the Package
• How Do I Get the UDID of an iOS Device?

Need help? Contact us and we'll get back to you shortly.

What Is a Version?

A version represents a single release cycle of your app (for example, v2.1.0). It brings together all the work needed to ship that release: the tasks your team is working on, the builds uploaded for testing, quality metrics like blocker counts, and the launches that track store submissions.

Creating a Version

1. Open your app in TestApp.io.
2. Navigate to the Versions tab.
3. Click New Version.
4. Enter a version name (e.g., v2.1.0 or Sprint 14 Release).
5. Your version is created in Planning status, ready for you to start defining scope.

Version Statuses

Each version moves through a defined lifecycle. Here is what each status means:

• Planning — You are defining the scope of this release. Create and link tasks, outline what will be included, and set goals. No builds are expected yet.
• Development — Active coding is underway. Your team is working on the tasks linked to this version, and builds are starting to be created and uploaded.
• Testing — QA is in progress. Builds are being distributed to testers, feedback is being collected, and blockers are being reported and resolved.
• Ready — All blockers have been resolved, and the version is cleared for release. This status signals that the build is approved to ship.
• Released — The version has been shipped to one or more stores. Your launches track the details of each store submission.
• Archived — The version is no longer active. Archived versions are preserved for historical reference but are hidden from day-to-day views.

The Version Dashboard

Every version has a dashboard with five tabs that give you full visibility into the release:

Overview

A summary of the version's current state. See the current status, key metrics at a glance, and a high-level snapshot of progress across tasks, builds, and quality.

Planning

View and manage all tasks linked to this version. This is where you define what work needs to be completed before the version ships.

Releases

Browse all builds that have been uploaded for this version. Each build includes its upload date, platform, and distribution details. This tab gives you a clear history of every build your team has tested.

Quality

Track the quality health of your version. See the current blocker count, test completion rates, and other quality metrics. This tab helps you decide whether the version is ready to ship.

Settings

Configure version-level settings such as the version name and other properties specific to this release.

Moving Through the Lifecycle

Advancing a version through its lifecycle is straightforward:

1. Open the version you want to update.
2. Click the current status indicator.
3. Select the next status in the lifecycle.
4. The change is applied immediately and recorded in the audit trail.

Quality Gates

TestApp.io enforces quality gates to prevent premature releases:

• Open blockers prevent moving to Ready. If any blocker is still unresolved, the version cannot be advanced to the Ready status. This ensures that known critical issues are addressed before you approve the release.
• Resolve all blockers first, then move the version to Ready when your team is confident the build is ready to ship.

Tips for Managing Versions

• Create your version early in the release cycle — even during planning — so all related tasks and builds are linked from the start.
• Use the Planning tab to connect tasks so your team has a clear view of what is in scope.
• Monitor the Quality tab regularly during testing to stay ahead of blockers.
• Once released, review the version dashboard for a complete record of the release cycle before archiving.

Need help? Contact us and we'll get back to you shortly.

Four Ways to Create Tasks

TestApp.io gives you four distinct methods for creating tasks, each suited to different workflows:

1. Manual Creation

The most direct approach. From your app's Tasks tab:

1. Click the New Task button.
2. Enter a title that clearly describes what needs to be done or tested.
3. Add a description with detailed steps, expected behavior, or reproduction instructions.
4. Set the priority level (Low, Normal, High, Critical, or Blocker).
5. Assign one or more team members to the task.
6. Optionally, link a release to associate the task with a specific build.
7. Set a due date if the task is time-sensitive.

2. Report Blocker

When you encounter a critical issue during testing, you can report it as a blocker. This creates a task with the priority automatically set to Blocker. You can report blockers from the release detail page using the Report Blocker button. For full details, see Blocker Tracking: Report and Resolve Critical Issues.

3. Pull from Integration

If your team uses project management tools such as JIRA or Linear, you can pull existing issues into TestApp.io as tasks. This is useful when your development team has already logged issues that need QA attention. The imported tasks maintain a link back to the original issue.

4. Auto-Sync from Integration

When two-way sync is enabled with JIRA or Linear, new issues created in those tools automatically appear as tasks in TestApp.io. This eliminates the need to manually import issues and keeps both systems in sync.

Task Properties

Every task in TestApp.io has the following properties:

• Title: A short, descriptive name for the task.
• Description: Detailed information, steps to reproduce, expected behavior, or testing instructions.
• Priority: Five levels that indicate urgency:
  • Low: Nice-to-test items, minor improvements.
  • Normal: Standard QA tasks and routine checks.
  • High: Important issues that should be addressed soon.
  • Critical: Severe issues that significantly impact functionality.
  • Blocker: Must-fix issues that prevent a release from shipping.
• Status: Tracks progress through four stages — Open, In Progress, Done, and Closed.
• Assignees: One or more team members responsible for the task. Multiple assignees are supported for collaborative testing.
• Release Link: Associates the task with a specific build, so you know which version the task applies to.
• Due Date: An optional deadline for task completion.

Views: Kanban Board and Table

TestApp.io offers two ways to view your tasks:

Kanban Board

The default view organizes tasks into columns by status (Open, In Progress, Done, Closed). You can drag and drop task cards between columns to update their status instantly. The Kanban board gives you a visual overview of work distribution and progress at a glance.

Table View

The table view presents tasks in a sortable, spreadsheet-like format. Each row is a task, and columns display properties such as title, priority, status, assignee, and due date. Click any column header to sort by that property. The table view is ideal when you need to scan a large number of tasks quickly or export a structured overview.

Filtering Tasks

Both views support filtering to help you find exactly what you need:

• By Status: Show only Open tasks, only In Progress tasks, or any combination.
• By Priority: Filter to see only Blockers and Critical tasks, for example.
• By Assignee: View tasks assigned to a specific team member or to yourself.
• By Linked Release: See only tasks associated with a particular build.

Task Detail Page

Click on any task to open its detail page, which includes:

• Full Description: The complete task description with all context and instructions.
• Comments Thread: A conversation thread where team members can discuss the task, ask questions, or provide updates.
• Attachments: Upload screenshots, screen recordings, logs, or any files relevant to the task.
• Activity Log: A chronological record of all changes made to the task — status updates, reassignments, priority changes, and more.

Need help? Contact us — we're happy to assist!

What Is the Leaderboard?

The Leaderboard is a gamification feature built into TestApp.io that rewards team participation. As you and your teammates perform actions across the platform — uploading releases, creating tasks, resolving blockers, and more — you earn points. These points are tallied and displayed on a leaderboard so everyone can see who is contributing the most.

It is designed to encourage engagement, recognize active team members, and make the testing and release process more enjoyable.

How Points Are Earned

Different actions earn different point values. Higher-impact actions are worth more points, rewarding the work that moves your project forward. Here are the types of actions that earn points:

• Connecting an integration — Link tools like Jira, Linear, Slack, or other project management tools to your TestApp.io workspace.
• Uploading a release — Upload a new build for distribution and testing. This is one of the highest-value actions.
• Creating a task — Log a new task for your team to track and resolve.
• Resolving a blocker — Close out a blocker that was preventing a release from moving forward.
• Adding comments — Participate in discussions on releases and tasks by posting comments.
• Other team actions — Various additional activities throughout the platform also contribute to your score.

Point values vary by action type. Actions that have a bigger impact on your team's workflow — like uploading a release or resolving a blocker — earn more points than lighter actions like adding a comment.

Viewing the Leaderboard

The leaderboard is displayed on your Home Dashboard in the TestApp.io portal. When you log in, you will see the Leaderboard widget showing the top contributors on your team.

The leaderboard displays:

• Team member names and avatars.
• Total points earned.
• Ranking position among teammates.

This gives you a quick snapshot of who has been most active and how your own contributions compare.

Real-Time Point Updates

Points update in real time as you work. When you upload a release, resolve a blocker, or perform any point-earning action, your score changes immediately. There is no delay or batch processing — you see the result of your contribution right away.

This real-time feedback loop makes it satisfying to complete tasks and encourages consistent participation throughout the day.

Why the Leaderboard Matters

The leaderboard serves several purposes for your team:

• Encourages engagement: Seeing your score rise motivates continued participation across the platform.
• Recognizes contributors: Team members who go above and beyond get visible recognition for their efforts.
• Makes QA enjoyable: A little friendly competition can make repetitive testing workflows feel more rewarding.
• Promotes best practices: By rewarding actions like resolving blockers and adding comments, the system encourages thorough, communicative workflows.

Tips

• Check the leaderboard regularly: Visit your Home Dashboard to see where you stand and celebrate teammates who are leading the way.
• Earn points naturally: The best way to climb the leaderboard is simply to do your work thoroughly — upload builds, log tasks, resolve blockers, and participate in discussions.
• Use it in retrospectives: The leaderboard can provide useful data for sprint retrospectives, showing team activity levels and participation trends.

Tip: Testers can also use the TestApp.io mobile app (iOS / Android) to install builds and receive push notifications for new releases.

Related Articles

• Home Dashboard
• Activity Feed
• Task Management

Need help? Contact us and we'll get back to you shortly.

Why Use External Storage?

By default, TestApp.io stores your uploaded builds securely. However, some teams need their data stored in specific locations or under specific controls. Common reasons to use External Storage include:

• Data sovereignty: Keep your builds in a specific geographic region to comply with local regulations.
• Compliance requirements: Meet HIPAA, GDPR, or other regulatory frameworks that require data to be stored in infrastructure you control.
• Company policy: Some organizations require all artifacts to be stored in company-owned cloud accounts.
• Backup and retention: Manage your own backup and retention policies for app builds.

Note: External Storage requires a Pro plan. Visit testapp.io/pricing for plan details.

Supported Providers

TestApp.io supports three cloud storage providers. Choose the one that matches your existing infrastructure.

Amazon S3

To connect an Amazon S3 bucket, you will need:

• Bucket name — The name of your S3 bucket.
• Region — The AWS region where your bucket is located (e.g., us-east-1, eu-west-1).
• Access Key ID — Your AWS access key.
• Secret Access Key — Your AWS secret key.

We recommend creating a dedicated IAM user with limited permissions scoped only to the target bucket. The user needs s3:PutObject, s3:GetObject, and s3:ListBucket permissions.

Google Cloud Storage (GCS)

To connect a Google Cloud Storage bucket, you will need:

• Bucket name — The name of your GCS bucket.
• Service Account JSON key — A JSON key file from a Google Cloud service account with access to the bucket.

Create a dedicated service account with the Storage Object Admin role on the target bucket for least-privilege access.

Backblaze B2

To connect a Backblaze B2 bucket, you will need:

• Bucket name — The name of your B2 bucket.
• Application Key ID — Your Backblaze application key ID.
• Application Key — Your Backblaze application key.

We recommend creating an application key scoped to the specific bucket rather than using a master key.

Setup Steps

Follow these steps to configure External Storage for your team:

1. Go to Team Settings in the TestApp.io portal.
2. Click Storage in the settings sidebar.
3. Click Configure External Storage.
4. Select your storage provider (Amazon S3, Google Cloud Storage, or Backblaze B2).
5. Enter the required credentials for your chosen provider (see details above).
6. Click Validate — TestApp.io will test the connection to your bucket to ensure the credentials are correct and the bucket is accessible.
7. Once validation passes, click Save to activate your configuration.

After saving, all new app builds will be stored in your bucket instead of TestApp.io's default storage.

Managing Your Storage Configuration

Once configured, you have several options for managing your External Storage.

Enable and Disable

You can toggle External Storage on or off without losing your configuration. When disabled, builds revert to TestApp.io's default storage. When re-enabled, your saved credentials are used again automatically. This is useful for testing or temporary changes.

Edit Configuration

Update your credentials, bucket name, or region at any time. Navigate to Team Settings → Storage and click Edit to modify your configuration. After editing, TestApp.io will re-validate the connection before saving.

Status Indicators

Your External Storage configuration shows a status indicator so you always know the current state:

• Active (green) — External Storage is enabled and the connection is working correctly.
• Disabled (grey) — External Storage is turned off. Your configuration is saved but not in use.
• Error (red) — There is a connection issue. This could mean expired credentials, a deleted bucket, or a permissions change. Check your cloud provider settings and update your configuration.

Security Best Practices

• Use dedicated credentials: Create a service account or IAM user specifically for TestApp.io. Do not reuse credentials from other services.
• Apply least-privilege access: Grant only the permissions TestApp.io needs (read, write, and list on the specific bucket).
• Rotate credentials regularly: Update your access keys periodically and re-validate the connection after each rotation.
• Monitor access logs: Enable access logging on your bucket to track all read and write operations.

Troubleshooting

• Validation fails: Double-check your bucket name, region, and credentials. Ensure the bucket exists and the credentials have the correct permissions.
• Status shows Error: Your credentials may have expired or been revoked. Go to Team Settings → Storage, update your credentials, and re-validate.
• Builds not appearing in your bucket: Confirm that External Storage status is Active (green). If it is Disabled, toggle it on.

Related Articles

• Getting Started with TestApp.io
• Publishing Destinations

Tip: Testers can also use the TestApp.io mobile app (iOS / Android) to install builds and receive push notifications for new releases.

Need help? Contact us and we'll get back to you shortly.

Where to Find the Activity Feed

To access the Activity Feed, navigate to any app in your TestApp.io portal and click the Activity tab in the sidebar. Each app has its own dedicated feed, so you see only the activity relevant to that project.

What Shows Up in the Feed

The Activity Feed captures a wide range of team actions, including:

• Release uploads — When a teammate uploads a new build, it appears in the feed with version details.
• Task creation and updates — New tasks, status changes, assignments, and completions are all tracked.
• Blocker reports and resolutions — See when blockers are raised and when they get resolved.
• Version status changes — Track when a release moves through different statuses.
• Integration sync events — Activity from connected tools like Jira or Linear appears here automatically.
• Comments and mentions — Comments posted on releases and tasks show up in the feed, along with any @mentions.

Interacting with Activity Items

The Activity Feed is not just a read-only log. You can interact directly with any item in the stream.

Reply to Activity

Click Reply on any activity item to add a comment directly in context. This is useful for asking quick questions about a release or acknowledging a completed task without navigating away from the feed.

@Mention Teammates

Type @ followed by a teammate's name to mention them. They will receive a notification, making it easy to pull someone into a conversation or flag something for their attention. For example, you might reply to a release upload with @Sarah can you test this on Android 14?

Add Emoji Reactions

React to any activity item with an emoji. Reactions are a quick, lightweight way to acknowledge an update without adding a full comment. Use them to signal approval, celebrate a milestone, or simply let your team know you have seen an update.

Real-Time Updates

The Activity Feed updates in real time. When a teammate uploads a release, creates a task, or posts a comment, the new activity appears in your feed instantly — no page refresh needed. This makes the feed a reliable, always-current view of what is happening across your app.

Tips for Using the Activity Feed

• Morning standup catch-ups: Open the Activity Feed at the start of your day to see what happened overnight. It gives you a quick summary of all team actions without needing to check multiple pages.
• Track release progress: Use the feed to follow a release from upload through testing to completion. Every status change and comment is captured in one place.
• Stay in the loop on mentions: Keep an eye on the feed for @mentions directed at you. This is how teammates flag items that need your attention.
• Use reactions to reduce noise: Instead of writing "looks good" or "got it," drop a quick emoji reaction to acknowledge without cluttering the feed.

Related Articles

• Comments: Replies, Reactions, Mentions, and Attachments
• Task Management

Need help? Contact us — we're happy to assist!

What Is What's New?

What's New is a built-in feature update feed inside the TestApp.io portal. It provides a chronological list of new features, improvements, bug fixes, and platform updates. Think of it as a changelog that lives right inside your workspace, so you do not need to check external blogs or release notes pages.

How to Access What's New

To open the What's New feed:

1. Log in to the TestApp.io portal.
2. Look at the top navigation bar (the header area).
3. Click the gift/present icon in the navigation.
4. The What's New panel opens, showing the latest updates.

The icon may show a badge or indicator when there are new, unread updates waiting for you.

Browsing Updates

The What's New feed presents updates in a scrollable list, organized by date with the most recent items at the top. Each entry typically includes:

• Feature name or title — A clear label describing the update.
• Description — A brief explanation of what changed, what is new, or what was improved.
• Date — When the update was released.

Scroll through the list to catch up on everything that has changed since your last visit.

Rating Features

Your feedback matters. Each item in the What's New feed includes an option to rate the feature — you can indicate whether the update was helpful or not helpful.

This feedback goes directly to the TestApp.io team and helps prioritize future improvements. If a feature is particularly useful to your workflow, rating it positively helps signal that similar enhancements are valuable.

Mark as Read

As you review items in the What's New feed, you can mark them as read to keep your list clean. Dismissing items you have already reviewed ensures that the next time you open the feed, you can quickly spot genuinely new updates without scrolling past items you have already seen.

Tips

• Check regularly: Make it a habit to open What's New periodically — even weekly. New features are released frequently, and staying current helps you take advantage of capabilities that could streamline your workflow.
• Share with your team: When you spot a feature that would benefit your team, let them know. A quick message in your team chat pointing to a new capability can improve everyone's experience.
• Provide feedback: Take a moment to rate features. Your input directly influences what gets built next, so your ratings help shape the platform to better fit your needs.
• Explore new features immediately: When you see an update that looks useful, try it right away while the context is fresh. This is the fastest way to integrate new capabilities into your daily workflow.

Related Articles

• Home Dashboard
• Playbooks

Tip: Testers can also use the TestApp.io mobile app (iOS / Android) to install builds and receive push notifications for new releases.

Need help? Contact us and we'll get back to you shortly.

1. Sign Up

Head to portal.testapp.io and create your account. You can sign up with your email address or use an existing Google account for faster onboarding. Once signed in, you will land on the home dashboard.

2. Create Your Team

Your team is the workspace where all your apps, releases, and tasks live. To create one:

1. Click Create Team from the onboarding prompt or the sidebar.
2. Give your team a name (e.g., your company or project name).
3. Invite team members by entering their email addresses. They will receive an invitation to join your workspace.

3. Create Your First App

With your team in place, create an app entry for each mobile project you want to test:

1. Click Create App from the Apps section in the sidebar.
2. Enter a name for your app.
3. Select the platform: iOS, Android, or Both. Choosing Both creates a unified app entry that accepts IPA files for iOS and APK files for Android.

Once created, you will be taken to the app overview page where you can upload builds, manage releases, and track tasks.

4. Upload Your First Release

Uploading a build to TestApp.io is straightforward:

1. Navigate to your app and open the Releases tab.
2. Drag and drop your build file (IPA for iOS, APK for Android) into the upload area. TestApp.io uses chunked uploads, so even large files transfer reliably.
3. Add release notes describing what changed in this build. Detailed notes help your team know what to test and also power AI task generation later.
4. Click Upload to publish the release.

5. Share with Testers

Once your release is uploaded, share it with your team and external testers. TestApp.io gives you multiple ways to distribute:

• Install Link: Copy the direct install link and send it via email, Slack, or any messaging tool. Testers tap the link on their device to install.
• QR Code: Each release has a scannable QR code. Display it on screen or print it — testers scan with their phone camera to install instantly.
• TestApp.io Mobile App: Have testers download the TestApp.io app (iOS / Android). They will receive push notifications for new releases, install builds with a single tap, work through assigned tasks, and submit feedback with screenshots and videos — all from their phone. See the Mobile App Getting Started guide for details.

6. What's Next

With your first release distributed, explore the full platform:

• Task Management: Create QA tasks, assign them to team members, and track progress on a Kanban board or table view. Learn more about task management.
• Blocker Tracking: Flag critical issues that must be resolved before shipping. Track blocker resolution across all your apps. Learn more about blocker tracking.
• AI Task Generation: Let AI read your release notes and generate targeted QA tasks automatically. Learn more about AI task generation.
• Integrations: Connect project management tools such as JIRA and Linear to sync tasks bidirectionally.
• Home Dashboard: Monitor your team's testing activity, open blockers, and top contributors from a single view. Learn more about the dashboard.

Need help? Contact us — we're happy to assist!

What This Does

The Install feature lets you take an app build that has been uploaded to the TestApp.io portal and install it directly onto a physical device. This is essential for manual testing, QA review, stakeholder demos, and any situation where you need to run a build on real hardware.

Installing from Desktop (QR Code Method)

When you are working on a desktop or laptop computer, the portal uses a QR code to bridge the gap between your screen and your phone.

1. Open the TestApp.io portal on your computer and navigate to the app you want to install.
2. Find the release you want to install. You can access it from two places:
   • Release list: Click the Actions menu dropdown on the release row, then select Install.
   • Release detail page: Open the release and click the Install button.
3. A QR code appears on your screen.
4. Open your phone's camera and scan the QR code.
5. The link opens in the TestApp.io mobile app on your phone.
6. The build installs automatically on your device.

The entire process takes just a few seconds from scan to install.

Installing from Mobile Browser

If you are already browsing the portal on your phone, you can skip the QR code step entirely.

1. Open the release page in your phone's mobile browser.
2. Tap Install on Device.
3. The TestApp.io mobile app opens automatically.
4. The build installs directly to your device.

This is the fastest path when you are already on your phone — one tap and the build starts installing.

Requirements

To install builds from the portal, you need:

• TestApp.io mobile app installed on your device. The mobile app handles the actual installation of builds onto your phone. Without it, the QR code and Install on Device links will not work.
• Access to the app in the TestApp.io portal. You must be a member of the team or have been granted access to the app.

Where to Find the Install Option

Here is a quick reference for where the Install action is available:

• Release list page: Each release row has an Actions dropdown menu. Click it and select Install.
• Release detail page: The Install button is prominently displayed on the page.

Both paths lead to the same result — choose whichever is more convenient based on where you are in the portal.

Tips

• QR codes in meetings: The QR code method is perfect for team meetings and demos. Share your screen with the portal open, click Install, and everyone in the room can scan the QR code to get the build on their own device instantly.
• Bookmark release pages: If you frequently test the same app, bookmark the release list page in your mobile browser for quick access to the latest builds.
• Keep the mobile app updated: Make sure you are running the latest version of the TestApp.io mobile app for the best installation experience.

Troubleshooting

• The QR code does not open the app: Make sure the TestApp.io mobile app is installed on your device. If it is installed but the link still does not open it, try updating the app to the latest version.
• Install on Device button not working: Ensure you are accessing the portal from a mobile browser on the device where you want to install the build.

Other Ways to Install

• TestApp.io Mobile App (iOS / Android) — Receive push notifications for new builds and install with a single tap. Testers can also manage tasks and submit feedback from their phone. See the Mobile App Getting Started guide.
• Share Links — For external testers and clients who do not have a TestApp.io account, create public install links with optional password protection. See Share Links.

Related Articles

• Getting Started with TestApp.io
• Activity Feed

Need help? Contact us and we'll get back to you shortly.

This guide walks you through connecting Linear, configuring field mappings, importing issues, migrating tasks, and monitoring sync activity.

1. Connecting Linear to TestApp.io

To get started, you need to authorize TestApp.io to access your Linear workspace via OAuth:

1. In TestApp.io, navigate to Team Settings → Integrations → Linear.
2. Click the “Connect” button next to the Linear integration.
3. You will be redirected to Linear’s OAuth authorization page.
4. Review the permissions requested and click “Authorize”.
5. Once authorized, you will be redirected back to TestApp.io. Your Linear workspace is now connected.

Tip: Only team admins can connect or disconnect integrations. Make sure you have the necessary permissions in both TestApp.io and Linear before proceeding.

2. Selecting Your Linear Team

After connecting, you need to choose which Linear team to sync with:

1. On the Linear integration settings page, you will see a list of available Linear teams from your workspace.
2. Select the team whose issues you want to sync with TestApp.io.
3. Click “Save” to confirm your selection.

This determines which Linear team’s issues will be synced, imported, or migrated within TestApp.io.

3. Configuring Field Mappings

Field mapping lets you define how statuses and priorities translate between TestApp.io and Linear:

Status Mapping

Map each TestApp.io task status to its corresponding Linear status. For example:

• Open (TestApp.io) → Todo (Linear)
• In Progress (TestApp.io) → In Progress (Linear)
• Resolved (TestApp.io) → Done (Linear)

Priority Mapping

Similarly, map priority levels between the two platforms to ensure issues maintain the correct urgency when synced.

To configure mappings:

1. Go to the Field Mapping section in your Linear integration settings.
2. For each TestApp.io status, select the corresponding Linear status from the dropdown.
3. Repeat the process for priority fields.
4. Click “Save Mappings” when finished.

You can update these mappings at any time without disconnecting the integration. See Integration Power Features for more on field mapping management.

4. How 2-Way Sync Works

Once connected and configured, TestApp.io and Linear stay in sync in real time through webhooks:

• Outbound sync: When you create, update, or complete a task in TestApp.io, the corresponding Linear issue is automatically updated.
• Inbound sync: When a team member changes an issue in Linear (status, priority, assignee, comments), the linked TestApp.io task is updated accordingly.

Sync happens automatically — there is nothing additional to configure. Both platforms reflect changes within seconds of an update being made.

Note: Only tasks that are linked between the two systems will sync. Unlinked tasks remain independent.

5. Importing Existing Linear Issues

If your team already has issues in Linear that you want to bring into TestApp.io, use the import feature:

1. In the Linear integration settings, click “Pull Tasks”.
2. Browse the available issues from your selected Linear team.
3. Select the issues you want to import.
4. Click “Import Selected”.

Imported issues become TestApp.io tasks and are automatically linked to their Linear counterparts for ongoing 2-way sync.

6. Migrating Local Tasks to Linear

If you have tasks created locally in TestApp.io that you want to move to Linear:

1. Go to your Linear integration settings and click “Migrate Tasks”.
2. Select the local TestApp.io tasks you want to migrate.
3. Map your TestApp.io statuses to the appropriate Linear statuses (e.g., “Open” → “Todo”).
4. Confirm the migration.

Migrated tasks will be created as new issues in Linear and automatically linked for bidirectional sync going forward.

7. Viewing Sync History

TestApp.io maintains a complete audit trail of all sync events between your workspace and Linear:

1. Navigate to Team Settings → Integrations → Linear → Sync History.
2. You will see a log of every sync event, including:
   • Direction: Whether the sync was inbound (Linear → TestApp.io) or outbound (TestApp.io → Linear).
   • Status: Whether the sync succeeded or failed.
   • Timestamp: When the sync occurred.
   • Error details: If a sync failed, the reason is displayed.
3. For failed syncs, click the “Retry” button to attempt the sync again.

Regularly reviewing sync history helps you catch and resolve any issues before they impact your workflow.

8. Troubleshooting

If you encounter issues with your Linear integration, try the following:

• Sync not working: Verify the integration is enabled (not just connected). You can toggle it on/off in the integration settings without losing your configuration.
• Authorization errors: Disconnect and reconnect the integration by going through the OAuth flow again.
• Missing issues: Ensure you have selected the correct Linear team. Issues from other teams will not appear.
• Failed syncs: Check the sync history for error details and use the retry button. Common causes include permission changes in Linear or network timeouts.
• Field mapping issues: If synced tasks have incorrect statuses, review and update your field mappings.

For more advanced features like toggling integrations, bulk imports, and detailed sync management, see Integration Power Features: Disable, Pull, Migrate, Sync History.

To learn more about how tasks work in TestApp.io, visit our Task Management guide.

Need help? Contact us and we’ll get back to you shortly.

This guide covers the key power features available for both the JIRA and Linear integrations.

1. Enable and Disable Your Integration

Sometimes you need to pause an integration without fully disconnecting it — for example, during a major reorganization or when troubleshooting an issue.

TestApp.io lets you toggle your JIRA or Linear integration on and off:

1. Go to Team Settings → Integrations and select your integration (JIRA or Linear).
2. Use the Enable/Disable toggle to turn the integration on or off.

What happens when you disable:

• All syncing pauses immediately. No changes will flow between TestApp.io and the connected tool.
• Your configuration is fully preserved — field mappings, project/team selection, and all linked tasks remain intact.
• No data is lost. When you re-enable, syncing resumes with your existing settings.

What happens when you re-enable:

• Real-time syncing resumes immediately.
• Any changes made while the integration was disabled will sync on the next update to the affected task.

Tip: Disabling is different from disconnecting. Disconnecting removes the OAuth authorization entirely and requires you to go through the setup process again. Disabling simply pauses sync while keeping everything configured.

2. Pull Tasks: On-Demand Import

The Pull Tasks feature lets you import existing issues from JIRA or Linear into TestApp.io on demand. This is useful when you want to bring over issues that were created before the integration was set up, or when new issues are added to a specific project or team that you want to track in TestApp.io.

How to pull tasks:

1. Navigate to Team Settings → Integrations and select your integration.
2. Click the “Pull Tasks” button.
3. Browse the available issues from your connected JIRA project or Linear team.
4. Select the issues you want to import.
5. Click “Import Selected”.

Imported issues become TestApp.io tasks and are automatically linked to their source issues in JIRA or Linear. Once linked, they participate in real-time bidirectional sync — any future changes in either platform will be reflected in the other.

3. Migrate Tasks: Move Local Tasks to JIRA or Linear

If your team has been creating tasks locally in TestApp.io and now wants to move them into JIRA or Linear, the Migrate Tasks feature handles this seamlessly.

How to migrate tasks:

1. Go to Team Settings → Integrations and select your integration.
2. Click the “Migrate Tasks” button.
3. Select the local TestApp.io tasks you want to migrate.
4. Map your TestApp.io statuses to the corresponding statuses in the target tool:
   • For JIRA: e.g., “Open” → “To Do”, “In Progress” → “In Progress”, “Resolved” → “Done”
   • For Linear: e.g., “Open” → “Todo”, “In Progress” → “In Progress”, “Resolved” → “Done”
5. Review the mapping summary to confirm everything looks correct.
6. Click “Confirm Migration”.

What happens during migration:

• A new issue is created in JIRA or Linear for each selected TestApp.io task.
• The task’s status and priority are mapped according to your field mapping configuration.
• The TestApp.io task is linked to the newly created issue.
• From this point forward, the task participates in real-time 2-way sync.

Note: Migration does not delete the original TestApp.io task. It creates a linked counterpart in your external tool.

4. Sync History: Complete Audit Trail

Every sync event between TestApp.io and your connected JIRA or Linear instance is logged in the Sync History. This gives you full visibility into what is happening with your integration at all times.

How to access sync history:

1. Go to Team Settings → Integrations and select your integration.
2. Click on “Sync History”.

What you will see:

Each sync event entry includes:

• Direction: Whether the sync was inbound (JIRA/Linear → TestApp.io) or outbound (TestApp.io → JIRA/Linear).
• Status: Whether the sync succeeded or failed.
• Timestamp: The exact date and time the sync event occurred.
• Error details: For failed syncs, a description of what went wrong.

Retrying failed syncs:

If a sync event has failed, you can retry it with one click:

1. Find the failed event in the sync history.
2. Review the error details to understand the cause.
3. Click the “Retry” button.
4. TestApp.io will re-attempt the sync.

Common causes of failed syncs include temporary network issues, permission changes in the connected tool, or field mapping mismatches. Reviewing error details usually points you directly to the fix.

5. Field Mapping: Customize at Any Time

Field mapping controls how statuses and priorities translate between TestApp.io and your connected tool. You can update these mappings at any time without disconnecting or disrupting your integration.

How to update field mappings:

1. Go to Team Settings → Integrations and select your integration.
2. Open the Field Mapping section.
3. Adjust the status and priority mappings as needed.
4. Click “Save Mappings”.

Updated mappings take effect immediately for all future sync events. Previously synced tasks are not retroactively updated — they will pick up the new mappings on their next change.

When to update mappings:

• When you add new statuses or priorities in JIRA or Linear.
• When you restructure your workflow in TestApp.io.
• When synced tasks are landing in incorrect statuses.

For detailed setup instructions specific to each integration, see:

• JIRA Integration: Setup and 2-Way Sync
• Linear Integration: Setup and 2-Way Sync

Need help? Contact us and we’ll get back to you shortly.

This guide covers everything from initial connection to importing issues, migrating tasks, and monitoring sync activity.

1. Connecting JIRA to TestApp.io

The JIRA integration uses OAuth 2.0 via Atlassian for secure authorization:

1. In TestApp.io, go to Team Settings → Integrations → JIRA.
2. Click the “Connect” button.
3. You will be redirected to Atlassian’s OAuth authorization page.
4. Log in to your Atlassian account (if not already logged in) and review the permissions.
5. Click “Accept” to authorize the connection.
6. You will be redirected back to TestApp.io with JIRA now connected.

Tip: You need admin-level permissions in your TestApp.io team to connect integrations. Ensure you also have the appropriate access in your Atlassian workspace.

2. Selecting Your JIRA Project

After authorization, choose which JIRA project to sync with:

1. On the JIRA integration settings page, you will see a list of available projects from your connected Atlassian workspace.
2. Select the project you want to sync with TestApp.io.
3. Click “Save” to confirm.

All sync, import, and migration operations will target this selected project.

3. Configuring Field Mappings

Field mappings define how task data translates between TestApp.io and JIRA. Proper mapping ensures that statuses and priorities remain accurate when synced.

Status Mapping

Map each TestApp.io task status to the corresponding JIRA status. For example:

• Open (TestApp.io) → To Do (JIRA)
• In Progress (TestApp.io) → In Progress (JIRA)
• Resolved (TestApp.io) → Done (JIRA)

Priority Mapping

Map TestApp.io priority levels to JIRA priority levels to ensure issues retain the correct urgency across platforms.

To configure your mappings:

1. Open the Field Mapping section in your JIRA integration settings.
2. Use the dropdowns to match each TestApp.io status with the appropriate JIRA status.
3. Do the same for priority levels.
4. Click “Save Mappings”.

Mappings can be updated at any time. For more details, see Integration Power Features.

4. How 2-Way Sync Works

With JIRA connected and field mappings configured, TestApp.io and JIRA stay synchronized in real time via webhooks:

• Outbound sync (TestApp.io → JIRA): When you create, update, or complete a task in TestApp.io, the linked JIRA issue is updated automatically.
• Inbound sync (JIRA → TestApp.io): When someone modifies a JIRA issue — changing status, priority, assignee, or adding comments — the corresponding TestApp.io task reflects those changes.

Sync is continuous and automatic. There are no manual steps required once the integration is configured. Changes typically appear within seconds.

Note: Only linked tasks and issues are synced. Creating a new task in TestApp.io does not automatically create a JIRA issue unless it was imported or migrated.

5. Importing Existing JIRA Issues

Bring your existing JIRA issues into TestApp.io with the import feature:

1. In the JIRA integration settings, click “Pull Tasks”.
2. Browse issues from your selected JIRA project.
3. Select the issues you want to import into TestApp.io.
4. Click “Import Selected”.

Imported issues become TestApp.io tasks and are linked to their JIRA counterparts for ongoing bidirectional sync.

6. Migrating Local Tasks to JIRA

If you have tasks that were created locally in TestApp.io and want to push them to JIRA:

1. Navigate to your JIRA integration settings and click “Migrate Tasks”.
2. Select the TestApp.io tasks you want to migrate.
3. Map your TestApp.io statuses to the corresponding JIRA statuses (e.g., “Open” → “To Do”).
4. Review the mapping summary and click “Confirm Migration”.

Each migrated task will be created as a new JIRA issue and linked for real-time sync going forward.

7. Migration from the Old JIRA Integration

If your team previously used an older version of the JIRA integration, you can migrate to the new OAuth-based integration:

1. Go to Team Settings → Integrations → JIRA.
2. If a legacy integration is detected, you will see a migration prompt.
3. Follow the on-screen instructions to re-authorize via Atlassian OAuth 2.0.
4. Your existing configuration (field mappings, linked tasks) will be preserved during the migration.

After migration, you will benefit from improved reliability, better sync performance, and the full set of integration features.

8. Viewing Sync History

TestApp.io logs every sync event between your workspace and JIRA in a detailed audit trail:

1. Go to Team Settings → Integrations → JIRA → Sync History.
2. Each entry shows:
   • Direction: Inbound (JIRA → TestApp.io) or outbound (TestApp.io → JIRA).
   • Status: Success or failed.
   • Timestamp: When the event occurred.
   • Error details: For failed syncs, the specific error message is shown.
3. Click “Retry” on any failed event to re-attempt the sync.

Monitoring sync history regularly helps you identify and resolve issues quickly.

9. Troubleshooting

If you run into problems with your JIRA integration, here are common issues and solutions:

• Cannot connect: Ensure you have the required Atlassian permissions. Try clearing your browser cache and re-initiating the OAuth flow.
• Sync not working: Check that the integration is enabled (toggled on) in the settings. A connected but disabled integration will not sync.
• Authorization expired: Disconnect the integration and reconnect it through the OAuth flow to refresh your credentials.
• Wrong statuses after sync: Review your field mappings. Incorrect mappings are the most common cause of status mismatches.
• Failed sync events: Open the sync history, review the error details, and use the retry button. Common causes include permission changes in JIRA or temporary network issues.
• Missing JIRA issues: Verify you have selected the correct JIRA project. Issues from other projects will not appear.

For advanced features like toggling integrations, bulk imports, and detailed sync management, see Integration Power Features: Disable, Pull, Migrate, Sync History.

To learn more about how tasks work in TestApp.io, visit our Task Management guide.

Need help? Contact us and we’ll get back to you shortly.

Step 1: Add Release Notes

AI task generation starts with good release notes. When you upload a build to TestApp.io, you will see a release notes field. Fill this in with a description of what changed in the build:

• New features that were added
• Bugs that were fixed
• UI changes or redesigns
• Performance improvements
• Platform-specific changes (iOS only, Android only)

The more specific your release notes are, the better the AI-generated tasks will be. For example:

Vague notes (less helpful):

Bug fixes and improvements.

Detailed notes (much better):

Added dark mode support for the settings screen. Fixed crash when uploading images larger than 10MB on Android. Improved onboarding flow with new progress indicator. Updated push notification handling for iOS 17.

Tip: Treat release notes as instructions for your QA team. If a tester could not figure out what to test from your notes alone, the AI will have the same problem.

Step 2: Generate Tasks

After your release has been uploaded:

1. Navigate to the release detail page for the build you just uploaded.
2. Click the Generate Tasks button.
3. The AI will process your release notes along with your app description and platform context.
4. After a few seconds, you will see a list of suggested tasks.

The AI reads three sources of information to generate relevant tasks:

• Release Notes: The primary input — what changed in this specific build.
• App Description: General context about what your app does, which helps the AI understand domain-specific testing needs.
• Platform Context: Whether the build is for iOS or Android, so the AI can suggest platform-appropriate test cases (e.g., iOS permission dialogs, Android back button behavior).

Step 3: Review Suggestions

The AI will present up to 15 task suggestions. Each suggestion includes a title, description, and suggested priority level. Before creating any tasks, review each one carefully:

• Title: Check that it clearly describes the test case. Edit it if the wording is unclear or too generic.
• Description: Review the testing steps and expected outcomes. Add any additional context your team might need.
• Priority: Verify the suggested priority makes sense. The AI may suggest High priority for a minor UI tweak — adjust as needed.

You can edit any field on any suggestion before creating the task. You are in full control of what ends up on your task board.

Step 4: Bulk Create Selected Tasks

Once you have reviewed and refined the suggestions:

1. Select the tasks you want to create by checking the box next to each one. You do not have to create all of them — pick only the ones that are relevant.
2. Click Create to add the selected tasks to your app's task board.
3. The tasks appear on your Kanban board immediately with an Open status, ready to be assigned and worked on.

You can assign team members, set due dates, and link additional releases to the tasks after creation, just like any manually created task.

Tips for Better AI Results

To get the most useful task suggestions from the AI, follow these best practices:

Write Detailed Release Notes

The single most important factor is the quality of your release notes. Include specific feature names, describe what changed, and mention any edge cases you are aware of. Avoid generic phrases like "bug fixes" without specifying which bugs were fixed.

Include Feature Names and Changes

Instead of writing "Updated the profile screen," write "Added phone number field to profile screen with country code picker and validation." The AI will generate much more targeted test cases when it knows the specifics.

Mention Platform-Specific Details

If a change only affects one platform, say so explicitly. For example: "Fixed iOS-specific issue where notifications were not cleared after opening" or "Added Android widget support for the dashboard summary." This helps the AI generate platform-appropriate test cases.

Keep Your App Description Up to Date

The AI uses your app description as background context. If your app has evolved significantly since you first created it, update the description in your app settings. An accurate app description helps the AI understand the domain and generate more relevant tasks.

Iterate and Refine

If the initial suggestions are not quite right, update your release notes with more detail and generate again. Over time, you will develop a feel for the level of detail that produces the best results for your specific app and workflow.

Note: AI-generated tasks work with all the same features as manually created tasks — comments, attachments, activity logs, filtering, and integration sync. For a complete overview of the task system, see Task Management: Creating and Managing Tasks. If an AI-generated task reveals a critical issue, you can escalate its priority to Blocker. See Blocker Tracking: Report and Resolve Critical Issues.

Need help? Contact us and we'll get back to you shortly.

Where You Can Comment

Comments are available in two places:

• Release detail pages — Discuss a specific build, report issues, or confirm testing results directly on the release.
• Task detail pages — Collaborate on tasks by adding context, asking questions, or providing status updates.

To access either, navigate to the relevant release or task in your TestApp.io portal and scroll to the comments section.

Adding a Comment

To add a comment:

1. Navigate to a release or task detail page.
2. Type your message in the comment box at the bottom of the page.
3. Click Send to post your comment.

Your comment appears immediately and is visible to all team members with access to the app. Comments also support markdown-like formatting, so you can use bold, italics, lists, and code snippets to structure your messages clearly.

Threaded Replies

Keep discussions organized by replying directly to a specific comment instead of posting a new top-level message.

1. Find the comment you want to respond to.
2. Click Reply beneath it.
3. Type your response and send.

Your reply appears nested under the original comment, creating a clear thread. This is especially useful when multiple conversations are happening on the same release or task — threads prevent discussions from getting tangled.

Emoji Reactions

Sometimes a full reply is not necessary. Emoji reactions let you quickly acknowledge a comment without adding noise to the conversation.

1. Hover over or tap a comment.
2. Click the reaction icon.
3. Select an emoji.

Reactions appear beneath the comment, similar to how reactions work on GitHub. They are a lightweight way to signal agreement, approval, or acknowledgement. Multiple team members can react to the same comment, and you can see who reacted by hovering over the emoji.

@Mentions

Need to pull a specific teammate into a discussion? Use @mentions to notify them directly.

1. In the comment box, type @ followed by your teammate's name.
2. Select the correct person from the dropdown that appears.
3. Finish your message and send.

The mentioned teammate receives a notification, ensuring they see your message even if they are not actively watching the page. This is particularly useful for:

• Asking a developer to investigate a bug found during testing.
• Requesting a QA lead to review a release before distribution.
• Flagging a blocker for a project manager's attention.

Attachments

Attach files directly to your comments to share evidence, context, or supporting materials.

1. Click the attachment icon in the comment box.
2. Select one or more files from your device — screenshots, documents, or videos.
3. Add any text to accompany the attachment, then send.

Image attachments display an inline preview directly in the comment, so teammates can see screenshots without downloading them. Other file types appear as downloadable links.

Common use cases for attachments include:

• Screenshots of bugs or UI issues found during testing.
• Screen recordings showing how to reproduce a problem.
• Design documents or specification files for reference.

Tips for Effective Commenting

• Use @mentions for urgent items: If something needs immediate attention, mention the responsible person rather than hoping they check the page.
• Use reactions for acknowledgements: A thumbs-up reaction says "I have seen this" without adding another comment to scroll through.
• Keep threads focused: Start a new top-level comment for a new topic rather than extending an unrelated thread.
• Attach visual evidence: A screenshot is often clearer than a written description. Use attachments to reduce back-and-forth.

Tip: These features are also available in the TestApp.io mobile app (iOS / Android). Testers can install builds, manage tasks, and submit feedback with attachments directly from their phone.

Related Articles

• Activity Feed: Track Everything in Real-Time
• Task Management
• Blocker Tracking

Need help? Contact us and we'll get back to you shortly.

What Is a Blocker?

A blocker is a task with the highest priority level in TestApp.io. It signals a critical issue that prevents a build from being released to production. Common examples include:

• Crashes on app launch or during core user flows
• Data loss or corruption bugs
• Security vulnerabilities
• Features that are completely non-functional
• Critical UI issues that make the app unusable

Blockers are treated differently from other tasks throughout the platform. They appear in dedicated widgets, trigger visual warnings, and are surfaced prominently so no one on your team can miss them.

How to Report a Blocker

There are two ways to report a blocker in TestApp.io:

Method 1: From Task Creation

1. Navigate to your app's Tasks tab.
2. Click New Task.
3. Fill in the title and description with details about the critical issue.
4. Set the Priority to Blocker.
5. Assign team members who should investigate and fix the issue.
6. Optionally, link the task to the specific release where you found the problem.
7. Save the task.

The task will immediately appear as a blocker across the platform.

Method 2: From the Release Detail Page

1. Navigate to the specific release where you found the issue.
2. Click the Report Blocker button.
3. Enter a title and description for the issue.
4. The priority is automatically set to Blocker, and the release is automatically linked.
5. Assign the appropriate team members.
6. Submit the blocker.

Where Blockers Appear

TestApp.io surfaces blockers in multiple places to ensure maximum visibility:

App Dashboard

Each app displays a blocker count badge on its dashboard card. If an app has open blockers, the badge is immediately visible, drawing attention to the fact that critical issues exist.

Version Overview Page

When viewing a specific version of your app, a warning indicator appears if there are open blockers associated with that version. This prevents anyone from assuming a version is ready to ship when critical issues remain unresolved.

Release List

In the releases list view, releases that have associated blockers are flagged with a visual marker. This makes it easy to scan your release history and identify which builds have known critical issues.

Home Dashboard

The home dashboard includes two places where blockers appear:

• Open Blockers stat card: Shows the total count of unresolved blockers across all apps.
• Blockers Across Apps widget: Lists every open blocker from every app, giving you a consolidated view of all critical issues in your workspace.

For more about the dashboard, see Home Dashboard Overview.

Resolving Blockers

When a blocker has been fixed and verified, resolve it with these steps:

1. Open the blocker task from any of the locations described above.
2. Click the Resolve button.
3. Add resolution notes explaining what was done to fix the issue. For example: "Fixed null pointer exception in login flow. Patched in build 2.4.1."
4. Confirm the resolution.

The system automatically tracks:

• Who resolved the blocker
• When it was resolved
• Resolution notes with the explanation of the fix

This audit trail is important for QA accountability and for understanding the history of critical issues across your releases.

Blocker Metrics

TestApp.io tracks key metrics around your blockers to help you improve your QA process over time:

• Resolution Time: How long it takes from when a blocker is reported to when it is resolved. Shorter resolution times indicate a more responsive team.
• Blocker Count Trends: Track whether the number of blockers per release is increasing or decreasing over time.
• SLA Compliance: If your team has internal targets for blocker resolution speed, you can measure how often those targets are met.

Need help? Contact us — we're happy to assist!