Support sprints time box in timeline view

[Neta Ilany]

We use ideas for initial roadmap planning, and to create a quarterly view before we create the dedicated delivery tickets (=epics) and assign to teams. 

The timeline feature is a good visualization tool - but it only supports specific dates. 

When we are in initial high level planning phase, we usually estimate in sprints (example - start in sprint 200 and end in sprint 204). 

Is there any plan to support sprint dates as in Jira plans? And - is there a plan to support the timeline view by sprints, once defined?

Thanks,

[Hermance NDounga · Accepted solution]

Hello Sebastian, 

Indeed these fields types aren't supported in Automation yet as per Known limitations of Jira Product Discovery.

We will explore support for these fields, but it is not prioritized on the roadmap yet. 

There is no workaround at the moment, bu could you please elaborate more on your use case?

Cheers, 

Hermance

[Bill Sheboy]

Hi @Hermance NDounga 

FYI the link you provided is broken.  Is this the one you wanted for the known limitations?

https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648

And...I just tested and although an example field of Reaction type is returned by the REST API to check for things automation supports, the value is always null in the response.  That behavior might confuse people into thinking it is sort-of supported.

Kind regards,
Bill

[Hermance NDounga]

So weird for the link; thanks Bill! 

Full disclosure here: We are in the middle of a refactoring of the fields - to improve on performance, and make sure we can scale. so basically, their behaviour might change very soon, and that's also why we aren't too sure yet how to integrate them with automation - because the way they are stored/built can change very soon. 

So yup it's not for today :) but you understand why we don't really optimize for their current behaviour.