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
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
oh I didn't realize that this setting already include the xray fields ... thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
yes, this is correct, for me this was the same I what to block all ticket changes after setting the ticket to done included all xray options/status etc..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
Hope this was helpful and solved your problem. If so: Please hit the accept button.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.