I need to set up a recurring Dudate for a Feature& track that in Program Board but unable to do so

[RAOS12]

[Joshua Brock _ Seibert Group_ GmbH]

Greetings @RAOS12 and welcome to the Community!

As the other answers have noted, the due date field on a Feature in Jira's Program Board is a static field, meaning there's no native recurrence engine behind it. Neither Jira Align nor Jira Plans was designed for a Feature to automatically roll its deadline forward on a schedule.

The reason goes back to the SAFe model itself: Features aren't intended to be perpetually running items with an auto-refreshing due date. They're deliverables scoped to a Program Increment.

When a Feature doesn't complete in one PI, the SAFe approach is to carry it into the backlog for the next PI (i.e. potentially re-estimated and re-scoped) rather than rolling a date forward automatically.

If you need to track a repeating organizational commitment (something that recurs every PI cycle), the practical approaches are:

• Create a new Feature per PI (e.g., "Compliance Review — PI 5", "Compliance Review — PI 6") and let the PI boundary serve as the natural due date
• Use labels or components to group the recurring feature family for cross-PI reporting
• Define PI end date as the implicit due date rather than maintaining a custom recurring field

If your team is running a scaled agile model where PI cadence is the governing structure for Feature-level work, it may be worth looking at Agile Hive. Rather than placing recurring date fields on individual Features, it models the full PI lifecycle as the organizing layer — Features are planned, tracked, and rolled over through the PI itself, so cadence management is built in rather than bolted on:

• Full Program Increment execution inside Jira — PI scope, objectives, and Feature-level tracking in one place
• PI-to-PI rollover managed through the data model rather than manual date updates
• Program Board with team capacity and dependency mapping
• Everything native to Jira — no separate system of record

There's also a free trial available on the Atlassian Marketplace.

 And just in full disclosure, I work at Seibert Group, the team behind Agile Hive.

Hope this helps, and again, welcome!

Joshua
Content Writer & US Representative
Agile Hive and Aura Apps (products of Seibert Group GmbH)

[garrett_lessard]

Hi there, 

You cannot make a due date recurring out of the box in Jira Align or standard Jira. The feature due date you see on the Program Board is just a single, static date field. It is not designed to automatically roll forward on a schedule. That is why you are stuck trying to map a repeating deadline to a single feature.

Depending on what you are trying to track, here are a few ways to handle this instead:

1. Create a separate feature for each occurrence If you deliver this item repeatedly, like every month or quarter, the cleanest approach is to create individual features for each cycle (for example, "Feature X - July" and "Feature X - August"). Give each its own due date and track them normally. This fits best with how Jira Align is built, since it expects a feature to be a distinct deliverable with a clear start and end.

2. Tie the work to PI or iteration boundaries If the item is due at regular intervals like the end of every sprint or Program Increment, use those timeboxes or milestones to track the cadence. Keep the actual feature due date set to the final delivery deadline rather than changing it for every checkpoint.

3. Use custom fields or tags for the recurrence schedule If you just need to flag a feature as a repeating task without shifting dates, add a custom field or tag like "Monthly" or "Quarterly." You can use this attribute for filtering and reporting, even though the Program Board will still look at the single, main due date.

Why the native field will not work this way:

• The due date is a static attribute, not a scheduling rule.
• Jira Align does not have a background engine to automatically update or clone dates on a cadence.
• The Program Board maps features against fixed timeboxes, so it will not generate future deadlines for the same item.

To help nail down the best approach, a few quick questions:

• Do you want the exact same feature to keep moving forward, or are you delivering a new version of the same capability each time?
• Are you only using the Jira Align Program Board, or do these dates need to sync back to Jira Software?
• What is the actual cadence (every sprint, monthly, or every PI)

Cheers, 
Garrett Lessard Appfire Expert Services

[Trudy P Claspill]

Hello @RAOS12 

Welcome to the Atlassian community.

The error message that is shown is only useful to Atlassian Technical Support to help them access trace information in the logs for your instance. It is not meaningful to end users or Jira Admins to identify exactly what the root problem is.

Here we are a user community, so we don't have access to those logs or your system. If you can answer some questions for us we may be able to advise you on next steps.

What exactly did you do just before this message appeared? Were you trying to simply edit the Due date field?

Have you retried those steps? If so, do you get the same results?

Do you get the same results if you try a different issue?

Have you tried clearing your browser cache and retrying, or trying the same steps through a different browser app or private browser window?

Have you asked a colleague to try the same steps, and do they get the same results?

Have you reported this issue to your Jira Administrators?

[Jean Horn]

👋 Hi @RAOS12 !

Could you give me more details about what you would like to do?

Thanks!

Jean horn