A rule that is created based on the reports of different reporters

[Meates Underwoodson]

Hi there,
An issue should be automatically assigned to a specific participant when a certain group of reporters (customers) raises it.
Is it possible to do that?
As of now, I can only set up a rule that adds a specific participant to every issue.
Project Settings>Automation>Create Rule>When: Issue Created (and then save)............Next component>Then: New Action>Edit Issue, select - Request Participant and then select the name.
Thanks

[Stephen Wright _Elabor8_]

Hi @Meates Underwoodson 

Can I confirm the logic is...

• If a specific set of Customers (Reporters) raises and Issue
• Then add a specific Request Participant
• ...and repeat, for multiple scenarios

...is this correct?

---

If yes, I'd recommend using the If/Else Block condition within your rule to allow for multiple different outcomes.

The rule would look something like this:

• Trigger: Issue Created
  • Condition: If/Else Block
    • IF...
      
      • Sub-Condition: Issue Fields Condition
        • Field = Reporter
        • Condition = is
        • Value = <Users Here>
      • Sub-Action: Edit Issue
        
        • Field = Request Participant
          • Value = <User Here>
    • ELSE-IF...
      
      • Sub-Condition: Issue Fields Condition
        • Field = Reporter
        • Condition = is
        • Value = <Users Here>
      • Sub-Action: Edit Issue
        
        • Field = Request Participant
          • Value = <User Here>
    • ...etc

---

A few notes on this rule:

• If Participant is actually "Assignee", you could replace the Field used in the Actions
• You can have multiple "ELSE-IF" sub-rules - just click "Add else" in the left-hand column showing the rule, and add at least one Condition to turn it into an "ELSE-IF" condition
• These rules usually run on the assumption that each IF/ELSE-IF statement is unique - i.e the Reporters/Customers are not the same on any other statement. If they can be, and your results are not optimum, you could use Branch instead for this scenario. It would look something like this for each section of the rule:
  • Branch: Related Issues
    
    • Type = Current Issue
      • Branch-Condition: Issue Fields Condition
        • Field = Reporter
        • Condition = is
        • Value = <Users Here>
      • Branch-Action: Edit Issue
        
        • Field = Request Participant
          • Value = <User Here>
  • ...etc

---

Let us know if this helps!

Ste

[Wong]

You might consider using an If/Else condition for this:

If reporter A

   Participant A

Else reporter B

  Participant B

Etc.