Defect #17211
closed
Assigning Parent Project when Copying Project
0%
Description
Assignation of Parent Project for a project you are copying does not "stick" until the project first creates.
When I try to assign a parent project to a project while trying to create a copy of a project, everything else seems to go through except for the parent project field. After clicking "Copy" and looking at the project page shows the new copied project on the top level. I have to go into the project settings and assign it and "save" in order for it to go through correctly.
Happens all the time for me...
Files
Related issues
Updated by Jean-Philippe Lang almost 10 years ago
- Resolution set to Cant reproduce
Tested with 2.4-stable and trunk, works fine for me.
Updated by Toshi MARUYAMA almost 10 years ago
- Status changed from New to Needs feedback
Updated by James H almost 10 years ago
It still does it for us.
I have included a screenshot of before & after "Copy" has been pressed.
Subproject is selected before "Copy" and then I scroll down and click "Copy"
The project is created but the "Subproject of" field becomes empty.
I have not changed any of the ruby code.
Updated by Michael Esemplare almost 10 years ago
Need more information as we cannot reproduce.
Can you provide the following:
- Plugins installed (if any)
- Excerpt of production log after the copy is executed.
Updated by James H almost 10 years ago
No plugins.
So I did some testing:
Subprojects do not get assigned correctly during the copy action when issues have problems copying over.
Some of my issues in the "copy from" project could not copy over successfully due to certain trackers being disabled for the project. Apparently thats the only time when the subproject returns blank.
Sort of related to #17499
Updated by Toshi MARUYAMA over 9 years ago
- Related to Feature #17499: Issues Do Not Copy when Issue Tracker is Disabled from "Copy From" Project added
Updated by Go MAEDA almost 4 years ago
- Status changed from Needs feedback to Closed