Loading Profile...
Cloning a project doesn't clone the versions
When creating a new project, if you select another project as a template, the versions from that project aren't copied over even though the blurb underneath the dropdown states that they will be.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?This has been logged but we will have to think on this one. In most scenarios, versions are usually unique for a project unless you don't use versions (like Default). There is also the added complexity of release dates and previously released versions.
I am not entirely sure if the text or functionality is wrong here (i.e. we do copy versions but it is a bug or we just don't support copying versions).
This has been planned to look into in 2.0
The company says
this solves the problem
2 Comments Add a comment
This solves the problem
-
Yeah I don't think versions need cloning and the release dates point is a good one. The paricular project I was cloning had generic and undated versions (1.0, 1.1) and it would have been handy in that case to clone them, but generally I would say that versions shouldn't be cloned. So just the text needs changing. -
I figured as much. Because this is a small copy change, we have bumped it up to 1.9
EMPLOYEE
