A Step Library collection is shared content. Updating it can change the instructions in several Test Cases and versions, including cases in other Jira spaces. Review its usage before saving a change.
Check where the collection is used
Open Step Library from the Test Repository menu, or open the collection from a Test Case’s shared script block.
Select the collection and open Traceability.
Review Used in. Check the Jira space, Test Case, version, and position for each listed usage.
Open the relevant case links and confirm whether the proposed change is appropriate for those workflows.
The usage list shows cases you can access. An empty list does not prove the collection has no references elsewhere. Ask the owning team to help review changes when the collection is shared more widely.
Decide whether to edit or create a separate collection
Situation | Suggested approach |
The same common procedure changed for every linked case | Update the shared collection after checking its impact. |
One workflow needs different instructions | Create a separate collection and use it in that workflow. |
A case no longer needs the procedure | Remove that collection reference from the selected case version. |
For example, updating the common sign-in page location may suit every linked case. Adding an administrator-only step to a shopper sign-in collection usually calls for a separate collection.
Edit and save the shared instructions
Open the collection’s Test Script tab. Select Edit collection if it is not already editable.
Update the actions, Test Data, Expected Results, or Plain Text procedure as appropriate.
Finish any open step edits and wait for uploads to finish.
Select Save for the collection.
Reopen the collection and inspect the saved content. Review representative linked case versions to confirm their scripts.
Your account needs permission to edit Test Cases in the space where you are editing the shared collection. Shared content is not a private copy of the case where you opened it.
If Vansah reports that the collection changed, reload it and compare the latest instructions before saving again. Another user may have saved an update.
Understand what changes
Area | Effect of a shared content update |
Referencing Test Case scripts | Linked script content and step order are updated across references. Review every affected workflow. |
Unrelated case steps | They remain outside the shared collection block. Check the full procedure after adding, moving, or removing collection steps. |
Existing Test Runs | Runs use their stored execution script. Editing the collection does not by itself replace those stored steps or record new test results. |
If an existing run needs revised instructions, review Update a Test Run to the Latest Script Revision before choosing that separate action.
Review the change history
Expand the collection’s Activity area and select History to review recorded changes. Use comments to explain a change or request a review. Case history also records updates to referenced collections.
For insertion or removing a Multi Steps block, see Add a Shared Step Collection to a Test Case. For a new independent procedure, see Create Reusable Test Steps in the Step Library.