Yes, that's almost certainly a separate issue. Copy visibility is controlled by a separate table, though the same trigger is used to maintain that other table. So, even if it's the trigger that is touched by the fix on bug 1730758, it'll be a new and different fix.
Yes, that's almost certainly a separate issue. Copy visibility is controlled by a separate table, though the same trigger is used to maintain that other table. So, even if it's the trigger that is touched by the fix on bug 1730758, it'll be a new and different fix.
Thanks, Kathy!