Page History
...
- Execution results can be imported even though the Test issue is archived
- For archived Test Execution it will return an error
JQL Functions
The cases noted in the table below are not necessary wrong, but due to their peculiarity deserve some reflection.
JQL function | note |
---|---|
requirements | The Requirement Status is still affected by the archived. It will return same results as if Test issue wasn't archived. |
requirementsWithStatusByTestPlan | The Requirement Status is still affected by the archived. It will return same results as if Test or Test Plan issue wasn't archived. |
testTestSet | Returns associated issues, even if issue passed as argument is archived. |
testTestSet | Returns associated issues, even if issue passed as argument is archived. |
testsWithNoTestSet | Returns associated issues, even if issue passed as argument is archived. |
testPreConditions | Returns associated issues, even if issue passed as argument is archived. |
preConditionTests | Returns associated issues, even if issue passed as argument is archived. |
testRequirements | Returns associated issues, even if issue passed as argument is archived. |
requirementTests | Returns associated issues, even if issue passed as argument is archived. |
testExecutionTests | Returns associated issues, even if issue passed as argument is archived. |
testTestExecutions | Returns associated issues, even if issue passed as argument is archived. |
testSetPartiallyIn | Returns associated issues, even if issue passed as argument is archived. |
testSetFullyIn | Returns associated issues, even if issue passed as argument is archived. |
testPlanTests | Returns associated issues, even if issue passed as argument is archived. |
testPlanTestExecutions | Returns associated issues, even if issue passed as argument is archived. |
testPlanRequirements | Returns associated issues, even if issue passed as argument is archived. |
testTestPlan | Returns associated issues, even if issue passed as argument is archived. |