Hello everybody. I am asking for your help for this matter.
I need to automate the creation of subtasks on a project.
Process looks like this :
1) User chooses an option on a "Product" custom field.
2) Depending on the option, a certain number of substasks are created.
Example
Possible values for Product :
- Square
- Circle
If square is choosen, I need to create four subtasks named Tomorrow, Phone, Chair and W.
If circle is choosen, I need to create three subtasks named James, Jones and Martin.
Things would be simple if there was not about 100 hundred options for "Product". Each option can create between 2 and 5 subtasks whose name changes for each option.
My solution was to create a template project that is going to nest every possible subtask and to build an automation that would create some of the subtasks depending the option choosen for Product, but I have two issues :
1) Isn't there another, simpler option (cascading fields, etc...) ?
2) My client does not have Premium and I think I will have a hard time trying to convince them to upgrade.
Feel free to ask me for details.
Thanks in advance for your help.
Assuming your subtask content does not have a lot of variation for each Product's subtasks, this could be tried with an automation Lookup Table.
For example:
If there is a lot of variation between the subtasks, one could add additional data to the lookup table, perhaps storing it as JSON, and use the new jsonStringToObject() function to decode it.
Kind regards,
Bill
@Bill Sheboy I haven't used lookup tables like that before, but I'm guessing that since you can only have 20 rows in a lookup table @Flavien Gache would have to create several tables and maybe multiple automation rules for the 100+ options for Product
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The documentation is incorrect as Lookup Tables now support up to 200 rows, per this article from Atlassian on the latest round of updates in July 2023: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798
The action's UX is a bit tricky to use as it pages every 20 rows.
The other possible workaround is using an attachment:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply @Bill Sheboy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your help.
I don't think i will go the lookup table path because my file is composed of 200 products with up to 6 subtasksks to create each time (about 1200 options to feed the automation here).
However, I am interested in your API option as I did not know you could use the API to read an attachment. I am going to try it today, might need some more help, I will keep in touch :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am stuck at step 3 of your answer @Bill Sheboy . I don't know what to do with {{webhookResponse.body}}. What can I do with it ? You are precising it is possible to use match() but do you have a link to documentation please ? I can't find any.
Thanks in advance.
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.