super stuck on an automation

[ezra bibby]

im trying to turn on an automation, where;
- summary includes the exact phrase "Invoicing 2.0 ran successfully on CSL", and
- reporter = BeelineDBATeam@beeline.com

in that scenario, i need to;
- remove all participants
- add the label "CSL"
- Assign to user Ezra Bibby
_ resolve the ticket

ive been trying for a few hours, cant get it right

[Valerie Knapp · Accepted solution]

Hi @ezra bibby , thanks for your post.

Stealing this from the great @Marc - Devoteam 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of the actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. images showing the relevant data in an image that is part of the rule execution.

6. Explain where the issue is.

These questions are not for not willing to help, but to have community members learn on how automation works.

Not just to provide a full solution, which would not help to understand what the automation is doing, but to have members understand what a rule is doing, if in need of change or error.

Please can you share some more information, including screens, audit logs? It will be difficult for us to help you troubleshoot without some more detail.

Thanks

[ezra bibby]

thx Valerie :-)

1. what type of project is this (e.g., company-managed, team-managed, etc.), 
   1. it's a company managed project
2. images that show your complete rule.
   1. 
3. images showing the details of the actions/conditions/branches.
   1. 
4.  images showing the Audit Log details for the rule execution.
   1. nothing to show here, audit log is just showing the edits the rule, each time it fails validation.  no detail on the "why"
5.  images showing the relevant data in an image that is part of the rule execution.
   1. 
6. Explain where the issue is.
   1. im not sure, but i get this
      

hope you can help!! :-)

[Valerie Knapp]

Hmm @Trudy Claspill or @Bill Sheboy , do you have any ideas here?

[Bill Sheboy]

Hi @ezra bibby and @Valerie Knapp 

Your rule uses Lookup Issues to gather the issues, tries to branch over the issue data, and then tries to modify the issues.  That is what the error is indicating (even though it is poorly worded): the Edit Issue action needs an issue and one is not provided.

Lookup Issues is used to gather issues, such as to sum a value from a field or report on them.  It cannot access them for edits.

For the scenario you describe, your rule could instead use the JQL from the action with the Scheduled trigger, and remove the branch completely.

For example:

• trigger: scheduled, with JQL to gather the issues
• ...actions to update the issues

And from what you show, several of the update / edit actions should be merged to update most of the fields at one time; this will improve rule performance and prevent problems.

Kind regards,
Bill

[Valerie Knapp]

Cheers @Bill Sheboy !

[ezra bibby]

thankyou @Bill Sheboy !

i really got tangled on that one lol... works now, and is so much neater!

ive had it set at 2 mins for testing, but will revert to the right trigger now, thx again!!

[Bill Sheboy]

Awesome; I am glad to learn the community was able to help!