Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

'Hold' status in the workflow as outgoing from all transitions and returning tho the same trnstion

Köstebek Teknoloji Destek
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 22, 2022

How can I create the 'Hold' status in the workflow as outgoing from all transitions and returning the same status from 'Hold'?

2 answers

1 vote
Scott Theus
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 22, 2022

To verify...are you asking about how to have an issue that is currently on hold to transition back to the status it was before being put on hold?

So for example

  • The workflows has statuses for open, refinement, development, testing, closed, and hold. 
  • All statuses transition to "hold." (Except closed, I'd imagine but that's not important for the example)
  • "Hold" also transitions back to all statuses.

In this scenario you can put an issue on hold from any status, and return it to any status once the hold clears. 

You are asking if there is a way to transition the issue back to the same status it was in before it was on hold; to go from "open" to "hold" then, when the hold clears, have the workflow know to transition back to "open" and not any other status. 

Is this correct?

 

If so then...

I do not know if any way to do this in the workflow. You would need to have some other information in the issue to indicate what status it was in before it was placed on hold so the user would know what status to return it to after the hold is gone. Typically this would be done in a comment on the issue. 

I've recently revised all our workflows to remove statuses for issues that are on hold, blocked, etc. because of the confusion it can cause when lifting the hold or clearing the block. Instead I've added a checkbox to the view for blocked or held issues, then used colors in the story cards on the boards to show those issues are blocked and set up other filters to find them easily. 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 22, 2022

I've found the problem with "hold" or "blocked" status is exactly what @Scott Theus says - people don't understand what it really means, and so you really need some form of explanation of why they've been put into that status.  (To be clear, it's not the status that is the problem, it's the "why did you do this").

It can be easy to explain it, but before you allow this sort of thing to happen, think about how your people might read it.

Evaldas August 22, 2024

A good sidenote of using Hold/Blocked with caution, however how would you eliminate that time spent from SLAs?

0 votes
Rilwan Ahmed
Community Champion
December 22, 2022

Hi @Köstebek Teknoloji Destek ,

Go to your Workflow, click Edit, select Diagram mode

Click on status "Hold" and select checkbox "Allow all statuses to transition to this one". Publish the workflow. This will allow you to change status of your ticket from any status to HOLD

image.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events