|Anonymous | Login | Signup for a new account||2019-12-13 14:08 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001153||TestLink||User Interface General||public||2007-10-30 21:47||2009-06-03 14:46|
|Product Version||1.7.0 final|
|Fixed in Version|
|Summary||0001153: Statistics for confirmation of delete of bigger amount of data.|
|Description||Whenever you delete or remove connection (test case, requirement) Testlink confirms this as action was successful.|
It would be nice to have the deleted/removed information echoed back to the users.
Delete 100 requirements.
Confirmation: Successfully deleted 100 requirements and then list the items deleted (by title for requirements, test suites, categories or test cases)
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
Not as easy as it seems.
Anyway may be in the future (IMHO low priority)
It's not useful for Test Case or requirements, but it would be nice for Test Suites and Requirement document to add extra page with such statistic (so user can take back unwanted action).
I guess that we had/has some similar issue earlier in discussion. Updated: new feature; low priority.
To implement this we need to traverse subtree/tree branch from
the node you want to delete, to get info about all elements that will be deleted.
Instead of doing just what we do today.
this kind of behaviour must be configurable, because this info may be is not useful for every kind of user.
We should not care about subtree. We can simply do count of nodes and testcases directly in the node. It's not too much work.
I know how danger is to delete accidentally amount of data.
OK, but in this way you will only give this kind of feedback:
4 test suites and 10 testcases will be deleted.
But 10 will be only count of children of removed node, not taking into account
children of 4 test suites.
Anyway we have functions to count in our classes
|Ok. It's better than I knew. Anyway I think that we need not set it configurable. Delete of Test Suite is not often used, so it's not boring.|
|2007-10-30 21:47||auee||New Issue|
|2007-10-31 17:32||fman||Note Added: 0002475|
|2007-11-05 19:19||mhavlat||Note Added: 0002530|
|2007-11-05 19:19||mhavlat||Status||new => acknowledged|
|2007-11-05 19:20||mhavlat||Priority||normal => low|
|2007-11-05 19:20||mhavlat||Category||General => New Feature|
|2007-11-05 19:20||mhavlat||Summary||echo the Deletes done on the system => Statistics for confirmation of delete of bigger amount of data.|
|2007-11-05 19:42||fman||Note Added: 0002532|
|2007-11-05 21:07||mhavlat||Note Added: 0002543|
|2007-11-05 21:12||fman||Note Added: 0002544|
|2007-11-05 21:54||mhavlat||Note Added: 0002547|
|2007-11-07 19:58||mhavlat||Relationship added||related to 0000380|
|2009-06-03 14:46||mhavlat||Category||New Feature => User Interface General|
|Copyright © 2000 - 2019 MantisBT Team|