Hi, How can we help you?

AgileTest ONLY stores the data that are not available on Jira. Our company will not share our customers’data with any 3rd party, under any circumstances.

1. The data that AgileTest stores:

• Issue ID, Release Sprint ID, Attachment Link, User Account ID.
• Milestones, Preconditions, Test Steps, Test Session Item, Test Execution Item, Folders (Repository), Tests History, Test Run Item, Test Runs, and similar data.

2. The data that Agile does not store (anything that is mapped to Jira will be stored on Jira)

• Test Case Issues, Test Plans Issues, Test Executions Issues, Requirements Issues, Script Issues (AgileTest Script), Sessions Issues (Exploratory Test).

• Sessions: manage ad-hoc tests for fast-release cycles with real-time result updates.
• Scripts: Script editor to write test scripts, and checklists for testing features and record test results in-line.
• Test Executions: runs and calculates the status of test cases and their test steps.

A reminder that both session items and the script’s checklist node would not be saved as Jira issues.

• Users can make changes to the generated test cases and test steps to their project’s needs.
• Besides, they can customize the generated tests/steps language by going to Apps (upper Menu bar) → Manage Your Apps → AgileTest Preferences (left-sidebar) → AI Configuration.

AgileTest plans to become commercial in Quarter 1, 2025. You can check this sample pricing plan here: Link.

The pricing of the AgileTest application is based on the maximum number of users of Jira products on your site. This pricing model applies to all apps purchased via Atlassian. For example, if you have Jira Software (100 users), Jira Service Management (80 agents), and Jira Work Management (50 users) on the same site, you will pay the 100-user price for each Jira Cloud app installed on your Jira products.

• Atlassian Server products operate on a tiered pricing structure. This means your cost is determined by the number of users you have. While the specific tiers may vary, the principle remains consistent: exceeding a tier threshold, even by a single user, will move your subscription to the next pricing level.

• For instance, if your team has 25 users, you fall within the 11-25 user tier. However, adding just one more user, bringing your total to 26, will shift your subscription to the 26-50 user tier. It’s crucial to be aware of these tier thresholds when planning your Atlassian Server usage to accurately forecast costs.