Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Advanced Roadmaps: Using Target Date Rollups for Baseline Dates Automation Rule?

Isabella Musial
Contributor
January 2, 2024

How can I update Baseline Dates using my Automation Rule if Target Dates are dynamically rolling up in Advanced Roadmaps (aka Plans) and not populating specifically on a Jira Issue?

 

So I solved how to match Baseline Dates to Target Dates. 

Solved: How to set Baseline Dates to match Target Dates (atlassian.com)

However, the Target Dates must be populated / visible on a Jira issue for this to work. 

AutomatedTargetDates2.PNG

When using Advanced Roadmaps (Plans), the Target Dates roll up dynamically based on the Story dates and are not visible on a Jira Issue. 

AutomatedTargetDates.PNG

We want to keep the Target Dates rolling up, but also want to be able to manually trigger our Automation Rule to populate Baseline Dates.

Thanks, 

Bella

(FYI: @Bill Sheboy since you always seem to help!)

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 7, 2024

Hi @Isabella Musial 

First thing, I am using Jira Cloud and not Server version, and so cannot confirm my suggestions...with that out of the way.

I do not believe dynamic fields are supported by automation rules, such as for built-in features and from marketplace apps.  Those are often calculated just-in-time using code and so are not persisted with issues.

You could confirm this for the plan fields using this how-to article with an example epic, and then searching for the fields.

https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html

Kind regards,
Bill

Isabella Musial
Contributor
January 8, 2024

Thanks for responding! 

The Target Date fields are available when populated manually. If you are using the rollups, and the data is not manually updated, then they do not appear. I did verify and used 2 different Epics to test it. 

"customfield_10104": "Target end"
"customfield_10103": "Target start"

I just have a feeling that because they are dynamically calculated, I won't be able to reference those fields in my automation rule.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 8, 2024

Did you try that how-to article with an example epic to see if the smart values are available to rules?

Isabella Musial
Contributor
January 9, 2024

I did. I am using Target Dates in other places and it's working. The Target Dates are not on the page if not manually populated.

Isabella Musial
Contributor
January 9, 2024

Unless I am misunderstanding your question.  I did review the page and used the link to check for the fields.

{{https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names}} 

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2024

Sorry, I am out of ideas on this one. 

You may need to wait for someone using Jira Server to comment further, or work with your Jira Site Admin to ping the Atlassian Support team to learn what they suggest.

Isabella Musial
Contributor
January 9, 2024

Thanks for trying - I appreciate it. I'll try to think of alternatives, but this may be all I can do! 

Suggest an answer

Log in or Sign up to answer