Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


My task inherits due date form the release date. How do I stop that?

When I assign a Jira task to a release, it automatically inherits its due date from the release date. This forces every task assigned to a release to end on the same date. Clearly some tasks will be completed before others. I do not want to set dates directly on Jira tasks because we use story points.

The idea is to make story point estimates for tasks, then sort them into epics that have target start and end dates to comply with release dates. If a Jira task inherited any due date, I would want it to inherit that from the epic, not the release. However, generally I don't have dates on Jira tasks at all and only story points.

What is the common way to accomplish this? 

Is there a different approach that is more common practice? 

How do I stop Jira tasks for inheriting due dates from the release they are assigned to? 

1 answer

1 accepted

2 votes
Answer accepted

I just found the configure option of "infer dates" and set it to none and that did the trick. 


I would still be interested in hearing how other folks do this in general. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events