Can a JPD date field hold a range and support grouping by Quarter?

Question

Hi all,

We're using Jira Product Discovery for roadmapping and have hit a gap in how time is modelled on ideas.

Our current setup

* Target Quarter: a multi-select field we created so an idea can be tagged with more than one quarter. It groups and filters well, but it can't be used on the Timeline view.
* Start date and Target date: two Date fields that do work on the Timeline view.

The problem

* A Date field only holds a single day, so Target date can't express a window. If we expect delivery to land somewhere between 20 October and 11 November, we have to pick one date and lose the uncertainty.
* Ideas that span more than one quarter can't be represented accurately in the date fields, so we maintain Target Quarter alongside them, which means keeping two sources of truth in sync.
* Views can't group by quarter on a Date field, so stakeholders who ask for a quarterly view can't get one from Target date.

What we'd like

We're happy keeping Start date and Target date as separate fields. What's missing is a field type where the value can be a date range (a from and a to), so that:

* Target date can represent a delivery window, e.g. 20 Oct to 11 Nov.
* The Timeline view can plot that range natively.
* Views can group by month or quarter based on the date, so we no longer need a parallel multi-select field.

Questions

* Is there a supported way to do this today that we've missed?
* Is a range-type date field, or grouping by quarter on Date fields, on the roadmap? If there's an existing feature request, please point us to it and we'll vote.
* How are others handling this? Automation or other workarounds that scale would be very welcome.

Thanks!

Tanguy Crusson · Answer

Hi @Roderick this is actually how JPD date fields work today?

Sami Shaik · Answer

@Roderick ,

Two things to add to @Matthew Sinclair and @Josh answers, because they settle your questions 1 and 2.

1. Your Date field is already a range, just not an arbitrary one. Under the hood a JPD Date value is stored as a start and end pair, {"start":"2026-10-01","end":"2026-10-31"}, which is why Josh's precision point works: choosing a month or a quarter in the picker stores the whole window, and the Timeline plots it. You can see the raw shape in Bill Sheboy's automation answer (the match() trick to pull start and end out). What the picker does not give you is a free-form 20 Oct to 11 Nov inside one field; the precision steps are day, month, quarter. So the honest answer to "a from and a to": you have it at month and quarter grain today, not at day grain. The timeline docs are explicit that the view "doesn't reach the precision of weeks".

2. Where to vote. I checked jira.atlassian.com today: the JPD project there holds bug reports only, so there is no suggestion ticket for a day-level range or for grouping by quarter to vote on. Feature feedback for JPD runs through the Jira Product Discovery Community group, where the team posts the roadmap link and reads threads like this one. Your post is well written enough to be that request; I would leave it as is and let the JPD team see it here.

3. Keep Target Quarter, but stop maintaining it. Views group by select fields, not by dates, so Josh's suggestion is the right one: an automation rule on Field value changed: Target date that sets Target Quarter from the stored end value. That turns it into a derived field with one source of truth. Build it on one idea first and check the rule's branch logic for the quarter boundaries before trusting it across the project.

Josh · Answer

Hi Roderick,

One thing worth checking before building a workaround: JPD's own date fields aren't limited to a single day. When you set Start date or Target date on an idea (or on a custom Date field created in JPD), the date picker lets you choose the precision: a specific day, a month, or a quarter. Picking "Q4 2026" or "November 2026" stores that as a window rather than one day, and the Timeline view plots it across that whole period.

For your example, that means Start date = October and Target date = November gives you a 20 Oct to 11 Nov style window at month level, and an idea that spans two quarters can be Start Q4 / Target Q1 without a separate field. Stakeholders who think in quarters can then be shown the Timeline view with the time scale set to quarters, which usually covers the "quarterly view" request.

What I wouldn't count on is a true from/to range at day level inside a single field, or grouping a list/board view by quarter derived from a date; for grouping you'd still need a select field. If you keep Target Quarter for that, an automation rule on "Field value changed: Target date" that sets Target Quarter accordingly keeps it as a derived field, so you only maintain one source of truth.

I'd test the month/quarter precision on a couple of ideas first, since it may change how your existing day-level Target dates read on the timeline.