The Jira add-on allows an administrator to control some features that affect the add-on's behavior. Most configuration options are available from the add-on's Configuration screen.
- Webooks
- Realtime-Enabled Projects
- Issue Export Limit
- Additional Export Options
- Event Auditing
- Export Locations
- Workflow Transition Post
| Anchor | ||||
|---|---|---|---|---|
|
...
This section allows an administrator to define which projects' Jira events will trigger updates to real-time update exports. By default, every project is enabled. Administrators may find that some projects do not need to update exports, and disabling those projects here may provide a performance benefit. Jira events fired from issues in projects that are not enabled here, will be ignored. Note that this section and the Webhooks 2547482857 section work together; the add-on will only process enabled events on realtime-enabled projects. Users are still able to export issues from projects that are not enabled here, but changes to issues in those projects will not trigger real-time updates, even if the export itself is realtime-enabled.
...
This section allows an administrator to expose additional data export options for users to select on the Export screen. If any options are enabled here, an "Additional Export Data" item will appear on the Export screen, giving the user the option to export additional data to other tables in the selected namespace. Currently there are 8 14 additional export options available, with 7 13 of these options being configurable by a Jira administrator. Some options, such as Tempo Worklogs, are only available when the developer's app is installed and active.
Boards, Components, Issue Types, Projects, Sprints, Users, and Versions will each perform a full export of their data into their respective tables in the selected namespace. Depending on data type and update type, other exports such as Assets will only export data that has changed since the last time an update was performed on the export. In the case of Changelogs and Worklogs, only the data that relates to the issues present in the user's export will be exported into their respective tables.
Enabling the Time in Status option will allow users to populate a table in Snowflake that summarizes the status changes performed on each issue in their export, and includes the number of minutes that the issue spent in each status.
Enabling the Tempo Worklogs option will allow users to export data related to Tempo Worklogs, including billable time, review status, and associated attributes.
Enabling the Analytics Structure option allows each export to populate a number of bridge and dimension tables within Snowflake that help to perform additional data analysis and visualization in Business Intelligence platforms such as Microsoft Power BI.
The final export option available to users, Field Mapping, is not configurable by a Jira administrator because it does not require additional API calls. Any user can export this data into the selected Snowflake namespace.
| Anchor | ||||
|---|---|---|---|---|
|
This section allows an administrator to enable additional auditing to record actions performed by the app, including which types of updates were performed by which users, which tables were updated, how much time was required to perform the updates, and whether any errors were encountered. These records are stored in the S4J_EVENT_AUDIT table in Snowflake. Additionally this will record details about any issue keys requested from Jira that either are not returned, or could not be inserted into Snowflake. These records are stored in the S4J_EVENT_AUDIT_ISSUES table in Snowflake.
| Anchor | ||||
|---|---|---|---|---|
|
...
After saving your Export Locations selections, users will see a Database/Schema item on the Export screen that, when clicked, will display a database selection drop down with the databases you specified.
If a user does not pick a database from this drop down when creating a new export, the export will be stored in the first available database.
...