{"action":"opened","issue":{"url":"https://api.github.com/repos/fi-group/clearly/issues/40","repository_url":"https://api.github.com/repos/fi-group/clearly","labels_url":"https://api.github.com/repos/fi-group/clearly/issues/40/labels{/name}","comments_url":"https://api.github.com/repos/fi-group/clearly/issues/40/comments","events_url":"https://api.github.com/repos/fi-group/clearly/issues/40/events","html_url":"https://github.com/fi-group/clearly/issues/40","id":342603216,"node_id":"MDU6SXNzdWUzNDI2MDMyMTY=","number":40,"title":"Going 'back' to a process step","user":{"login":"rickmakkinga","id":24542664,"node_id":"MDQ6VXNlcjI0NTQyNjY0","avatar_url":"https://avatars3.githubusercontent.com/u/24542664?v=4","gravatar_id":"","url":"https://api.github.com/users/rickmakkinga","html_url":"https://github.com/rickmakkinga","followers_url":"https://api.github.com/users/rickmakkinga/followers","following_url":"https://api.github.com/users/rickmakkinga/following{/other_user}","gists_url":"https://api.github.com/users/rickmakkinga/gists{/gist_id}","starred_url":"https://api.github.com/users/rickmakkinga/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rickmakkinga/subscriptions","organizations_url":"https://api.github.com/users/rickmakkinga/orgs","repos_url":"https://api.github.com/users/rickmakkinga/repos","events_url":"https://api.github.com/users/rickmakkinga/events{/privacy}","received_events_url":"https://api.github.com/users/rickmakkinga/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-19T07:03:43Z","updated_at":"2018-07-19T07:03:43Z","closed_at":null,"author_association":"NONE","body":"Currently, a work item can only go 'back' to a previous step (it doesn't actually go back in time, but the steps are executed again) if the process has an explicit loop. \r\nFor example, if a solution for an 'Issue' process is suggested in step X, and rejected in step Y, the work item has to redo step X and step Y. This requires an explicit process flow from step Y to step X. \r\n\r\nIn practice, we see that this ability for changing or fine tuning information is important for end users. A possibly unwanted side effect is that processes are extended with numerous decision attributes and loops to provide this flexibility. This makes the processes overly complicated, often only to facilitate exceptional cases.\r\n\r\nFor consideration: A solution might be to enable the end user (or maybe only the admin) to select one of the previously executed process step to be executed again. Thus setting the work item 'back' to a specific point in the process flow, without the requirement for a provisioned loop in the process. Of course, to ensure compliance to the agreed process, all subsequent steps have to be executed again too. \r\nThis introduces more flexibility without complicating the processes.\r\n\r\n![image](https://user-images.githubusercontent.com/24542664/42926621-47075ec4-8b32-11e8-8e76-2967144e7b2a.png)"}}
{"actor":{"display_login":"rickmakkinga"}}