[umbrello-devel] [umbrello] [Bug 334435] New: No redo when deleting actor on use case diagram

[Ralf Habacker]

https://bugs.kde.org/show_bug.cgi?id=334435

Bug ID: 334435
Summary: No redo when deleting actor on use case diagram
Classification: Unclassified
Product: umbrello
Version: 2.13.0
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: umbrello-***@kde.org
Reporter: ***@freenet.de

Undoing a removed actor on a use case diagram which is connected with several
use cases do not restore the associations. If these connections are named, only
the names are restored.

Reproducible: Always

Steps to Reproduce:
1. open umbrello
2. add a use case diagram
3. add an actor, 5 use cases and connect the actor with the use cases
4. remove the actor
5. undo 1 step
Actual Results:
The actor and the names of the associations are restored, the associations
itself not.

Expected Results:
The associations should be restored too

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=334435

Andrew Crouthamel <***@kdemail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO

--- Comment #1 from Andrew Crouthamel <***@kdemail.net> ---
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test
if the bug is valid in the latest version? I am setting the status to NEEDSINFO
pending your response, please change the Status back to REPORTED when you
respond.

Thank you for helping us make KDE software even better for everyone!

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=334435

Andrew Crouthamel <***@kdemail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED

--- Comment #2 from Andrew Crouthamel <***@kdemail.net> ---
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you
help us out and re-test if the bug is valid in the latest version? This bug
will be moved back to REPORTED Status for manual review later, which may take a
while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!