The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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 ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, you could map both "On-Hold" statuses onto a single column.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So when I say 2 "on-hold" statuses, I don't mean they have the same name. It would probably look something like this.
On a board, you can have the two on-hold statuses (Step 1 Hold, Step 2 Hold) mapped to a single board column.
I think this is the simplest solution to what you want.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could use a (hidden) custom field to mark the origin status and check this field value in the transition condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
👋 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...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.