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.
Community moderators have prevented the ability to post new answers.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.