If there is more that 1 subtask on a parent, and if the subtask updates the parent's state while traversing the subtask workflow, only the oldest substask will update the parent state as it goes through the workflow. Moving a new subtask through the workflow will not update the parent status, even though that newer subtask is executing all the same transition code.
In my business rules, having only one subtask per parent makes sense and prevents the problem I mentioned above.
Anyone have any thoughts?
Steve
I guess a validator on creation like this (scriptrunner example):
issue.parentObject?.subTaskObjects.size() == 0
would allow you to create a subtask only if it's the first one for the parent issue
if you dont have a scriptrunner try looking at options for validators you have, maybe there's something else to make this check
Thanks for your input on my question, Ilya - I've found it helpful to me!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.