Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

JIRA 6.1-m02 Top Navigation Bar disappears when custom js is imported

Akira Tsuchiya
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 23, 2013

The Top Navigation Bar disappears in JIRA 6.1-m02 when the steps below are applied.
This problem does not happen in JIRA 6.0.x.

Step 1. The we resource below is defined in the atlassian-plugin.xml.

<web-resource key="issue-resources" name="Issue Resources">
<resource type="download" name="customMade.js" location="/js/customMade.js"/>
</web-resource>

Step 2. The line below is described in the target vm file.

$webResourceManager.requireResource("[atlassian plugin key]:issue-resources")

Step 3. The vm file is loaded in a browser.


I want to know the workaround.

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Akira Tsuchiya
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 27, 2013

I do not fully understand UI-related issues in JIRA 6.x.

I found that <param name="ieonly" value="false"/> is necessary in JIRA 6.0.x.

And I am now confused about it in JIRA 6.1.

Refer to the new question below.

https://answers.atlassian.com/questions/217053/how-to-create-a-javascript-web-resource-in-jira-6-1

0 votes
Akira Tsuchiya
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2013

In atlassian-plugin.xml, describe the we-resource like below.

<web-resource key="some-resources" name="Some Resources">
<resource type="download" name="some.js" location="/js/some.js">
<param name="ieonly" value="false"/>
</resource>
</web-resource>

Point 1.

If the some.js uses jquery.js, do NOT import jquery.js like below.

<resource type="download" name="jquery.js" location="/js/jquery.js"/>

It is because JIRA 6.x uses jquery.js by default.

Point 2.

Set the <param> attribute in your custom js as below.

<param name="ieonly" value="false"/>

This is for workarounding browser-specific bugs and the setting is effective from IE, Firefox, Chrome through Safari.

Holger Schimanski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 24, 2013

You mean in Point 2, that you *have to include* the ieonly param in the atlassian-plugin.xml even if it is set to false? Sounds strange. Did you try to remove the param?

0 votes
Akira Tsuchiya
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2013

This depends on browser type.

It is OK with Chrome.

But the problem happens with IE, Firefox, and Safari.

I think it is related to Compatibility View.

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events