A task in a sprint has a "depends on" link to a task outside the scope of the sprint (i.e. in the backlog). This is of course undesirable as it inherently leads to scope change in order to complete it.
It would appear JIRA "let this happen" (i.e. dragging a task into a sprint with "depends on" links) without flinching. Why is there no warning about this when planning a sprint?
Thanks in advance,
Well.... don't know why there's no warning except that the "Links" can be modified and that would be a pain to keep up with.
Make the review/over sight process during Sprint planning look for those instances, or run a check before you start the sprint.
If your not on the cloud, I guess you could add some code to check for that when an issue is moved into a sprint... can't help you with that, never tried it.
Just my thoughts...
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs