nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Ugo Abate_rp23xw

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.

Accepted answers

Ugo Abate_rp23xw

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

All comments

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.

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_rp23xw

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