📌 February FAQs with Answers

Practi-Talk
1

Hi everyone!

Here’s a quick roundup of some of the most common questions we received in February👇

:one: How can I update a field value in many tests at once?

You can easily update multiple tests using Batch Edit:

  1. Select the required tests by clicking the checkbox next to each one.

  2. Click “Batch Edit.”

  3. Update the relevant field values for all selected tests at once.

This is especially helpful when making bulk updates after requirement changes or sprint adjustments.

:two: Can I create a custom view of all issues found during the current regression testing that have not been resolved?

Yes, and there are two ways to approach this:

:white_check_mark: Option 1: Use a Custom Field in the Issues Module

  1. Create a custom field in the Issues module (for example, Test Level).

  2. Add a value such as “Regression” and tag all issues found during regression testing accordingly.

  3. Make sure issue statuses are updated correctly.

  4. Create a filter with these criteria:

    • Test Level IS Regression

    • Status IS Open/Unresolved

    • Created from (insert relevant regression dates)

This will give you a focused view of unresolved regression issues.

:white_check_mark: Option 2: Use a Cross-Filter

If you already have a filter in your Test Sets and Runs module (e.g., “Current regression testing”), you can use it as a cross-filter inside the Issues module for more dynamic tracking.

:three: How can I make sure that my testers populate the fields that are necessary for reporting?

To ensure consistency and accurate reporting:

  1. Go to Project Settings → Fields

  2. Navigate to the relevant field

  3. Mark the field as Mandatory

This guarantees that required data is captured before testers can proceed.

:four: How can I create a report showing all instances and their statuses that were run during a specific sprint?

Here’s a structured way to do it:

  1. Create a custom Sprint field in Test Sets and Runs.

  2. Make sure the Sprint field is populated for every Test Set executed during that sprint.

    • You can also update past Test Sets retroactively using Batch Edit.

  3. Create an auto-filter in Test Sets and Runs using the Sprint field as the criteria.

  4. Go to Reports.

  5. Choose Instance Tabular Summary Report.

  6. Apply a Test Set–level filter using the Sprint field and select the relevant sprint.

You’ll now have a clear view of all instances and their execution statuses for that sprint.

If you have follow-up questions on any of these, or want to share how your team is handling similar workflows, drop a comment below.

See you in next month’s FAQ recap! :rocket: