Project

General

Profile

Actions

Defect #21766

closed

CSV import does not keep the project it was clicked from

Added by Olivier Houdas about 8 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Importers
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

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:
  1. Clicking the sidebar links in one of the import steps has various consequences, from no action (custom queries) to Error 500 (Calendar, Gantt)
  2. When reaching the field mapping step, there is a project which is preselected, but not the one the import link was clicked from.

Files

Actions #1

Updated by Olivier Houdas about 8 years ago

Sorry, for the Calendar and Gantt links, the error 500 is due to a plugin.

Actions #2

Updated by Toshi MARUYAMA about 8 years ago

  • Status changed from New to Needs feedback

Did you solve problems?

Actions #3

Updated by Olivier Houdas about 8 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.

Actions #4

Updated by Toshi MARUYAMA about 8 years ago

  • Status changed from Needs feedback to New
Actions #5

Updated by Marius BĂLTEANU over 4 years ago

  • Status changed from New to Confirmed

I confirm this behavior in the latest trunk.

Actions #6

Updated by Marius BĂLTEANU over 4 years ago

  • Assignee set to Marius BĂLTEANU
Actions #7

Updated by Marius BĂLTEANU over 4 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
Actions #8

Updated by Marius BĂLTEANU over 4 years ago

Attached is a fix for this problem, it can be applied on top of #32196.

Actions #9

Updated by Marius BĂLTEANU over 4 years ago

Should we include this fix in 4.1.0?

Actions #10

Updated by Go MAEDA about 4 years ago

  • Target version changed from Candidate for next major release to 4.1.0
Actions #11

Updated by Go MAEDA about 4 years ago

Confirmed the issue. Since the change is small, I have set the target version to 4.1.0.

Actions #12

Updated by Jean-Philippe Lang about 4 years ago

  • Status changed from Confirmed to Closed
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Committed.

Actions

Also available in: Atom PDF