Versions Compared

Old Version 7

changes.mady.by.user Derya Özdemir

Saved on

compared with

New Version Current

changes.mady.by.user Derya Özdemir

Saved on

Key

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

...

...

...

...

Panel
panelIconIdatlassian-info
panelIcon:info:
panelIconText:info:
bgColor#F4F5F7

This page is about Assets & Inventory Plugin for Jira DC. Using Cloud? Click here.

This guide details how to capture browser traces for troubleshooting JavaScript-related issues in Jira. Traces are helpful for Appfire Support to diagnose issues.

Note

Important

...

:

Browser traces are utilized by Appfire Support only for troubleshooting purposes. Be cautious about sharing these traces, as they may include sensitive information about your environment.

...

On this page:

Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printabletrue

Google Chrome and Microsoft Edge (Chromium)

Both Google Chrome and Microsoft Edge (Chromium) are based on the Chromium open source project. The following steps show how to use the developer tools, which are very similar in these browsers. 

  1. Log in to Jira.

Note

Log in before you start the trace so that the trace doesn't capture sensitive information related to your sign-in.

  1. Navigate to the step just prior to where the issue occurs.

  2. Press F12 or select Image Modified > More tools > Developer tools.

  3. By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro requires going to more than one page:

    1. Select the Network tab, then select Preserve log.

      Image Modified

    2. Select the Console tab, select Console settings, then select Preserve Log. Select Console settings again to close the settings pane.

      Image Modified

  4. Select the Network tab, then select Stop recording network log and Clear.

    Image Modified

  5. Select Record network log, then reproduce the issue in the portal.

    Image Modified

    You will see a session output similar to the following image:

    Image Modified

  6. After you have reproduced the unexpected portal behavior, select Stop recording network log, then select Export HAR and save the file.

    Image Modified

  7. Back in the browser developer tools pane, select the Console tab. Right-click one of the messages, then select Save as..., and save the console output to a text file.

    Image Modified

  8. Package the HAR file, and console output in a compressed format like .zip, and share that with Appfire Support.

...

Microsoft Edge (EdgeHTML)

The following steps show how to use the developer tools in Microsoft Edge (EdgeHTML). For more information, see Microsoft Edge (EdgeHTML) Developer Tools.

  1. Log in to Jira.

Note

Log in before you start the trace so that the trace doesn't capture sensitive information related to your sign-in.

  1. In the portal, navigate to the step just prior to where the issue occurs.

  2. Press F12 or select Image Modified > More tools > Developer tools.

  3. By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro requires going to more than one page:

    1. Select the Network tab, then clear the option Clear entries on navigate.

      Image Modified

    2. Select the Console tab, then select Preserve Log.

      Image Modified

  4. Select the Network tab, then select Stop profiling session and Clear session.

    Image Modified

  5. Select Start profiling session, then reproduce the issue in the portal.

    Image Modified

    You will see a session output similar to the following image.

    Image Modified

  6. After you have reproduced the unexpected portal behavior, select Stop profiling session, then select Export as HAR and save the file.

    Image Modified

  7. Back in the browser developer tools pane, select the Console tab, and expand the window. Place your cursor at the start of the console output then drag and select the entire contents of the output. Right-click, then select Copy, and save the console output to a text file.

    Image Modified

  8. Package the HAR file, and console output in a compressed format like .zip, and share that with Appfire Support.

...

Apple Safari

The following steps show how to use the developer tools in Apple Safari. For more information, see Safari Developer Tools overview.

  1. Enable the developer tools in Apple Safari:

    1. Select Safari, then select Preferences.

      Image Modified

    2. Select the Advanced tab, then select Show Develop menu in menu bar.

      Image Modified

  2. Log in to Jira.

Note

Log in before you start the trace so that the trace doesn't capture sensitive information related to your sign-in.

  1. In the portal, navigate to the step just prior to where the issue occurs.

  2. Select Develop, then select Show Web Inspector.

    Image Modified

  3. By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro requires going to more than one page:

    1. Select the Network tab, then select Preserve Log.

      Image Modified

    2. Select the Console tab, then select Preserve Log.

      Image Modified

  4. Select the Network tab, then select Clear Network Items.

    Image Modified

  5. Reproduce the issue in the portal. You will see a session output similar to the following image.

    Image Modified

  6. After you have reproduced the unexpected portal behavior, select Export and save the file.

    Image Modified

  7. Back in the browser developer tools pane, select the Console tab, and expand the window. Place your cursor at the start of the console output then drag and select the entire contents of the output. Use Command-C to copy the output and save it to a text file.

    Image Modified

  8. Package the HAR file, and console output in a compressed format like .zip, and share that with Appfire Support.

...

Firefox

The following steps show how to use the developer tools in Firefox. For more information, see Firefox Developer Tools.

  1. Log in to Jira.

Note

Log in before you start the trace so that the trace doesn't capture sensitive information related to your sign-in.

  1. In the portal, navigate to the step just prior to where the issue occurs.

  2. Press F12 or select Image Modified > Web Developer > Toggle Tools.

  3. By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro requires going to more than one page:

    1. Select the Network tab, then select Persist Logs.

      Image Modified

    2. Select the Console tab, select Console settings, then select Persist Logs.

      Image Modified

  4. Select the Network tab, then select Clear.

    Image Modified

  5. Reproduce the issue in the portal. You will see session output similar to the following image.

    Image Modified

  6. After you have reproduced the unexpected portal behavior, select Save All As HAR.

    Image Modified

  7. Stop Steps Recorder on Windows or the screen recording on Mac, and save the recording.

  8. Back in the browser developer tools pane, select the Console tab. Right-click one of the messages, then select Export Visible Messages To, and save the console output to a text file.

    Image Modified

  9. Package the HAR file, and console output in a compressed format like .zip, and share that with Appfire Support.