Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Program Board "quirk" question

Chris Berry
March 30, 2026

This is kind of a confusing question so I'll do my best:

When under Plans -> Program board, and assigning Features to sprints, there is an oddity with due dates.

If the Feature has no sprint set in it's sprint field, and you drag and drop the Feature card into a sprint lane on the board, it auto-changes the due date to the last day of that sprint. Ok fine so far.

If you manually set a sprint in a Feature, say sprint 1 with a due day of April 1, and then drag the card to sprint 2 with a due date of May 1, it does NOT update the due date field of the Feature. It keeps the due date April 1 even though you assigned it sprint 2 with a due date of May 1.

Why does the system work that way? It's causing confusing because now the sprint end date and the due date of the Feature are no longer in sync.

1 answer

1 accepted

0 votes
Answer accepted
Ravi Sagar _Sparxsys_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 30, 2026

Hi @Chris Berry 

Sprint end dates and due dates will not be in sync, but you can always create an automation rule to update the due date when the sprint value changes.

I hope it helps.

 

Chris Berry
March 30, 2026

Hi, thanks. Yes I could do that.

I'm just trying to understand the "why" behind it. Not auto-updating the date based on the sprint date could cause confusion. I'm not sure I see a good reason for why they would not be in sync or why the sprint shouldn't "override" the due date in this scenario.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events