Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When a report is created using the Reports and Timesheets for Jira app, it is recommended to follow the instructions given on: How to ensure AIO reports accessibility if the creator is removed, to maintain the accessibility to this report in case the user is not available. If these instructions were not followed before the user is inactive, it is possible to change the ownership through the database (Data Center instance) following the instructions below:

\uD83D\uDCD8 Instructions

Step-by-step guide.

Info
  • Please note these steps should be performed on a Staging or Test instance first and once is confirmed that all is good, perform those changes on Production.

  • It is always a good practise and a recommended to take a back up of the production database.

  1. Identify the user who owns the lost reports.

    1. For this is necessary to analyze the content of the app_user table and look for the user_key that belongs to the user with a particular username. An SQL query example is below:

      Code Block
      SELECT "user_key" FROM "app_user" WHERE "lower_user_name" = '<username>';
  2. With the user_key, after analyzing the content of the AO_6B9F04_AIO_USER the owner_id will be obtained. The SQL example is below:

    Code Block
    SELECT "ID" FROM "AO_6B9F04_AIO_USER" WHERE "ACCOUNT_ID" = '<user_key>';

...

  1. List all reports owned by this user, the SQL example is the following:

    Code Block
    SELECT "ID", "NAME", "OWNER_ID" FROM "AO_6B9F04_AIO_REPORT" WHERE "OWNER_ID" = '<owner id for that user>';
  2. Update the owner for all the reports identified in the previous step. An example SQL query is below:

    Code Block
    UPDATE "AO_6B9F04_AIO_REPORT" SET "OWNER_ID" = '<new owner id>' WHERE "ID" = '<report id>';
ART-172
  • .

Info
  • Please note this is a workaround on a special situation, all measures should be taken to avoid direct changes to the database.

  • Currently we also have an improvement request for this purpose

:
Jira Legacy
serverSystem JIRA
serverId8382ec9d-abb6-3a29-8d72-95b9a5732a63
key