...
Link Types can be selected from here and applied to all existing links between Requirements and Tests. Different link types can be set up in JIRA's configuration and they can be selected from the drop-down menu here. By default, "Relates", "Blocks", "Cloners" and "Duplicates" are available.
Re-Index
Re-Indexing
Ever so often Zephyr for JIRA's indexes (alongside JIRA's indexes that apply to tests) need to be regenerated. This can help in various cases when and is a common requirement when information is being updated consistently and accurate information is not being displayed in JIRA. Administrators can re-index all projects or just a selection of some projects from here. Once the projects have been selected, click on the Re-Index button. This might take some time based on the amount of data and users present in the system.
Users are also able to perform two types of re-indexes. By selecting a project and clicking "Re-Index", this performs a soft re-index which essentially overwrites previous index and adds on the new index. This process is the general option and will be the most likely re-index to be performed as it significantly reduces the time spent on re-indexing. By performing a soft re-index, it cuts the time from hours to minutes. The other option is to perform a hard re-index which completely deletes the previous indexes and it then performs a full re-index.
...
Ever so often Zephyr for JIRA's indexes (alongside JIRA's indexes that apply to tests) need to be regenerated. This can help in various cases when and is a common requirement when information is being updated consistently and accurate information is not being displayed in JIRA. Administrators can re-index all projects or just a selection of some projects from here. Once the projects have been selected, click on the Re-Index button. This might take some time based on the amount of data and users present in the system.
| Info |
|---|
For reindexing, we require the customer to take one of the Nodes off the Load Balancer and reindex on that node. This is done to prevent any incoming request on that node. If a re-index is done once and then a hard re-index is performed, it will delete the previous snapshot time in the database and update to the latest time index. |
...