[almighty] Save, Undo + Edit UI Model
Thomas Mäder
tmader at redhat.com
Wed Aug 10 13:21:43 UTC 2016
Am 10.08.2016 um 15:16 schrieb Sarahjane Clark:
> Deleting (like actual removal from the database) is a little tricky
> with the concept of dependencies and blockers. For example, if you
> delete card A, which card B has listed as a dependency, would we just
> not show card A in card B's dependency list anymore? Would it be
> listed, but just have a strikethrough?
>
I would expect actual deletion to be a rather rare operation: usually
work items are simply closed. That said the only way to prevent dangling
references would be to check for them before delete (we're not doing
that right now)
/Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160810/183cfb7e/attachment.htm>
More information about the almighty-public
mailing list