I'm looking to create automation that works when the Stage (it is a custom field) value changes. When that value changes, the Status field will be updated appropriately. So for example, if Stage is updated to Configured then the Status will transition to configured....OR if the Stage is updated to Assembling then the status will transition to assembling. There are several other values....I'd prefer not to create a separate automation for each. Does that make sense?
Hi @Chuck Rohllf -- Welcome to the Atlassian Community!
What have you tried so far, and can you post an image of your rule? That will help the community provide input.
It sounds like what you are trying to do is:
Please note the nesting to ensure your actions are paired with their condition tests.
Best regards,
Bill
Thanks for the fast response! Here is a snapshot of part of the rule.....I'm not seeing the Else/If option - which is probably my issue:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
You can find the If/Else looking under New Condition:
Next thing, you may not need that branch For Current Issue. That helps when you have a more complicated structure and/or need to iterate over a set of things. For example, starting with the parent of an issue.
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.