Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,297,670
Community Members
 
Community Events
165
Community Groups

Two way workflow Transition For "ON HOLD" Status

Hello everyone,

am stuck with workflow transition 

i have two steps status in the workflow which i have added Transition to "ON hold" status

But the problem is 

when i move the transition from "Step 1" to "On hold" , then after it shows the Transition of "step 1" and also the "step 2" 

which i don't want to be Happen

Kindly provide any solution 

when i move from step 1 to on hold and again from on hold to step 1, the other step 2 should not be visible.

 

Work.PNGCapture1.PNG 

 

3 answers

1 accepted

0 votes
Answer accepted
Robert Wen Community Leader Jun 08, 2022

The only way I see out of this is having 2 "On-hold" statuses, one for each Step.

Hi @Robert Wen 

Thanks for your quick Response

we can make 2 "On-hold" statuses but what if i want to show that status in the Board

then i have to make to make to columns for both Status

and also need to make 2 different Statuses in the workflow with same name 

even also we would face issues in importing data of "Status"

is there any better solution for this problem ?

Robert Wen Community Leader Jun 08, 2022

Actually, you could map both "On-Hold" statuses onto a single column.

But 2 "On-Hold" statuses with same spelling it won't accept ?

Robert Wen Community Leader Jun 09, 2022

So when I say 2 "on-hold" statuses, I don't mean they have the same name.  It would probably look something like this.

Screen Shot 2022-06-09 at 6.22.41 AM.png

 

On a board, you can have the two on-hold statuses (Step 1 Hold, Step 2 Hold) mapped to a single board column.

Screen Shot 2022-06-09 at 6.27.28 AM.png

I think this is the simplest solution to what you want.

Like # people like this

Thank you soo much @Robert Wen 

Like Robert Wen likes this
0 votes

On Server, there are a couple of apps that provide a "previous status was" condition.  Cloud doesn't support that yet, but you can get close with off-the-shelf functions.

You need a custom field, and  four transitions:

Add a field called something obvious like previous-status.

  • Step 1 -> on hold
    • With a post-function that sets previous-status to Step-1
  • Step 2 -> on hold
    • With a post-function that sets previous-status to Step-2
  • On hold -> step 1
    • With a Condition that says "only allow this if previous-status is Step-1
    • With a post-function that clears previous-status
  • On hold -> step 2
    • With a Condition that says "only allow this if previous-status is Step-2
    • With a post-function that clears previous-status

You could use a (hidden) custom field to mark the origin status and check this field value in the transition condition.

Hello @karel_mellen 

Could you please explain how to do it

Because it not a custom field

You need to *create* and extra custom field in which you store the previous status. You can use this field's value to build conditions on. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,770 views 37 47
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you