Page History
...
Xray provides some specific custom fields that calculate their values on the fly. This means that you should have that in mind, specially if you're including them in tables/issue listings/gadgets.- The most intensive custom fields are the field is the "Test Execution Defects" and the "Test Set Status" (isto ja nao é verdade, certo Diamantino Campos? há aqui algum custom field calculado em realtime a salientar?). => não é verdade no caso de já estarem calculados. O Test Set Status é muito mau, é de evitar o seu uso. The "Tests Count", as it does an aggregation, is also is intensive if you use it for multiple issues.
Reports and Gadgets
- 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.
Limit the target issues for the reports/gadgets, i.e. generate the Overall Requirement Coverage (report/gadget) just for issues that you really need and not all Jira requirements or projects; the setting "Max number of requirements per report or gadget results" (available under Miscellaneous) acts as a maximum limit for some reports/gadgets.
...