Is it possible to automatically persist Jira Plans inferred dates into the tickets?

[Ugo Abate]

When using Jira Plans it is possible to have inferred dates based for instance on the sprint or the release a ticket is assigned to. It looks to me that when date are inferred, these dates are not saved/attached to the ticket and I'm looking for a way to achieve that.

[Ugo Abate · Accepted solution]

I have my answer https://support.atlassian.com/jira-software-cloud/docs/how-advanced-roadmaps-rolls-up-dates/

Inferred dates are never really saved to the tickets and only exists for planning purposes.

This is officially my dead end :D

[Marc - Devoteam]

Hi @Ugo Abate 

Welcome to the community.

When using Jira Plans and you change dates, you need to save than changes made in the plan to the issues,

The button is in the top right corner, you will need to have the correct project permissions on the issues you want to change.

Or is this not your use case?

[Ugo Abate]

The dates are not manually added, are inferred by Jira plans based on the sprint the ticket is added to. The, even if I save the changes, inferred dates are not persisted in the ticket. More precisely, if you open the ticket, you'll see that the date look not set at all

[Marc - Devoteam]

Hi can you show an example by using screenshots

[Marc - Devoteam]

Hi @Ugo Abate 

As you mention on @Jeffrey Wolfe , can you show the automation you have setup.

Please mind the following:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

[Ugo Abate]

It's a company managed project. I don't have a rule yet. I've only verified that Jira Plans "inferred dates" do not update target dates either.

I'm not sure what fields should I look at that correspond to inferred dates... I'm not even sure there is one.

[Marc - Devoteam]

Hi @Ugo Abate 

If you use fields on an issue with dates, or sprint dates you need an automation rule to copy these values to another field.

this field can then be used as the persistent date

[Jeffrey Wolfe]

If you want to persist them, one workaround is using Automation for Jira. You can create a rule that triggers when a sprint or release is set, then copies the inferred start/end dates into custom date fields in the ticket.

Another option is using Scriptrunner if you're open to scripting. A custom script could extract the inferred dates and update the corresponding issue fields automatically.

[Ugo Abate]

this is what I'm trying, but it's not clear to me how to access the inferred dates... I've tried "targetstart" and "targetend"... but no luck