A form/view/smartobject/workflow version that persists between environments
It can be hard knowing what the version of an item is when it is in different environments. The "version" number that is there is specific to that environment. If an items is packaged out of development and into a test environment the version is typically a smaller number (as there would be multiple versions created in dev). I would like to see a version number/tracking feature that persists when deploying to another environment. If the item is changed in a different environment, then a version is appended to the previous one and not overwritten (could be date/time-server-user). You would then at least see that it came from development and then updated in the test environment, etc. I have seen some developers implement this using the description field which does persist when deployed, but is very manual and easily missed.
Sam Watterson commented
In addition to making debugging much easier by being able to confirm which version of a component is in an environment, having a strong versioning model across environments would also benefit organisations from an audit perspective. E.g. you can pull the version of each component in production, show that those components were in the following packages that were installed, tested and signed off in UAT prior to prod deployment. While most of that audit process sits outside of K2, it hinges on being able to show that the version of something deployed to UAT is the same as the one currently in production.
James Goodman commented
This would be an enormously helpful feature.