Common issues with Assets caused by user-installed apps
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
There are some visual bugs or glitches on an issue/request/Assets object view
Environment
Any Jira Software version since 8.x or Jira Service Management since 4.x with Assets installed and in-use
Diagnosis
Here's a list of the known symptoms.
- Jira issue view has a different layout where the Activities section that is usually on the left bottom of the page appearing on the right side of the page. This behavior is only observed on Jira issues that contain at least one Assets custom field with value.
- In an Assets object, users couldn't navigate through tabs like Connected tickets, Comments, History as there's no response from clicking on these tabs. It might take many mouse clicking to be able to load a different tab.
When viewing a Jira issue, the selected object on the Assets custom field doesn't show all the expected attributes per the custom field configuration. If user edits this issue, user will find that the Assets custom field does not have the drop-down available, only the magnifying glass icon and maybe the plus icon on the right side. In the space where the drop-down usually is, the description of the custom field is seen (if exists).
- Consider a Service Management request with one Assets custom field and another one referencing this custom field. On request creation, user filled in both Assets custom fields and afterwards, removed the object on the first custom field. When the user wants to select an object again on the first custom field, the dropdown becomes distorted and it's not possible to find and select a new object. User has to refresh the page or create the request in a new page.
Cause
The exact cause is not known, it also varies from app to app. In general, these odd behaviors are caused by some user-installed apps.
Some known user-installed apps used to cause symptoms described above are
Solution
- Verify if the issue persists in Jira safe mode. Downtime might be required as all user-installed apps will be disabled in safe mode, which could impact users and business.
- If the issue is not reproducible in safe mode, we can confirm that one of the user-installed apps is causing the issue.
- Disable one user-installed app at a time and test if the issue is reproducible.
- If the issue is not reproducible when a specific app is disabled, identify the vendor and contact the vendor for support. This information can be obtained from Atlassian Marketplace.