RELATED IDEAS
Data Range field is broken
What is the challenge? |
Data range field is not working correctly when you switch from Manual dates to Sprints dates. Also, there is a bug if you shift requirements back and forth, the date range filter in the parent feature will be updated only to the future dates, but start date won't get updated past its current value. |
|---|---|
What is the impact? |
There is a workaround to fix this but it requires switching the value from "sprints" to manual, then setting the values to empty and then switching back to Sprints. Sometimes even this doesn't work. |
Describe your idea |
-
ADMIN RESPONSENov 11, 2025
When you move a record, It will keep the original start date but the end date will update to the new sprint's end date. (this is designed so that you can spot rollovers). It will always retain the latest possible end date, so if you later pull it up to an earlier sprint, it will keep that original end date as well.
If you move a requirement, then it keeps the earliest start date for a sprint until you move it sooner than that, it keeps the latest date until you move the req to a later date
© 2025 Aha! Labs Inc.•All rights reserved