Say I have a .csv with information:
I have "System Serial #", "Site", and "System Type" as dropdown fields in my "Issue/Bug" issue type in my team-managed project. The available options in those dropdown fields span the options listed in the .csv.
I want to automate the updating of "Site" and "System Type" by entering the "System Serial #" during issue creation using information I have in a .csv similar to the above picture. I would rather not make a new branch rule per "System Serial #" and update information accordingly.
Let me know if I need to make clarifications.
Hi @Makai Baker
Rather than use the branching/conditions, you could try using the new Lookup Table feature of rules. This would work as long as you have 20 items/rows or less.
Please look here to learn more and see examples of that rule action: https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333
Kind regards,
Bill
Hello @Makai Baker
If I understand correctly, I believe you could use an Automation Rule to update the Site and System Type fields after the fact by including two Lookup Table actions. In the Automation you can use the value entered in the Serial # field to lookup the corresponding values for Site and System Type in the tables, and assign those values to the corresponding fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, I basically did exactly what was done in the "Example use case" section
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.