In 5.1 we started porting code from JSPs to web-panels. We completed this work during 5.2. Each block on the view-issue page is now a plugin. This gives us a lot more flexibility.
Under jira-components/jira-plugins lives a plugin - jira-view-issue-plugin.
In this plugin there are a number of web-panels defined. You can either update this plugin and upload your new version, or create a new web-panel and disable the old one you want to replace.
These panels are displayed in 2 columns (As specified by the location) and ordered by the weight.
Hope this helps.
JIRA Engineering Manager
I looked around and couldn't find any references to 'jira-components', however I took what I know about jira and looked in <jira_data_folder>/plugins/.bundled-plugins and I was able to find a "jira-view-issue-plugin-5.2.jar".
We will take a look into that and hopefully it's the same thing you were describing.
For JIRA 5.2.x to 6.2.7 you may follow the instructions on J-trick's tutorial: http://www.j-tricks.com/1/post/2012/05/modifying-atlassian-bundled-plugins.html From JIRA 6.3 onwards, the jira-view-issue-plugin JAR can be found on the JIRA_INSTALL/atlassian-jira/WEB-INF/atlassian-bundled-plugins folder.
Hi Nick, I have problem in reordering a third-part plugin (named structuremodule in the view issue screen) I can easily reorder all other components using the jira-view-issue-plugin, but the structure plugin must be probably modified from its own jar file. and changing all the weights found in its manifest file didn't help. Do you have any idea, how the third-party plugins are placed in the view issue page? I greatly appreciate any help. Thank you.
Hey Nick, sort of related to this. In JIRA 5.1.7 what would be your suggestion for the quickest way to ensure a wider 1st column in the id="issuedetails" ul.?
One of our client instances has some large customfield values and I think the right hand side (class="item item-right") is pushing the left side too small, cutting off the custom field names.
Correct - there is only one definition of each way to look at an issue.
You could write code that displays differently by project, but it'll be a bit of a mess - think about the issue navigator as an example. If a user runs a filter for two different projects that you've decided to display differently, then as they page through the results, the formats are going to change, which is disjointing and confusing.
In other words, stick with one layout for your system.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot