Unwanted behaviour? - Default versions status
1 1

2 posts in this topic


I think I may have stepped on a unwanted behaviour about versions status : when creating a new version, its status is the first of the selected status in system Settings → Schemas → My_Schema → Version.

If you reorder the statuses (System Settings → Statuses) and move an another status used in your schema one top of the first one used and then save, the status of new versions will change accordingly.

This is not true for tasks that are always created with the Not ready status (or so I believe).  As a result, this is not intuitive at all for versions.  It could be handy to be able to explicitly chose which status is the default one, for tasks and for versions.



Share this post

Link to post
Share on other sites

Hi Francois,

This sounds strange.
And I can't seem to reproduce what you mention.
Or maybe I have misunderstood.
Could you provide us with some screenshots on what it looks like when you set it up?


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
1 1