-
This is because I first named milestone as 3.1.2, then renamed it to 3.2.0. Since milestone is different object managed separately from issue, the name changing is hard to be reflected in issue change log. This is also true for some other separately managed objects such as assignee. If the assignee changes the name, it will be reasonable NOT to record the name change in every assigned issues.
So I'd rather treating this as a limitation, instead of a bug.
-
Previous Value Current Value Open
Closed
| Type |
Bug
|
| Priority |
Minor
|
| Assignee | |
| Affected Versions |
Not Found
|
Issue Votes (0)
Just something I observed:
The milestone is 3.2.0 but the log sais 3.1.2