nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Disable option to edit Xray Test Steps

oliver.schulz

hi,

we use the Xray Add-on for our test management.

Is it possible to 'freeze' the xray fields (test steps) in a ticket? Maybe combined with the ticket status, e.g. you can't edit a closed test.

Like the jira.issue.editable setting for the default jira fields.

Thanks

Accepted answers

Stefan Salzl

Hi @oliver.schulz

you could indeed use the following workflow property at any specific workflow status:

jira.permission.edit.denied

It kinda looks ugly as it let´s you do changes but throwing an error when trying to save but it does the work (avoid changes on closed tickets).

Best
Stefan

All comments

Stefan Salzl

Hi @oliver.schulz

you could indeed use the following workflow property at any specific workflow status:

jira.permission.edit.denied

It kinda looks ugly as it let´s you do changes but throwing an error when trying to save but it does the work (avoid changes on closed tickets).

Best
Stefan

oliver.schulz

oh I didn't realize that this setting already include the xray fields ... thanks!

Stefan Mengele

Hi, i have the same issue and set already the "jira.permission.edit.denied" flag in the workflow for Jira ticket status "DONE". The result is that i can not change my ticket entries but still the test status of the xray add on from "PASSED" to any status.

Can I prevent to change the test status in the "Done" status of the Jira ticket?

Stefan Salzl

Hi @Stefan Mengele

apparently it´s not the same issue. The original post was about "preventing test steps to be edited within a test case issue when test case is in status done".

The problem you describe is "preventing test runs to be changed within a test execution issue when the test execution issue in status done".

Is that correct?

Best
Stefan

Stefan Salzl

Hi @Stefan Mengele

I´ll post this as a seperate answer as it covers another context. In general a new question should be created if it´s not exactly the same issue (in your case it was another issue type and another section of an issue).

I know it´s not always that obvious and it can be confusing (especially in the context of XRAY) as those issue types behave differently and eg. the test execution issue contains of test runs, which is a section of "objects" that lives within xray and test executions but they are not native jira issue on their own =S

sooo....regarding your question:

If you would like to have all native fields of your test execution issue prevented from being edited then the workflow property as described above is the way to go. As mentioned this covers all jira native issue fields but not the test run. therefore -->
there is an option in the project settings/xray/misc to disallow executions/runs within a specific workflow status (see screenshot). This will prevent any test runs in the test execution issue to be run

Hope this was helpful and solved your problem. If so: Please hit the accept button.

Best
Stefan

Stefan Mengele

Hi, this was exactly what I need, thank you so much

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

xray

jira

cloud

jira-software

jira-software-cloud

test-management