Test the whole release, not one project at a time
Bring requirements from other Jira projects into your testing, plan across projects, and log defects where each team works.
Releases cross projects. Testing usually doesn't.
One release, many projects
Requirements get copied
Coverage stops at the border
Defects are scattered
Test across projects without copying a single story
Requirements stay in the project that owns them. AgileTest brings them into your testing.
Map other projects
Plans across projects
Traceability across projects
Defects in the right project
Defects by project
Explore any issue
Set it up once in Requirement Mapping
Open Requirement Mapping
In AgileTest Settings, a project or Jira admin opens the Requirement Mapping tab.
SettingsMap the projects
Click + Map Project and pick the projects that feed your release.
+ Map ProjectChoose the work types
Drag in the work types, such as Story or Epic, that become requirements.
Story · EpicTest and report
Plan, run and report on them like requirements in your own project.
Plans · Coverage · DefectsHow mapped requirements behave
They work like your own requirements, without leaving their home project.
Stay in their home project
Nothing is copied. Each requirement keeps its own key and project.
Only the types you choose
Only work items of the selected work types become requirements.
Traceability kept
Links between requirements, tests and results carry across projects.
Pick what counts
Exclude requirements from coverage when they shouldn't move the numbers.
Defects where devs work
Log defects in the project that owns the fix, then filter reports by project.
Cloud and Data Center
Set up by a project or Jira admin, on Jira Cloud and Data Center.
Frequently asked questions
Yes. Map other projects in Requirement Mapping, and their work items appear as requirements in your test project.
Yes. Link test cases to them, add them to Test Plans, and see them in Test Coverage and Traceability reports.
Yes. When a test fails, create the defect in the project that owns the fix, such as the dev team’s project.
Yes. Cross-project requirement mapping works on Jira Cloud and Data Center.
No. Mapped requirements stay in their own project and keep their own keys. AgileTest lists them alongside your own requirements.
Yes. Test Plans and Test Executions can include test cases from more than one project.
A project admin or a Jira admin, from the Requirement Mapping tab in AgileTest Settings.
More ways to manage quality in Jira
Test the whole release from one place
Map the projects behind your next release and see coverage and defects in one view.