Many configuration tweaks can be made to Zephyr for JIRA. The following screen summarizes them:
Display workflow toolbar for Issues of type “Test”
By default, the workflow toolbar for a test is not shown when viewing it. If the workflow toolbar is needed for any reason, select this box.
Check for software updates
By default, Zephyr for JIRA checks for new software updates.
Associate IssueType "Test" on Project Create
By default, Zephyr for JIRA adds the issue type "Test" on every new Software or Business project that is created. If this is unchecked, then new Software or Business projects will not get the "Test" issue type. If you need to add it later, do so from that Project's administration page, Issue types section.
Zephyr Log Level
Zephyr for JIRA Server now writes easy-to-read logging information into its own log file. This file will have the details on the service calls, information message and error message details.
- Logging is initialized on the "plugin enabled" event and will default to INFO level
- After the plugin is initialized, all Zephyr for JIRA Server related logging would be written to the same level as Atlassian's JIRA log file
- $JIRA_HOME$/log
- The logging level can be changed at any time without server restart
- Default log rotation is set to 20MB and can be changed from the Zephyr for JIRA Server - General Configuration page
Zephyr Log Max Size
Maximum log file size of zephyr-jira.log
Zephyr Log Max Backup
Maximum number of zephyr-jira.log backup files
Enable Issue Security
By default, Issue Security is disabled. This feature allows users to add more control over the security of the test case itself.
Disable Test Summary Label Filters/All Filters
Administrators now have the ability to enable or disable the viewing of filters for labels or All on Test Summary page. By default, both options are disabled.
Show Create Zephyr Test on Issue Type(s)
Determine what issues types a Test issue can be created from in all JIRA projects. Selected issue types will have an additional option in the More Actions drop-down to allow creating test issues and linking directly back in one action.
Select an existing dashboard to associate with the “Test Metrics” menu item in the “Tests” menu
By default, the “Zephyr Dashboard” is selected when a user clicks on the “Test Metrics” menu item in the top-level “Tests” menu. This can be replaced with an existing dashboard by selecting that dashboard from the drop-down list here.
Enable issue link from issues to tests
By default, this is on, which means that when a defect is filed from a test execution, that defect (issue) will have a remote link pointing back to the test. Disable this if too many remote links are being created in that issue.
Enable issue link from issues to test executions
By default, this is on, which means that when a defect is filed from a test execution, that defect (issue) will have a remote link pointing back to that specific test execution. Disable this if too many remote links are being created in that issue.
Inverse issue link directionality
By default this is off, which means links are outbound from defects and inbound to tests (i.e. Test <-- Defect or in other words, Test "is blocked by" Defect and Defect "blocks" Test). Select this if you want them to go the other way around.
Configure LinkType for Test–> Defect relation
Link Types can be also be selected from here and applied to all existing links between Tests and Defects. 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.
Reset
Links are created between a test execution and a defect that it is associated with (this happens when a test is executed and during that process, either a new defect is created or an existing one associated). Sometimes the paths of these links change (e.g. if this JIRA instance is moved to another machine, or if Test Cycle names are modified etc.). Pressing the “Reset” button will ensure that these links are updated with the latest changes. Use this if users are complaining about these links not going to the right test execution. Be aware that this action might take a while to finish as it will go across all projects.
Re-indexing
Ever so often Zephyr for JIRA's indexes (alongside JIRA's indexes that apply to tests) need to be regenerated. Click on the "Re-Index" button if you are not seeing some of your information being updated. This might take some time based on the amount of data you have and users will not be able to use the system during that period.
Cycle Cleanup
Cleanup cycle indexes. Note: This may take a long time depending on data size