Help with changing ops.bar.group.size.opsbar-transitions

[Nicklas Kittelmann]

Hello!

I'm trying to find out if it is possible to change the ops.bar.group.size.opsbar-transitions in a hosted jira instance (OnDemand), or if we need help from you to do it, please advice. I can't find the setting in the administration part of Jira, but perhaps I've missed some place...

We'd like to have it set to 3 instead of the current 2, as per the page http://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-workflowtransitionbuttons

Regards

Nicklas Kittelmann

[Nick Mason · Accepted solution]

To get this changed in OnDemand, you'll need to raise a support request and we'll be able to change this option for you.

[Martin Butt]

@Eric Franklin, is there anyway of changing this for OnDemand customers? Or any plans to make this a configuration variable?

[Eric Franklin]

Hi all,

Please note that this is no longer a property that can be changed in JIRA Cloud, and that includes being changed via Atlassian Support.

[Dieter]

The procedure Radek describes looks ok but you cannot change files in the JIRA Home Directory since your are on an OnDemand instance. Only Atlassian support could do that but i'm note sure if they will. Please contact Atlassian support

[Nicklas Kittelmann]

Well, I'm not sure how to shutdown Jira, nor do I understand how to edit files in some directory...

It would have been easy if we had the instance running at one of our machines, but not when it's hosted by atlassias as part of the OnDemand.

[Radek Kantor]

This does not work?

1. Shutdown JIRA.
2. Edit the jira-config.properties file in your JIRA Home Directory.
   See Making changes to the jira-config.properties file for more information.
3. Change the value of 'X' in the ops.bar.group.size.opsbar-transitions = X property of this file to the number of transition buttons required before the Workflow button.
   If this property does not exist in your jira-config.properties file, add it. Otherwise, a default value of 2 is assumed.
4. Save the updated jira-config.properties file.
5. Restart JIRA.