Links Explorer plugin "issue-popup" CSS class issue

[Nikolai Derzhak]

We have got issue with "issue-popup" div CSS is not displaying on click on "eye"-icon in tree.

Example:

Open https://jira.appcelerator.org/browse/TC-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel

Click Links Explorer tab – click on eye-icon.

You will get raw html div code like this:

"

<div class="issue-popup"> <strong><a href="/browse/TC-90" title="TC-90">TC-90</a></strong> <div>takeScreenShot showCamera view capturing black background</div> <dl> <dt>Affect Versions</dt> <dd> <span class="versions-container">None</span> </dd> <dt>Fix Versions</dt> <dd> <span class="versions-container">None</span> </dd> <dt>Assignee</dt> <dd> <span>Tony Guntharp</span> </dd> <dt>Reporter</dt> <dd> <span>Trevor Ward</span> </dd> </dl> </div>

"

It works only when I load link explorer tab directly: https://jira.appcelerator.org/browse/TC-90?page=com.otpl.jira.plugins.lxp:link-issue-tab-panel

Jira version is: Atlassian JIRA (v5.1#768-sha1:38ad524)

Looks like CSS namespace (?) issue. Or probably plugins conflict.

I have tried to put issue-tab related CSS in Announce banner with no luck.

I am ready to test this on staging. But give directions to try , please.

[Deepak J]

Hi Nikolai,

I have tried to reproduce issue, but was not able to do so, with

• Atlassian JIRA (v5.1.7#786-sha1:c37bed1)

But I have discovered that, issue is not releated to CSS or JS, but it is due to velocity templates.

I have found that, somehow JIRA is encoding, content inside AUI templates writeen inside velocity templates, which is not a desired behaviour, from velocity.

I wil file issue with Atlassian, and will see what they have to say about it.

Meanwhile I suggest you to update to 5.1.8 or later version of JIRA. Please, let me know if issue exists with other version too.

[Deepak J]

https://answers.atlassian.com/questions/137836/velocity-templates-encoding-content-inside-aui-templates

You can view response from Atlassian here.

[Nikolai Derzhak]

I have played with upgraded jira (5.2) and plugins on staging host and found plugins conflict.

The issue went away when I disabled Field Security Plugin.