Hi,
I am trying to write an automation such that when 3 of the 5 tasks related to my story are 'Done' then the related Story transitions to the next step in workflow - the 3 tasks that need to be done all share a common word in the 'summary' field and I was wondering if I could use this to differentiate between the tasks that need to be 'done' and those that don't.
So far I have the following:
- this automation will transition the linked story to the next step in the workflow but ALL of the related tasks have to be set to 'Done' however as explained above id like to further this such that only those tasks with the word 'development' in the summary field need to be in status 'done' for the related story task to progress to the next step of the workflow (namely SPEC DEVELOPED).
Any help would be much appreciated
thanks
I believe that this workflow will address your needs:
The If statement looks for any issues that have your summary text that are NOT Done. If this returns one or more issues, then it will simply add a line to the audit log. Unfortunately, there is no way to put in a "NO OP" action, so this is the simplest and least intrusive action. If there are no issues that are NOT Done, then it will transition the issue.
Thank you - just to confirm, this is the current set up I have.
My requirement is that once that RCDEMO-708 is transitioned to 'Done' then the automation picks up the fact that all related issues with the word 'Development' in their summary are now in the status 'Done' and then transitions the overall issue to 'Spec Developed'.
I am getting this error when I run the workflow suggested above:
My attempt of putting it into a logical piece of prose would be:
When 'task' is transitioned from in progress > done, Pick up the linked ('Related to') story issue and if all the linked task issues to that story issue with the word 'Development' in the summary are in status 'Done' then transition that story issue from 'Spec signed off' > 'Spec developed' otherwise leave the story in its current status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.