Configuration and Features
The behaviour of the Jenkins Integration for Jira app can be customized through configuration and features. Features are essential on or off configuration settings, whereas other configuration settings can contain other bit of information as well.
The Configuration dialog can be accessed on the main administration page of the app in Jira by going to Settings > Apps > Jenkins Integration > Configuration. Once the configuration dialog is open you can access the Features dialog by clicking on the Features button.
The Configuration dialog allows you to configure the following:
Jira Sync URL
This configuration setting allows you to change the sync URL that Jenkins plugin will use to communicate with Jira. By default this will be the same as the application URL that is configured in Administration > System > General Configuration. This can be useful if your Jenkins or Hudson instance should bypass a proxy in order to connect to Jira.
Maximum Builds per Page
This configuration setting allows you to limit the number of builds that are shown on a CI Builds panel, defaults to 100.
There are two types of features, system and site, System features are features that are either enabled or disabled by the app itself and cannot be customized. Site features however are features that administrators of a Jira site can enable or disable to customize the behaviour of the app.
|jira-jenkins-automation||Share synchronization events with the Jenkins Integration Automation for Jira add-on to trigger rule executions.|
|build-info-provider||Push build data to Jira when a build is synchronized and has links to valid issues. This data is then made available in the Development Panel.|
|deployment-info-provider||Push build data to Jira when a build is synchronized that represents a deployment to an environment and has links to valid issues. This data is then made available in the Development Panel.|
|dynamic-ui-elements||When enabled only show UI elements, CI Build Panels, Triggering Builds, Release Report, when the viewing issue or project has one or more builds linked to it. This can be useful in case you have multiple Jira Software projects in Jira but only a subset of them use the Jenkins integration.|
|disable-issue-indexing||Enabling this feature will cause the app to stop automatically updating issue indexes after a build is synchronized and will instead rely on Jira to perform the indexing.
Only enable this feature if directed by Marvelution support!