Description for New Version Update

Hi @rishub,

I'm not sure if there is an automated way to do this while publishing a new version. But we can probably use Process model annotations to track the Process model version history. Whenever there is a new stable version of the process model,we have to make a note of the changes manually in an annotation. Not an elegant way but does the job.

Thanks
Raj

Sounds like a good idea for a shared component/plugin..

We have used annotations (like mentioned above) that says version and description of change. We also use our agile tools (like JIRA or Agile Manager) to keep change logs/notes of objects changed and description of changes.

@Christineh: the use case for this requirement is to minimize the clutter on process models as some of our process models have more than 500 versions so adding annotations won;tbe food enough. Also, it will minimize use of external tools.