There is an function in
This functionality is a little different to what you are expecting.
Here's a brief example of how this works.
Rule 1, triggered when a ticket is created.
Rule 2, triggered when the Assignee is updated.
Rule 1 is triggered and updates the Assignee to the Project Lead.
Rule 2 is checked to allow triggers from another rule, therefore Rule 1 updating the Assignee will trigger Rule 2.
Without this checked, Rule 2 will only trigger from a user manually updating the Assignee.
This can be used cleverly to enforce checks on users (such as if a field is made empty), whereas Automation wouldn't trigger the same check, allowing the Automation to proceed as you require, whilst still blocking users doing things you don't want them to.
Thank you Sam. It's very hard to understand like this.
When can Jira provide the way like I expected?
Rule 1 contains some common actions.
Rule 2 can trigger Rule1 like calling a shared function. It will save lots of effort to add repeating actions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@flourish_x_yang it's something we would love to have implemented too, but there's no 'clean' way to trigger Rule 2 based on an action in Rule 1.
If that existed, then this would be a much more powerful tool, but it's just not there!
Without, we have the same, we have multiple rules sometimes doing very similar things because the trigger points are different!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks anyway for telling me this.
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.