You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.