Defect #21766
closed
CSV import does not keep the project it was clicked from
0%
Description
When clicking the new Import link in the side bar menu of Issues, the project information seems to be lost.
There are several consequences:- Clicking the sidebar links in one of the import steps has various consequences, from no action (custom queries) to Error 500 (Calendar, Gantt)
- When reaching the field mapping step, there is a project which is preselected, but not the one the import link was clicked from.
Files
Updated by Olivier Houdas almost 9 years ago
Sorry, for the Calendar and Gantt links, the error 500 is due to a plugin.
Updated by Toshi MARUYAMA almost 9 years ago
- Status changed from New to Needs feedback
Did you solve problems?
Updated by Olivier Houdas almost 9 years ago
Well, not #2.
The fact that side-bar menus are not really relevant in the import page (since it is not set to any project) is just a note.
This is not a serious issue, but there is a reference to @import.project in the mapping page (views/mapping.html.erb) which returns a value, but we will never get the project we actually came from, because the link in the project\issues page is not project-dependent.
Updated by Toshi MARUYAMA almost 9 years ago
- Status changed from Needs feedback to New
Updated by Marius BĂLTEANU about 5 years ago
- Status changed from New to Confirmed
I confirm this behavior in the latest trunk.
Updated by Marius BĂLTEANU about 5 years ago
- Subject changed from CSV import does keep the project it was clicked from to CSV import does not keep the project it was clicked from
Updated by Marius BĂLTEANU about 5 years ago
- File 0002-Fix-CSV-import-does-not-keep-the-project-it-was-clic.patch 0002-Fix-CSV-import-does-not-keep-the-project-it-was-clic.patch added
- Assignee deleted (
Marius BĂLTEANU) - Target version set to Candidate for next major release
Attached is a fix for this problem, it can be applied on top of #32196.
Updated by Marius BĂLTEANU about 5 years ago
Should we include this fix in 4.1.0?
Updated by Go MAEDA about 5 years ago
- Target version changed from Candidate for next major release to 4.1.0
Updated by Go MAEDA about 5 years ago
Confirmed the issue. Since the change is small, I have set the target version to 4.1.0.
Updated by Jean-Philippe Lang about 5 years ago
- Status changed from Confirmed to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Committed.