---
title: "Quick Setup"
canonical: "https://docs.getxray.app/space/XRAY/301502490/Quick%20Setup"
format: markdown
---
After installing Xray, there are basically two steps you need to make or ensure before starting to use it.
> Macro (toc)
## Configure Requirements and Defects
In Jira's administration, in the Add-ons tab, go to Issue Type Mapping and configure what issue types should be considered as "requirements" and "defects".
> ⚠️ Xray Issue Types (Test, Test Plan, Test Set, Test Execution, Sub-Test Execution and Precondition) MUST NOT be mapped as Requirements nor Defects.
> ℹ️ **Learn more**
> ℹ️
> ℹ️ Refer to the specific [Issue Type Mapping](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301473147) page or take a look at the extensive [Administration & Configuration](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301501144) if you want to fine-tune Xray or adapt it to your specific needs.
## Enable Xray in your projects
You can enable Xray for your existing projects or create a new project with both standard and Xray issue types.
### Enable testing in existing projects
For existing projects, in the project Administration page, go to Actions at the top right-hand side. You can either:
a) set your project as a Requirements project by choosing "Enable Xray Requirement Coverage", so the requirements are covered by tests; or
b) add Xray issue types (i.e., Test, Test Set, Test Execution, Test Plan) to the project.
> ℹ️ **Please note**
> ℹ️
> ℹ️ Since the Issue Type Scheme being used by your project may also be used by other projects, in order to add Xray's Issue Types from the project settings page you must belong to a group allowed to do so in Xray settings. The allowed groups to add Xray Issue Types can be defined in [this setting](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301407212/Miscellaneous#User Groups allowed to add Xray Issue Types).
> ℹ️ **Learn more**
> ℹ️
> ℹ️ - [Configure Jira project to be used as Requirements project](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301406021)
> ℹ️ - [Configure Jira project to be used as Xray Test Project](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301665624)
> ℹ️ - [Configuring Xray with an Existing Project](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301698139)
### Create new projects from scratch with testing enabled
If, instead, you want to quickly create a new project and use it to manage everything (e.g., requirements, defects, tests), go to the Jira Administration page for Projects. In the creation dialog, choose "Xray Test Project".
> ℹ️ **Learn more**
> ℹ️
> ℹ️ See [Creating a Test Project using an Xray Template](https://getxraydocs.atlassian.net/wiki/pages/createpage.action?spaceKey=xray&title=Creating%20a%20Test%20Project%20using%20an%20Xray%20Template&linkCreation=true&fromPageId=301502490).
## Configure Test Case Designer
Test Case Designer is a cloud powered feature and requires user to make an initial configuration to allow access.
> ⚠️ To enable Xray Test Case designer you need to make sure that Jira is at in 8.22.x or higher.
> ⚠️
> ⚠️ Additionally, for Jira/Xray Data Center, it is important to understand the connectivity flow for Test Case Designer and what is required to make it work.
> ⚠️
> ⚠️ - When a user clicks to open Test Case Designer (TCD) on your instance, that action triggers a request from the user browser to our IP address. As part of that request, the authorization code provided by your Jira server is given to our TCD server. We then take that code and use it to connect to your Jira server and ask it to verify it and give us an access token for the user, which we then use to request the user's profile on the Jira server.
> ⚠️ - If authentication is successful, eventually a user will want to use the API connection to sync tests back to Xray. For that, TCD uses Jira REST APIs to create or update work items
> ⚠️ - If a user wants to associate tests to a Test Set or a Test Plan, TCD uses Xray REST APIs.
> ⚠️
> ⚠️ Since in bullet 2 TCD will need access to your Jira, the purpose of the authentication (bullet 1) **includes** allowing TCD server to connect to your Jira server on behalf of the user. So, when a user clicks the “Allow” button, TCD makes the request to your DNS and, if records cannot be found, gets the NXDOMAIN status back, blocking the connection.
> ⚠️
> ⚠️ Therefore, we would need the client side to allow that DNS connection to enable both the initial access and the later sync of tests from TCD to Xray.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
>
> You will now be able to see the new option on projects menu for Test Case Designer
> > Macro (inline-media-image)