Preventing transition when unsaved changes exist

Jakub Nowacki_inkkfl

Hello,

 

I've created a workflow where edits to Issue's subject and description are only allowed in initial state. After transitioning to next state further edits are disabled.

Problem is that users who edit description in initial state forget to hit save button and transition to next state. Then workflow doesn't allow to "go back" and saving isn't allowed anymore due to edits disabled.

I'm looking for a way to prevent this misuse. Is there a way to either:

- block transition when unsaved changes exist ?

- force save when transition occurs if changes exist ?

John Funk

Hi Jakub,

I assume by "initial state" you don't mean on Create. Otherwise, you could have a different create screen from the edit screen. 

You might consider using a Transition screen that makes sure the fields are populated before the transition can happen.