Is it possible to freeze the Description bar?

[Grazi]

Hi, everyone! First, apologies if I'm not using the proper terms. :)

For that reason I also apologize if this is a common question! Since I did not know which terms I should use to search on the forums, I couldn't find anything closer to what I'm asking.

So, I'd like to know if its possible to freeze this Description bar when scrolling/typing an issue:

Sometimes my issue's text description gets too long and it's a bit of a hassle to keep going back up to change or add something. It'd really help if the bar could also accompany you while you type all the way down!

Thanks in advance for your time!

[Sameera Shaakunthala [inactive]]

You can use a global transition for 'Reopen'.

https://confluence.atlassian.com/display/JIRA/Advanced+Workflow+Configuration#Advancedworkflowconfiguration-common_transitionsWorkingwithcommonandglobaltransitions

Or else, I can suggest you these two steps.

1. If you have multiple 'Reopen' transitions in any single workflow, create a common action (re-usable transition) instead of all.
2. Manually edit all workflows' XML and set the transition ID of 'Reopen' to the same number. Eg. 500

[Greg Sommerville]

Thanks for the quick response.

A global transition is "global" only for a single workflow, right? It's not like I can set up one and it works across all of the workflows, correct? So it sounds like I'd need to set up one global transition per workflow.

On the other hand, if I can just go in and edit all of the workflow XML and assign my own ID to Reopen, that should solve it. Are there any potential problems with me doing that? That ID was assigned by JIRA, so I'm a little hesitant about going in there and just changing it however I feel...

[Sameera Shaakunthala [inactive]]

Oops... sorry. My understanding of global transitions was wrong.

Please take whatever I've written below 'Or else...' as the answer. :)

I just went through a workflow XML where a common action is used. It shouldn't be a problem to change the action ID, but you have to change it everywhere.

Here's how common action should begin,

<common-actions>
    <action id="500" name="Reopen" view="fieldscreen">

And here's how it should be reused.

<common-action id="500" />

What you shouldn't mess with is step IDs.

[Greg Sommerville]

OK, so I can edit the numbers of my transitions, but stay away from the step IDs.

Is that true if I'm not dealing with common actions? Let's say I just go in and edit the transition IDs for normal actions (not common, not global). Will that be OK?

[Sameera Shaakunthala [inactive]]

Changing transition IDs should be OK. But don't overuse it. Do it only when required. If you have workflow-related plugins like Behaviours installed, changing some transition IDs may affect the plugin's functionality.

Regarding step IDs, each step ID represents a Status (global) in JIRA. Therefore I don't think it's a good idea to change step IDs. In your case you don't need to mess with them. :)

Be sure to take a backup of your workflow before performing any sort of modification to it.

--------

And don't be scared to modify workflow XML. :) :)