All Collections
Monitor, control and improve processes
Manage improvements from idea to live
Manage improvements from idea to live

Mark comments as 'change suggestions' to manage them in an approval flow from start to finish.

Peter Olsen avatar
Written by Peter Olsen
Updated over a week ago

Your version management can start from the initial change suggestion and Gluu ensures a controlled flow through the following steps:

  1. Change suggestion submitted to a process or an activity by a user.

  2. Process Owner or Editor assigns a status to the suggestion, so that e.g. once it is ready for implementation it gets the status "Approved".

  3. Approved suggestions then show for process editors who can view and pick them for implementation in work sessions.

  4. Once a change suggestion is implemented it can be marked as part of a version and will change status to 'Implemented'.

  5. Now you can find the version, its original change suggestion and all detail in a single update.

Now, let's go through it step by step in more detail.

TIP! Want to learn more about about versioning? Check out this article that takes you through everything you need to know: 'How to handle versioning in Gluu'

Submitting a change suggestion

Any user with access to the process can submit comments or change suggestions. Comments can later be turned into change suggestions and vice versa:

Reviewing a change suggestion

  1. Other users reply to the suggestion and it is reviewed and discussed. Labels and detail can be added.

  2. When the idea takes shape it can be given a name:

  3. If you're a Process Editor or Owner then you have an option to change status of the change discussion at any point in time:

Implementing a change suggestion

  1. Approved change suggestions will now show when the process is in edit mode:

  2. Clicking the button will show the suggestions and their status (except 'rejected' suggestions):

  3. The process editor can now change status to 'Implemented' as the person implements the suggestions in the process flow or the underlying work instructions.

  4. When saving the work, the editor will be able to create a formal version. This will contain all changes since the last version was created and bundle everything:

  5. Completing the change sessions lets the editor give it a name and all history and discussion will be included.

Showing version and change history

  1. The change suggestion is now combined into a single update:

  2. Clicking 'version changes summary' opens a drawer to show the version's change log:

  3. Each work session can be accessed to show differences between before and after:

Did this answer your question?