eazyBI incident

Tempo worklog import is working only partially

Notice Resolved View vendor source →

eazyBI experienced a notice incident on June 18, 2018 affecting Web App, lasting 4h 47m. The incident has been resolved; the full update timeline is below.

Started
Jun 18, 2018, 01:56 PM UTC
Resolved
Jun 18, 2018, 06:44 PM UTC
Duration
4h 47m
Detected by Pingoru
Jun 18, 2018, 01:56 PM UTC

Affected components

Web App

Update timeline

  1. identified Jun 18, 2018, 01:56 PM UTC

    Tempo worklog attributes, Accounts and Teams are not being imported for now. This is due to Tempo API update (https://support.tempo.io/hc/en-us/articles/360001188087-UPDATED-Action-Required-for-APIs) and we are working to resolve the issue. When resolved, we will inform all affected account owners about further actions required.

  2. resolved Jun 18, 2018, 06:44 PM UTC

    The incident has been resolved. Tempo team has improved the Tempo worklog REST API as well as changed the authorization towards this API. To continue importing Tempo custom fields to eazyBI a new Tempo token needs to be added in eazyBI Source data / Jira / Add-ons page for all eazyBI Jira cloud accounts that are using Tempo import. To do this, please follow the steps below: 1. Open Source data tab and open Jira import / add-on page in eazyBI. Navigate to Tempo Settings (or do this from Jira by clicking the Gear icon on the Tempo sidebar > User Preferences, select API Integration). 2. Click Get token to generate a token. 3. Click the copy icon to the right of the token to copy the token to the clipboard. 4. Go back to eazyBI and paste the new token. 5. Make sure all necessary worklog attributes and custom fields are selected for import and run import to eazyBI. Please contact [email protected] to let us know if there are any questions regarding the steps above.