Hello,
As in the picture;
In some projects, when "reporter" is sentryintegration@gozendigital.com, I want "assignee" to be the person I want.
When the reporter is "sentry" after the ticket is received, "assignee" will be metin.sunbul in the example GSS-Gohub project.
How can we automate?
Hi @Barış Özer,
A setup like this should do the trick:
The condition (the second step in the rule) is a Field Value condition on reporter. In steps 2 and 3, just replace the reporter and assignee with the values you need.
Hope this helps!
Many thanks for the quick reply.
I want to run this rule only in 2-3 projects that I want.
How can I add the projects I want?
It doesn't need to work on all projects.
For example; I made a watcher rule and added the projects I wanted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since you seem to be on a standard plan, the best way to do this may be to add the rule in each project separately. Yes, that means you have to configure it 3 times, but you have a limited number of rule executions in a standard cloud plan. Rules inside a single project are not counted towards that limit are not counted against that limit, so they are free in a sense.
You configure project specific rules in a project by going to project settings > automation.
As an alternative, you can create a global automation rule and in Rule details select the projects it applies to. You need to set scope to Multiple projects and in the field below select the projects you need.
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.
I don't understand what it means?
If I mark and save will the rule work and replace "assignee"?
I don't understand do I have to mark it?
"Allow rule trigger
Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You only need to check this option if you want to let your automation rule be activated by another automation rule. From what your describe, I cannot see why you should need to check this.
Your automation will run every time an issue is created in your project (that is what the Issue Created trigger (the first step in the screenshot) takes care of. There is nothing else you need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then I don't mark it.
I thought like this;
There is something like (run rule now) after Outlook rule. I thought it was something like that.
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.