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
- 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 2547482857 Webhooks 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 set a limit on the number of issues that can be exported at one time. Since larger exports take more time and resources to generate and update, limiting the number of issues in the exports can help improve performance. The default limit matches your Jira instance's setting (jira.search.views.max.limit in Jira Server or Data Center, or is 1,000 in Jira Cloud). To allow an unlimited number of issues, set this value to -1. Any limit set here applies to all exports created by the add-on.
...
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 databasenamespace. Currently there are 8 additional export options available, with 7 of these options being configurable by a Jira administrator.
Components, Issue Types, Projects, Users, and Versions will each perform a full export of their data into their respective tables in the selected namespace. In the case of worklogs, all worklogs for Changelogs and Worklogs, only the data that relates to the issues present in the user's export will populate the S4J_WORKLOGS table in the selected Snowflake database.
be exported into their respective tables.
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 define Snowflake databases namespaces where users can store their exports. For each database in the list, check its checkbox if the checkbox for the schema(s) were you would like to allow users to create exports in that database.
Note: Only databases with a "PUBLIC" schema are shown in this section.
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.
...