Feature Requests

Right now the custom fields are ordered in chronologically from time of creation, we want to be able to set the order as we want, maybe even at the Project level if possible, if not in the https://app.qase.io/workspace/fields

Feature Request: Introduce an archiving feature to manage unused test cases while preserving their full history and metadata without inflating repository size or losing change records. Problems now: • No efficient archiving: Current options require either moving test cases to a new suite (which increases repository size) or cloning them to a separate archive project (which doesn’t preserve their change history). • Can't delete them because: The trash bin lacks filtering and viewing options, making it hard to recover or manage deleted test cases. Proposed Solutions: Labeling for Archival Management: • Enable users to label TCs with tags like “Archived,” “Trash,” or other custom names, organizing inactive TCs within the same project. Improve Trash Bin options: • Add filtering and search functions in the trash bin to help locate deleted TCs. • Enable viewing of TC content directly within the trash bin to support informed recovery decisions. Flexible Clone and Restore Options: • Provide an option to transfer TCs between projects without losing their history. Why this is important: As projects evolve, archiving is essential to manage TCs effectively without losing valuable data or cluttering the repository.

Sometimes it is needed to mark several steps in a case as automated and others as manual

It would be helpful to display the preconditions of the suite in the test case editing page so as to avoid unnecessary repetition, either in the preconditions of the test case or in the test steps of the test case. It also would avoid the need to open multiple Qase tabs to verify the suite preconditions.

Add the ability to save parameter/values as "shared" so that they can be selected for multiple test cases.

Description: Currently, our test management platform lacks the ability to archive test cases that have become obsolete or irrelevant. While we have the option to mark them as deprecated or delete them, neither of these options is ideal. Deleting them outright may result in the loss of valuable historical data, while marking them as deprecated still clutters the test suite visually. Requested Feature: We propose the implementation of a feature that allows users to archive test cases. Archiving a test case would remove it from the active test suite, making it invisible in day-to-day testing activities, but preserving it for historical reference and audit purposes. Benefits: Keeps the active test suite clean and focused on current testing needs. Preserves historical test case data for future reference and auditing. Provides a non-destructive alternative to deleting test cases. Implementation Suggestions: Introduce an "Archive" option alongside "Deprecated" and "Delete" for test cases. Archived test cases should be easily retrievable for viewing and reporting purposes. Provide the ability to restore archived test cases if needed. Additional Notes: Archiving test cases will enhance the organization and efficiency of our testing process while ensuring that valuable historical data is retained for future use.

Right now the only way to see suite precondition in repository view is to open Edit menu. It will be great if we will be able to see suite precondition in test case view here (see the screenshot attached)

Currently , the webhook payload for case.updated in Qase does not any include details about what was updated in a test case, only the event and the ID of the affected case. { "payload": { "id": 7163 }, "timestamp": 1726049640, "event_name": "case.updated", "project_code": "QD", "team_member_id": 20 } To improve the integration and support automation workflows, it would be beneficial to include additional details about the specific updates made. For example, in a workflow aimed at automating the process of creating Jira tickets when a custom field in Qase is updated to a specific value - the current payload from the webhook endpoint does not provide details on what exactly was updated within the test case. Proposing , to update the webhook payload to include details about the specific changes made to the test case. This could include fields that were updated, their previous values, and their new values.

I would like to edit rich text fields directly using markdown syntax, so that when I save, the text will be formatted as I intended. e.g. # Heading 1 ## Heading 2 `code snippet` - bullet - bullet - bullet | theader | tcolumn | tcol2 | | -------- | -------- | ----- | | tdata | tdata | tdata | - [ ] checkbox - [x] checked checkbox I need to highlight these ==very important words== I just love **bold text** let's separate this section from the next using a horizontal rule ------- voila!