Defect #8193
closedTask Relation "Follows" broke if not added in ascending order
0%
Description
- your database version: MySQL 14.12
- your Ruby version: Ruby 1.8.7 (i386-mingw32)
- your Rails version: Rails 2.3.5
- your Redmine version: 1.1.2 Stable
Create Task 1 with due date today+5
Create Task 2 with due date today+6
Create Task 3 with due date today+7
In Task 3, add relation "Follows" Task 2
In my distribution, the relation isn't shown until I refresh the screen, but that's not the intent of the bug report. If you see the relation added, continue, otherwise hit refresh.
Now, add a second relation "Follows" Task 1. The relation won't be created because Task 1 has an earlier start date than Task 2. If you delete the relation to Task 2 and start over adding Follows Task 1 and then Follows Task 2, it will be accepted.
Updated by Etienne Massip over 13 years ago
- Affected version (unused) set to 1.1.2
- Affected version set to 1.1.2
Updated by Josh Davidson over 13 years ago
Due date=... in description should be start date=…
Updated by Etienne Massip over 13 years ago
Can't reproduce on demo site.
Could you please recreate the situation on demo site where trying to add the 2nd relation in t3 is denied ?
Updated by Josh Davidson over 13 years ago
It's working correctly on our server after a reset (and a couple uninstalled plugins), so let's close the ticket. I'll report back if it happens again.
Updated by Etienne Massip over 13 years ago
- Status changed from New to Closed
- Resolution set to Invalid
No problem, thanks.