Bugs

When selecting a Due date for the Milestone on the drop-down calendar, it highlights and selects the day prior (in the screenshot example, 2025-07-28 was clicked, but it selects 2025-07-27). The correct date is displayed on the main Milestones page (the one the user clicked), but should be reflected on the Create Milestone and Edit Milestone pages.

Given I have a widget on my dashboard for Open Defects When a Defect is the "In Progress" state Then that Defect is not being shown in the "total" open defect accounts A defect in the "In Progress" state is still in an "Open" state and not resolved and should be reflected in this total. Note the "Open Defect" widget that presents in a timeline does keep the "In Progress" defects in the total accounts (as expected)

In your project settings, set "Default test case steps type" to Gherkin Raw. Update settings Under a suite, create a quick test Edit the quick test Bug: Says "Select value" and a value has to be set. Very time consuming having to select the whole time. Side note: When value is set to Gherkin steps or Classic steps, it works correctly when creating a Quick test. Side note two: When clicking on New Test > Create manually, then it works. But then you need to select a test suite. Also time consuming. Please fix! Thanks team :)

When linking cases to a requirement then later deleting some of those cases, the total number of test cases linked to the requirement stays the same when attempting to edit the requirement. Example: -Start with 10 test cases linked to a requirement -Delete one of the 10 test case (from repository) -When attempting to edit the requirement, it shows 10 cases but only 9 are listed against the requirement. Appears to still be including the deleted case.

Precondition: #pytest #xdist #qase-pytest Param 'Project settings - Test run - Auto create test cases' is enabled. Steps: Run the following paramterized pytest autotest first time, without decorator @ qase.id (case_id). ########### import pytest @pytest.mark.parametrize("version", [1, 2]) def test_example(version): pass ########### Expected result: Get one test case in qase.io with all params of paramterized pytest autotest. Actual result: Sometimes we can get two test cases with different params in qase.io .

Given a user is creating a Qase bug and linking to Jira When they select the "Parent" as a User Story Then the bug is not created in Jira & no error displays on Qase. Situation: The instance of Jira we have limits Parents to Epics; however, when a user of Qase selects a Story instead of an Epic they do not receive an error at the time of selection and the bug is NOT created in Jira. We did note there appears to be an error on Qase - but it's under Apps, this is not useful as the majority of our users do not use the apps tab.

When trying to edit an active test run, the screen hangs on loading. I have given it 3mins+ to resolve but did not.

We have encountered this twice in the past 2 weeks. We selected 1 test case to delete only, but it ended up deleted the whole suite(and more) instead without any prompt for confirmation. Over 2K test cases were deleted and we have to restore all of them 1 by 1 on the Trash Bin page.

Edited by Qase Support (as on Mar '25) - Add assignee in the results, when results are fetched from API Add option to specify (default) assignee when creating a test run with case ids specified. Add 'executedBy' / 'author' of result when fetching results from API