BigQuery Connector for Jira (DC)
Breadcrumbs

Administering the App

You can adjust BigQuery Connector for Jira settings on a single page. The instructions below will guide you in locating app settings page and provide an overview of all available configuration options.

Platform administrators always can view, modify, delete, and edit the share settings of any existing connectors in an instance.

How to Get to The Settings Page

There are 2 options for how to get to the application settings page. Feel free to use the one that is more convenient for you.

Option 1

  • Being signed in to your Jira instance, select BigQuery, and then select Administration.

bq_connector_for_jira_dc_administration_option1.gif

Option 2

  1. Being signed in to your Jira instance, select ⚙️, and then select Manage apps.

pbi_connector_by_tempo_dc_admin_2.gif
  1. Scroll down, look for BIGQUERY CONNECTOR FOR JIRA, and then select Plugin settings.

bq_connector_for_jira_dc_administration_option2.gif

Settings Page Overview

BigQuery Connector for Jira Settings page includes the following settings:

  • Permission Settings

  • General Settings

The page also has the Reset to defaults button.

bq_connector_dc_settings_overview.png

Reset to Defaults

Reset to defaults - This action will restore all app settings, delete all data sources and their settings, and delete all users permissions.

  • Select Confirm, if you do want to reset all settings and delete data sources.

  • Select Cancel, if you no longer want to do it.

bq_connector_for_jira_dc_administration_settings_reset_to_defaults.gif

Permission Settings

Here Jira administrators can grant permissions to users to create, edit, view, and export connectors.

  1. In the Users field, enter the username you want to grant permissions to.

bq_connector_for_jira_dc_administration_users.png
  1. In the Groups field, enter the group name you want to grant permissions to.

bq_connector_for_jira_dc_administration_groups.png
  1. In the Project Roles field, enter the role(s) you want to grant permissions to.

bq_connector_for_jira_dc_administration_roles.png
  1. Select the Edit icon, if you want to make changes.

  2. Select the Clear button, if you want to delete permissions.

Selecting the Clear button, you will erase information from all fields: Users, Groups, and Project Roles.

bq_connector_for_jira_dc_administration_edit_and_clear.png

General Settings

The General Settings help to:

  • prevent misuse of the app

  • alleviate the significant strain on Jira

  • improve time to export

Issues limit - This setting allows you to set a maximum number of tickets that can be exported at the instance level.

Fields threshold - This settings allows you to set a maximum number of fields that can be exported without a warning message.

bq_connector_for_jira_dc_administration_general_settings.png

Getting App & Export Logs

App & Export logs are now fully integrated with Jira logging.

To get logs:

  1. Being signed to your Jira instance, select Settings, and then select System.

app&export_logging_1.jpg
  1. Select Troubleshooting and support tools, and then select Create support zip.

  2. Select Create zip.

Make sure Jira application logs is enabled.

app&export_logging_info_panel.jpg
app&export_logging_2.jpg
  1. Select Download zip.

app&export_logging_4.jpg

The log file is downloaded to your device.

Changing Log Levels

If you need more detailed logs - for example, when investigating an issue - you can change the logging level at runtime in the Jira administration UI.

To change logging level:

  1. Being signed to your Jira instance, select Settings, and then select System.

app&export_logging_1.jpg
  1. Select Logging and profiling.

app&export_logging_log_level_2.jpg
  1. Find the app logger.

  • For BigQuery Connector, they are the following:

io.tempo.bigquery-connector-jira.app
io.tempo.bigquery-connector-jira.export
  1. Select the desired logging level by clicking on that.

bq_connector_dc_logging_level.png

Logging Level Description

Log Level

What to Log

Examples

ERROR

Critical errors that prevent operation or indicate failure

Exceptions, stack traces, failed export reasons, system error causes

WARN

Potential issues, recoverable problems

Invalid configurations, deprecated API usage, non-critical failures

INFO

High-level operation flow

Export started/completed, plugin initialization, user actions, MDC

DEBUG

Detailed internal plugin behavior

REST requests/responses (truncated), service method calls, conditional logic, state, MDC

TRACE

Full step-by-step execution, method arguments, very detailed diagnostic info

Every method entry/exit, arguments, return values, thread info, detailed state, detailed MDC

At the moment, the output of the following tables is being logged.

Jira Core

Jira Software

Service Management

Tempo

Insight

Xray

Tempo Budgets

  • Issues (Issues, Issue Effort, Parent Issues, Epics)

  • Issue Links

  • Issue Custom Fields (Issues or custom table)

  • History (Histories, Time in Statuses, Time at Assignee)

  • Projects

  • Sprints

  • Sprint Issues

  • Boards

  • Board Charts

  • Sprint Report Charts

  • Burndown Charts

  • Board Issues

  • Approvers

  • Customer Request Type

  • Request Participants

  • Customer Request Type

  • Request Participants

  • Another Service Management Fields (Issues)

  • Tempo (Issues)

  • Teams

  • Object Schema

  • Object

  • Object Type

  • Object Type Attribute

  • Status Type

  • Role

  • Insight Attribute Value

  • Test Runs

  • Folios

  • Expenses

  • Human Resources

  • R

  • ates

  • Allocations