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 ?
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.
Thanks for replying. To clarify, by "initial state" I mean first state (let's call it "To Do") AFTER issue is created.
My problem is not with fields not being populated. All fields are already populated. Problem is that Users modify "Description" field by changing text that is already there. I'm looking for a way to make sure that those changes are applied before allowing transition to any other state.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events