Yes. Please refer to the Time Tracking documentation.
Upgrades are managed automatically by our team and the process is transparent to you.
There is no "Requirement" issue type installed by Xray. In fact, Xray does not install any requirement-related issue types. If you had the opportunity to attend one of our webinars, particularly one similar to the Xray walkthrough, you will learn that with Xray, you are able to define which issue types Xray should consider as requirements so you can cover them with Tests. Besides the standard "Story" and "Epic" Jira issue types, Jira allows you to create your own issue types. You just need to configure Xray properly, as detailed here, to let Xray internally treat those issue types as requirements.
You need to ensure that your issue type is configured to be handled as a Covered Issue Type (i.e., a testable entity) This can be done in Project Settings: Test Coverage.
Also check out the Quick Setup for an overview of the initial setup steps you need to follow.
Yes. A Test is like a test template. You can use it in multiple Test Sets or Test Executions, which may be assigned with different versions.
The association of a Test with a project version is not direct. Your Tests are written in order to validate some requirement, that itself belongs to a specific version. Although a Test may be associated with a requirement of a specific version, you are able to run Tests for the versions you like. In terms of requirement coverage, you have different behaviors to choose from in the administration settings (see Requirement Coverage Strategy). You may also to have a look at Tips for implementing Test Versioning.
Please refer to Tips for implementing Test Versioning.
Please take a look at Tips for organizing tests.
Yes. You can create normal links between Test issues, as you would do for any standard Jira issue. Xray will not process those relationships in any special way; it will ignore them unless they are of "tests" or "tested by" relationships.
Not yet.
You can do it easily within the Test Plan screen via the "Create Test Execution" button. You may also create a new Test Execution for some of the tests listed in the table below the Filters. Select one or more tests (you may use a filter to help you out) and then choose the action available in the button next to the bulk selection (e.g., "(xx) Selected").
Not yet.
No, but if you execute the same tests in different environments, you certainly will find it as the most useful and accurate way of testing a requirement.
No. It’s up to you to organize your Tests per environment.
Xray does not provide this feature out-of-the-box. However, you may use a simple tool dedicated to taking screenshots (e.g., LightShot) and easily attach the screenshot to the evidences during the execution of the test.
A bit of both. A Test Plan contains a list of Tests. For calculating the status of each test, it takes into account test runs from Test Executions explicitly linked to the Test Plan, through the field “Test Plan”.
Not yet.
Yes, if you wish to track different groups of Tests (e.g., regression tests versus tests for new requirements).
You don’t have to, but there are great advantages if you start using them.
A sub-task can only have one parent issue, so it won’t be possible to have multiple requirement issues with the same Sub-Test Execution. However, you can add Tests from another Requirement issue to a Sub-Test Execution. You’ll be able to execute them, but you are going to have the same behavior as the Test Execution, while using Agile Boards. So, if you intend to track the executions in the Agile Board, we recommend that you have a Sub-Test Execution for each coverable issue.
The Tests already linked with the coverable issue will be automatically added to the Sub-Test Execution. You can remove them if you want. If you add a new Test to the Requirement issue after creating the Sub-Test Execution, then you’ll need to add them manually.
Xray does not install any "default" workflow for the issues it provides. You may define whatever worfklow you think fits best your scenario/organization. Xray is workflow-aware though, and provides some configurations specifically for that purpose (see Project Settings: Miscellaneous).
More information can be found in the Xray section of the Atlassian's Marketplace.
If you have a paid or trial license and it expires, you won't be able to use the Xray app.
Yes. Even for trying Xray, you need a trial license. More information can be found in the Xray section in Atlassian's Marketplace.
Yes, up to 5 times. More information can be found in the Xray section in Atlassian's Marketplace.
If, for some reason, you need to uninstall Xray, you can do it safely. No relevant data is removed from Jira. This means that Xray issue types, custom fields, Xray settings and all recorded information related with testing is kept.
Note: If you uninstall and install Xray once again, nothing special should happen. In other words, it should be idempotent.
Currently, this is not possible.
Please see our EULA and Security Statement. Xblend has also successfully completed Atlassian's security self-assessment program.
Xray Cloud integrates with Atlassian Cloud infrastructure; therefore, we'd recommend having a look at a Atlassian documentation on security, reliability, privacy and compliance.
We really prefer that you contact us through our Service Desk, so the right person can properly address your question asap.
Sure. Please leave us a message in our Service Desk and we'll get back to you right away. We also have webinars (both live and recorded) that you can attend.