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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,921
Community Members
 
Community Events
176
Community Groups

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

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

 

2 answers

0 votes

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

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

If reporter A

   Participant A

Else reporter B

  Participant B

Etc.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events