nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lock/Freeze an issue

Saint Germain

Hello,

During the workflow of an issue, we may need to freeze the workflow temporarily (for instance because the issue can be cancelled but we are not sure yet).

A big displayed warning which warn the user not to process the issue or related sub-tasks would be perfect but I don't think that is possible ?

I have currently not found any other solution than creating an additional status/step "Frozen" which can be reached from any status/steps and which can go back to any status/steps: very complicated.

Does anyone have a more elegant solution ?

Thanks very much in advance,

Accepted answers

Jobin Kuruvilla [Adaptavist]

Workflow is indeed the best solution. See if you can use common or global transitions for lesser complexity.

https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-common_transitions

All comments

Jobin Kuruvilla [Adaptavist]

Workflow is indeed the best solution. See if you can use common or global transitions for lesser complexity.

https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-common_transitions

Saint Germain

Thanks, the complexity is in defining how to put a constraint to return only to the departing status/step before freezing (of course we can manually check the transition history).

I don't think that this is possible currently.

Saint Germain

Oh I found that this is in fact possible. You can create transition with a condition on the previous immediate status.

So the solution is to create a global transition to a "Frozen" status and to manually create transitions from this status to every other status (with each one of the transitions having a condition on the previous status).

Radu Dumitriu

Not anymore. We'll release a plugin soon which helps you eliminating (in certain conditions) the need for transitions.

Here's the example http://confluence.kepler-rominfo.com/display/TR/Locking+Issues . Stay tuned .

Edit: updated the URL, as requested below

Also, Locking issues via Live Fields: http://confluence.kepler-rominfo.com/display/TR/Lock+an+issue+-+a+better+variant+%28Live+Fields%29

http://confluence.kepler-rominfo.com/display/TR/Making+an+issue+read-only

Saint Germain

Very interesting and elegant solution !

Would your approach also lock the associated sub-tasks ?

I'm eagerly awaiting this plugin.

Thanks !

Radu Dumitriu

Hi. We thought so, too.

It's scripted, so yes, subtasks can be locked too.

Delivery is in about 3 we from now (around 31Aug +- 1w)

Radu Dumitriu

Done, check the above

Renjith Pillai

Also usage of workflow properties will help you restrict who can change anything in the issues that reaches the frozen state. Read Jobin's blog http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html