Automation : Lookup table with a label field

[Joseph HANI]

Hello everyone ! 

I hope you are doing great ! 

I'm quite lost here on the update of my automation...

To give you more insight, we were using field to plan our estimate Delivery of an Epic for the team to commit on this deadline. Based on the value of this field, it updated 2 other dates field : Build Start / Build End 

Everything was working great here was the automation using lookup table, added some log to be sure 

But here is my problem : 

- Recently, we have switched our process and use a new add-on that have created a label field that is populated automatically. 
And now we have to plan / commit the Delivery and the Test of our Epic. 
--> Which mean that I will create 2 automation to will populate 4 fields 

- Delivery : Build Start / Build End 
- Test : Test Start / Test End 

Both labels value will be now in this field : "Program baseline sprint" and looks like this : 

- DATADE : Delivery

- DATAAN : Test

And here is the trick ... 
I kind of don't understand how I can do the matching of this labels inside the lookup table ... I tried to used regex to match "AN" or "DE"

And then even more disturbing for me is the edilt field where I tried to do the matching ... 

Build Start :
{{DeliveryTargetStart.get(issue.Program Baseline Sprint)}}

When I tried the automation, it shows success but nothing happen :( 

I'm open to any suggestion after many failed attempt 😭

Thank you very much for your help ! 

Have a nice day ! 

[Bill Sheboy]

Hi @Joseph HANI 

The keys for a Lookup Table are static text and although they could represent a regular expression, they would not behave that way in the lookup's get() function.

Instead, I recommend parsing out the unique part of your "Program Baseline Sprint" field to match distinct keys in the table, and use that for the get() call.

One more thing...if you are trying to iterate over the values of a field (like a list of labels) and then access the Lookup Table, that will not work due to scoping limitations of iterators.  Please let me know if that is what you are trying.

Kind regards,
Bill

[Atlass Monster]

Hi mate. Your question is well constructed but I still struggle to get two things:

-Do you set the date by hand in the automation for every delivery or you get it from somewhere via automation? 

- and why you need to match the value inside the table?

[Joseph HANI]

Hello Atlas ! 
Thank you for your answer ! Here is some more information

1. We set up the date value manually inside the lookup table since we know for the year our sprint date 

2. Since the field I'm checking is a label field, and we can have multiple labels inside this field. Here in the example it is DATADE / DATAAN, but we also have many more and the structure is mostly the same, they all end with "AN" or "DE" and the PI number + iterations

And I also want to be sure that anything before "AN" or "DE" is not check because it will mean that I will need to create multiple automation for the exact same needs and then admin those multiple automations every time there is a change or new dates sprints