Feature #7626
version due date and issue due date interactions
| Status: | New | Start date: | 2011-02-15 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | - | |||
| Resolution: |
Description
When adding issues to versions I expected the due date of the issue to match the due date of the version.
Here are some behaviors I thought would be nice:
- If an issue without a due date is added to a version with a due date it gets that due date
- If a due date is changed on a version prompt to 'standardize' this due date for the rest of the issues
- If an issue due date is changed to after the version due date a warning is thrown(?)
I was expecting similar interactions with due dates as related tickets have with percent done.
Related issues