Actions
Defect #11738
closedBatch update of issues clears project path
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
The following just happened:
- opened project
- opened list of issues
- set filter to show all with status "Resolved on Dev"
- selected all issues, right clicked, batch set "% Done" to 100%
- list reloaded, but in root, not in project, so all issues of all projects with the given status where listed, of course I didn't realize at the time...
- selected all again and batch updated status to "Resolved on Test"
- made some other developers a bit angry and had to restore yesterday's backup of our Redmine system
I have done this procedure before but never noticed this behaviour. Has anybody else noticed it? Is it a configuration problem? Our setup is pretty basic, though...
We are using:
Environment: Redmine version 2.0.3.stable Ruby version 1.8.7 (x86_64-linux) Rails version 3.2.6 Environment production Database adapter PostgreSQL Redmine plugins: no plugin installed
Updated by Lorenz Breu about 12 years ago
New insight:
Seems that it happens when issues of both a project and a subproject are updated at the same time...
Updated by Etienne Massip about 12 years ago
- Status changed from New to Confirmed
- Target version set to Candidate for next minor release
Reproduced on demo.
Updated by Etienne Massip about 12 years ago
- Subject changed from Batch update of issues clears project-filter to Batch update of issues clears project path
Updated by Jean-Philippe Lang about 12 years ago
- Status changed from Confirmed to Closed
- Assignee set to Jean-Philippe Lang
- Target version changed from Candidate for next minor release to 2.1.0
- Resolution set to Fixed
Confirmed with 2.0-stable but fixed in current trunk.
Actions