...
- Webooks
- Realtime-Enabled Projects
- Issue Export Limit
- Additional Export Options
- Event Auditing
- Export Locations
- Workflow Transition Post
...
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 13 14 additional export options available, with 12 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.
...
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 | ||||
|---|---|---|---|---|
|
...