Hello,
I have seen documentation explaining that the fields ‘affects version’ and ‘fixed versions’ are for example:
Affects version is the version in which a bug or problem was found. Although it can be useful for tracking problems, it isn't used very often in Jira. Fix version is the version where you plan on releasing a feature or bugfix to customers.
The questions I have based on the explanation of the purpose of these two fields are:
Thank you
Hi @h kay
Going straight to your questions:
Why are these two fields displayed in my Xray test, test executions, test plans issue types(...)?
Those fields are displayed on the Xray issue types by default, due to clients' demand on the earlier stages of the product.
(...)should we be using them here? e.g. if I populate fixed version with my release number, the test issue type is displayed under the release when really I would expect only requirements displayed under the release as releasable items (i.e. user story and bugs)
That is entirely up to you, we have seen many different version usage from our clients, and it is up to the customer to understand its company work methodology and actions.
Based on the answer to Q1, is it possible to not display these fields in my Xray test issue type?
Of course, you just need to remove them from the issues screens on your project, and they won't be displayed.
Are there any other ways to track these test issue types were used for a specific version xx.xx?
It is possible to do so using some of our built-in reports and enhanced JQL functions.
If you have any more questions, please reach out to us through our service desk.
Best Regards,
Team Xray
Hello Xray team,
Is there a way to configure Xray so that when Tests are created they do NOT inherit the requirement Fix version field?
It is very annoying to have to do it manually for any single test and people simply forget to do it...
Thank you in advance,
Claudio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is the current behavior of Xray.
However, we have this improvement suggestion (XRAY-4365 ) reported and gathering the interest of our customers.
Please vote and watch it so that you can receive email alerts.
Thanks.
Kind regards,
Rogério Paiva [Xray Support Team]
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.