#746: Parent/child relations are inverted in ticket validation
------------------------+-----------------------
Reporter: rjollos | Owner: rjollos
Type: defect | Status: closed
Priority: major | Milestone: Release 8
Component: relations | Version:
Resolution: fixed | Keywords:
------------------------+-----------------------
Description changed by rjollos:
Old description:
> To reproduce:
> * Create ticket A.
> * Create ticket B and add a //B is a child of A// relation.
> * Attempt to close ticket B with resolution //fixed//. The following
> warning results:
> {{{#!html
> <div id="warning" class="alert fade in">
> <button type="button" class="close" data-
> dismiss="alert">×</button>
> <span class="label label-warning">Warning</span>
> Cannot resolve this ticket because it has open child
> tickets.
> </div>
> }}}
New description:
To reproduce:
* Create ticket A.
* Create ticket B and add a //B is a child of A// relation.
* Attempt to close ticket B with resolution //fixed//. The following
warning results:
{{{#!html
<div id="warning" class="alert fade in">
<button type="button" class="close" data-
dismiss="alert">×</button>
<span class="label label-warning">Warning</span>
Cannot resolve this ticket because it has open child
tickets.
</div>
}}}
For reference, the behavior in question is contained in
`TicketRelationsSpecifics._check_open_children`, which was initially
implemented in [1501152] for #588.
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/746#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
