This bug is fixed in 2.0.21.
-David
On Mon, Dec 19, 2016 at 8:55 AM Philip Sanders
wrote:
> I think I just hit this issue with the same release too. Is there any way
> to get out of this situation other than creating an entire new review?
>
>
> On Friday, July 3,
I think I just hit this issue with the same release too. Is there any way
to get out of this situation other than creating an entire new review?
On Friday, July 3, 2015 at 3:54:30 PM UTC-5, David Trowbridge wrote:
>
> Dan,
>
> This is something that used to work correctly, but obviously
WE are running 2.0.17 and have managed to create a situation and dont know
how to resolve it - or whether its a defect
Someone created 2 reviews with code changes that were dependent.
They marked Review 2 as Depends On Review 1 - this then updated the
'Blocks' field.
They then marked Review 1