You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello to Everyone!!!
I'm trying to create an automation to change issues in sequence once they belong to the same epic.
This will gonna need to fulfill both Target start and Target End.
I basically discovered this topic that is really similar to what I'm trying to execute, but have the problem with the fields of the Date that are being used
So basically my question is how do I set up this automation for Target End and Target Start? I assume that I need two different automations, and I started with the Target End first.
I'm struggling now how should I change this value of the Due date for JSON to Target End
First things first: there have been open suggestions and community posts about whether or not advanced roadmap fields like Target Start and Target End are supported by automation rules. I encourage you to pause and use this how-to article to confirm if they are supported. Essentially you identify an example issue with your fields set, call a REST API function with a browser tab, and then search for your fields. If they are present they are supported, and if not...they are not supported.
This how-to will also identify the correct smart value (or custom field id) to use for the edit.
Next thing: what exactly do you mean by "sequential issues"? Are you trying to process/update issues in a particular order for some reason. If so, that is not possible with automation rule branches. Branches on more than one item are processed asynchronously and in parallel, and so the processing order is not controllable.
Let's assume the fields are supported (as this suggestion states in the work-around). The biggest challenge is getting the format correct for use in the advanced edit with JSON. I seem to recall these are text and not date/time fields. And so when you set them you need to select the correct format, which is probably jiraDate.