Defect #16181
When moving issues to a new project, Target Version is lost.
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues workflow | |||
| Target version: | - | |||
| Resolution: | Duplicate | Affected version: | 2.3.0 |
Description
When moving issues to a new project, the configured relevant Target Versions from the old project should be copied to the new project. This is relevant when merging two formally-distinct projects.
Related issues
History
#1
Updated by Wim DePreter over 8 years ago
Could it be that your target version is not shared with the new project?
related to #5086?
#2
Updated by Dotan Cohen over 8 years ago
Actully, this looks like a dupe of #5086. Thank you for finding that issue, Wim!
Could an admin please mark this as a dupe? Thank you.
#3
Updated by Jean-Philippe Lang over 8 years ago
- Duplicates Feature #5086: Add a warning to inform that target version is reset while moving an issue to another project added
#4
Updated by Jean-Philippe Lang over 8 years ago
- Status changed from New to Closed
- Resolution set to Duplicate