I am able to tune the number of Workflow buttons via ops.bar.group.size.opsbar-transitions in $JIRA_HOME/jira-config.properties. One problem is that a ghosted "Workflow" dropdown button will appear if the number of transitions available is one less than this value.
But, although my Project is not configured for Greenhopper, I have these silly "Agile Board" and "Rank to Top" buttons which I will never use, prominently placed on my UI. I'd like to get these out of the way. I can not figure a way to configure the button list, but I did try setting ops.bar.group.size.opsbar-operations but I do not observe any change in the number of Operations buttons displayed.
The above screenshot is with jira-config.properties configured like so:
ops.bar.group.size.opsbar-operations = 2
ops.bar.group.size.opsbar-transitions = 4
One problem is that a ghosted "Workflow" dropdown button will appear if the number of transitions available is one less than this value.
This is being tracked by Atlassian here: https://jira.atlassian.com/browse/JRA-24608
Regarding the setting of the ops.bar.group.size.opsbar-operations property, it worked correctly for me, so it is possible there is sonme problem with the file you've created, so to use it please:
Also, if you wish to change the order of the buttons displayed, see this page (search for "Customising the Positions of Items and Sections"). For example, to make the Log Work button appear before the Agile Board, Rank Bottom, etc. buttons, I did the following:
<web-section key="operations-work" name="Ops Bar Operations Work Section" location="opsbar-operations" i18n-name-key="webfragments.view.issue.opsbar.operations.work" weight="11"/>
This attribute I modified is the "rank" attribute of the button. That is, every button/web-section has a 'weight' value and the lower values appear before the higher in the menu. So what I did is I lowered the value of the 'operations-work' web-section so it would appear before GreenHopper.
I hope this helps!
Thank you sooooooo much for this! Your properties file is a broken link now but it wasn't needed after viewing the very detailed https://developer.atlassian.com/display/JIRADEV/View+Issue+Page+Locations#ViewIssuePageLocations-IssueOperationsBarLocations page that you linked. After rearranging the weight of the opsbar operations-operations to 10 (to be first) then I set the number of buttons displayed to be 4 to cover them all with jira-config.properties: ops.bar.group.size.opsbar-operations=4
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs