Hi all,
We have tasks which are automatically created when a new line is added in Excel (using Zapier). One of the fields input into Excel is Record ID and usually looks something like A01723, and this number is pulled into the Jira task summary as well as a separate custom field. We also have auto-allocation rules in place to assign these tasks to users in a role upon creation.
Sometimes if there's multiple Excel records for the same customer, the Record ID will be A01723/001, A01723/002 etc. We would like to make it so these tasks are assigned to the same user, which would be based off the first 6 characters of the Record ID.
Any automation help at all would be massively appreciated!
Hey Callum,
I think we can mock up a rule for you, but first I want to confirm this is essentially what you need:
For a preview, we can use the length() function to see if the custom field is longer than 6 digits (to see if it's multipart) or use the match() function to check for the slash. The substringBefore() function could get just the digits before the / separator for comparison.
Let me know if this is about on the track of what you need, and we can mock it out into full rules!
Cheers,
Daniel
Hi @Daniel Eads, thanks for your reply - you're spot on with your description, this sounds exactly what we're looking for :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Daniel Eads, are the any updates on the above? Really keen to see how this rule will work :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your patience, I was out a few days! For the purposes of this example, I am assuming your custom field for the record is called recordID. Given this is a fairly long/complicated rule to set up, you can download the rule here and then just import this rule into your own instance (rule import/export instructions here).
The first part isn't so tricky:
And there you have it! Again, given the rule complexity, I do advise downloading the JSON from here , importing it, and then updating steps 4 and 6 with your custom field name, then modifying step 11 for your normal assignment rules.
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.