Enable a bulk Search and Replace feature for Test Steps, allowing users to quickly update recurring text across one or multiple Tests without manual editing.

Description
Provide a native Search and Replace capability for Xray Test Steps in Jira Data Center, allowing users to find a keyword or phrase and replace it across all steps within a Test or across multiple selected Tests.

User friction

Users currently need to manually edit each Test Step

Steps to reproduce (right now) / Actual Result:

• Open a Test containing multiple Test Steps.
• Search for a specific keyword that appears in several steps.
• Attempt to replace the keyword across all steps.
• Observe that there is no native bulk search-and-replace functionality.

Actual Result: Users must update each step individually
IMPACT

Maintenance of large test repositories becomes time-consuming and error-prone whenever common text needs to be updated across Test Steps.

What would improve if solved:

• Faster maintenance of manual Tests.
• Reduced risk of missed updates and inconsistent documentation.
• Less dependence on custom scripts or API integrations.
• Improved usability for non-technical users.

Impact on stakeholders:

Increases maintenance effort and the risk of inconsistent updates for testers and test managers working with large test repositories.

Current workaround:

Users must manually open and edit the relevant Test Steps or fields one by one to locate and replace the desired text, which can be time consuming and prone to errors, especially when the keyword appears across multiple Tests and steps.

CONTEXT & EXAMPLES:

Organizations frequently need to rename applications, update URLs, modify environment names, or replace deprecated terminology across hundreds or thousands of Test Steps.

Concrete example:

A company migrates from:

https://oldportal.company.com to
https://newportal.company.com

The old URL appears in hundreds of Test Steps spread across multiple Tests. Users currently need to update each occurrence manually or develop custom scripts.

Workaround risk:

• Manual updates are time-consuming and prone to human error.
• API-based solutions require technical expertise and development effort.
• Incomplete updates can lead to outdated test instructions and execution failures.