---
title: "Hold an issue, proceed when clear"
canonical: "https://support.appfire.com/space/JMWEC/466322207/Hold%20an%20issue%2C%20proceed%20when%20clear"
format: markdown
---
> Macro (aura-html)

| **Goal** | Place an issue on hold, and return it to its original status when ready |
| --- | --- |
| **Scenario** | You need to place issues in a holding status ('Blocked', for example) when work can not proceed. Additionally, when work is ready to restart you need to guarantee that the issue returns to its original status before being placed on hold. |
| **Components** | [Set issue fields](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465504849) post function, [Build-your-own (scripted)](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465474365) condition |
| **Baseline** | - Your workflow must include a status specifically for holding issues outside the normal flow of work.
- A custom field exists or is created to store the return transition for the issue (e.g. **Return to In Progress**). |

---

> 📝 In this example, the workflow is configured so that: 
> 📝 
> 📝 - Only statuses that are in the **In Progress** category (blue status nodes in Figure 1, below) have transitions to a status labeled **Blocked** - the “on hold” status.
> 📝 - All incoming transitions to **Blocked** use the same transition - a transition called **Blocked**.
> 📝 - Outgoing transitions from **Blocked** use the formula “Return To” and the name of the original status (e.g. “Return to In Progress”)
> 📝 
> 📝 In your Jira instance, the status values may be labeled differently, or you may have additional statuses that need to be connected to the “on hold” status. You may have multiple “on hold” status values (such as both **Blocked** and **Waiting for Clarification**). If you have different values, just substitute your status values in the steps below. If you need more than one “on hold” status, just repeat the steps below for each holding status.