Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Workflow Conditions

Hi, I want to set conditions on my workflow, such as an issue must have an estimate before being pulled into "In Progress" or an issue must have time logged before being pulled into "accepted" (the final step in my workflow.  My question is if i set these conditions what will happen to tickets that dont fit these conditions that are already in these statuses?  I dont see a way to bulk add estimates or log time to issues and I dont want to activate the condition and have my stories all move to other statuses.  Has anyone ran into this issue before?

2 answers

1 vote

No, is the short answer.

Conditions are evaluated when someone is looking at an issue and looking for transitions.  If you add a new one, then yes, it'll kick in and stop stuff straight away, but it has no historical impact. 

So the good and bad news is adding a condition does not cause any existing data to change - good because no transitions or unexpected updates, but also bad, because nothing is going to go back over those old issues and undo "we let you make a change"

You'll need to do things like

"search a project for issues where my field is not set, and use (bulk) edit to update them"

0 votes
John Funk Community Leader Jan 19, 2021

Hi Brett - let me see if I understand the need. You would need to implement a condition on the transition from one status to another - say from status A to status B. In other words, do not allow the the card to move to status B if it is missing those things. 

You can implement that now with no problems. 

But your question seems to be, what about the cards already in status B?  Correct?

One way would be to add the same condition moving from status B to status C. But the issue might be that you need the information NOW while it is in status B. Correct? 

So you need to get the estimates in there along with time. And it won't let you bulk load that. 

One option might be to create an email in Automation For Jira that sends an email to the assignee for each card in Status B that is missing the information and ask them to populate those fields. You could have it send everyday until it gets updated. 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Trello

📹 Favorite Trello templates

Hello Community!  My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. In this video, I'll share my favorite Trello templates. Templates mentioned in ...

73 views 4 5
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