'Create project version' could be more user friendly

Related products: Software Factory

A new Thinkwise developer was creating his first project, using the e-learning.
After deploying his datamodel and making a few changes in the User interface he wanted to create a new project version.

Sadly here it went wrong. 

He used the Task ‘Create project version’ instead of ‘Copy project version’, expecting it to create a new version of his project.
After a while he found out that all his work was gone and didn't knew what caused it.

Maybe we should rename the task or make it a bit more clear that it is used for creating a new empty project version. This is not something you are not going to do many times, during development. 

Any suggestions?

What is the function of this task? The version is automatically created when creating a project. And once v1 of a project is build you only want to copy the version. I would opt for removing this button, unless someone can explain when you would use this task? 


This task is called automatically after creating a new project, and there are indeed not many use cases to create an empty project version in an existing project. We will consider hiding this task if there is already a project version available.

 


This task is called automatically after creating a new project, and there are indeed not many use cases to create an empty project version in an existing project. We will consider hiding this task if there is already a project version available.

 

Hi Jasper,

I think this would be a appropriate resolution.


In the 2020.2 version of the Software Factory, this task will be hidden if there is already a project version available.


In the 2020.2 version of the Software Factory, this task will be hidden if there is already a project version available.

Hi Jeroen, Good to know it's already implemented but why in the 2020.2 release? The 2020.1 isn't even out yet.


In the 2020.2 version of the Software Factory, this task will be hidden if there is already a project version available.

Hi Jeroen, Good to know it's already implemented but why in the 2020.2 release? The 2020.1 isn't even out yet.

You are right that the 2020.1 release is not out yet, but it will be very soon. The deployment package has already been built and is being tested. The 2020.1 version is therefore closed for development.