...

This document provides somes tips to improve performance of your Jira instance while using Xray.

Xray is As Xray is built on top of Atlassian's Jira, therefore is mostly dependant on the architecture and technologies followed by Jira itself.

Atlassian provides some metrics and peformance tips related with scaling, that also apply to Xray.

Therefore, the first thing to make first thing you neeed to make sure is that your Jira instance is properly configured and tunned beforehand. Thus, you may deploy Xray confidently and follow the tips provided herein to make sure it will keep performing great.we recommend looking at Jira specifics section first.

After ensuring your Jira instance is fine-tuned, then you may proceed to Common Tips as they apply both to Server and Data Center based deployments. In the end of the document, you have some specific Data Center Tips that complement the previous sectionLarge organizations or organizations with huge amounts of data and/or having many users should consider Jira Data Center, which increases performance and improves throughput on higher concurrency usage scenarios; it also provides high-availability for critical scenarios.

Background

Xray mainly uses Jira issue types for implementing Test Management related entities, such as:

...

•  - major
•  - highest
•  - high
•  - medium
•  - low
•  - lowest

Jira specifics

 Xray is built on top of Atlassian's Jira, therefore is mostly dependant on the architecture and technologies followed by Jira itself.

Atlassian provides some metrics and peformance tips related with scaling, that thus also apply to Xray.Therefore, the first thing to make sure is that your Jira instance is properly configured and tunned beforehand. Thus, you may deploy Xray confidently and follow the tips provided herein to make sure it will keep performing great.

Large organizations or organizations with huge amounts of data and/or having many users should consider Jira Data Center, which increases performance and improves throughput on higher concurrency usage scenarios; it also provides high-availability for critical scenarios.

1. moderate the usage of custom fields
   

   1. Managing custom fields in JIRA effectively

   2. Optimizing custom fields
2. ??

Process

1.  "Unified" development process: define a process that can be applied to all teams in the way how to manage the STLC. Every team is different and has its own needs, therefore your process should not be too strict but it should provide some guidance on how development life cycle should be addressed, covering requirement management, bug management and test management. Having teams working completely in different ways, hardens communication and leads to unproper and unoptimized tool usage. If you have a well-defined process that can be used organization wide, better; this is the key to ensure an optimal usage and have the best performance.
2.  Are you adopting Agile and Scrum? Check out Using Xray in an Agile context for tips on how you can take advantage of Xray in such scenarios;. Agile software development page provides high-level overview of Agile and Agile Testing and besides background information on them, it will also provide some useful tips so your team can be more Agile and avoid doing things that are unnecessary.

...

• quais outros settings podem ter mais impacto na performance? separation of concerns?

Reports and Gadgets

1.  One way of doing reporting is by using gadgets. Gadgets are great to share information between team members and even between different teams; however, if not use carefully, they can degrade JIRA performance if all users have the same report on their dashboard as they will probably generate multiple requests once users access the dashboard. Thus, use carefully most intensive gadgets such as the "Historical Daily Requirement Coverage" and the "Tests Evolution" gadget and others that do aggregations (e.g. "Test Runs Summary" gadget). Gadgets that just "list" entities should not affect performance significatively.
2.  Limit the target issues for the reports/gadget, e.g. generate the Overall Requirement Coverage (report/gadget) just for issues that you really need and not all Jira requirements or projects.

...