Lock/Freeze an issue

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,

3 answers

1 accepted

1 vote

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

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.

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).

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

Related:

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

Very interesting and elegant solution !

Would your approach also lock the associated sub-tasks ?

I'm eagerly awaiting this plugin.

Thanks !

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)

Done, check the above

Radu, can you please update the answer, the URL is broken and even by browing your website I wasn't able to find as solution for this problem: Freeze / Unfreeze. I need a solution that would not mess all my workflows.While Freeze is easy to implement as an Global transition (or common if you want it to make if available for Close state or others), I need a defroze solution :D

0 vote
Renjith Pillai Community Champion Apr 04, 2013
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

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,203 views 13 19
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot