Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000803Taste[All Projects] TASTE-IV/DVpublic2018-09-11 13:232021-05-21 09:16
Reporterttsiodras 
Assigned Toellidiss 
PrioritynormalSeveritymajorReproducibilityN/A
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Summary0000803:

Ability to "dump" steps taken by GUI when we reach a buggy state

Description

As more and more users use TASTE and the GUI to create increasingly more complex designs, being able to report how exactly the GUI reached a bad state is very important. As-is, when this happens, it is very difficult to reliably reproduce the bad state again - but if we had the ability to "dump the steps" that were taken since the GUI was launched on this particular design, then Ellidiss would be able to consistently and reliably reproduce the issues.

Such a history of "steps" should in fact already be there, since the "Undo" functionality is in all likelihood depending on something similar.

We therefore ask for some way to trigger a "dump history" functionality on the GUI, that would be used anytime we need to report a GUI bug. The dumped history should contain information that describes fully the steps that drove the GUI to the "bad" state being reported - so it must be minimal and complete. Note that in contrast to the "Undo" information, this list should never have things removed from it - only appended to it (since the "Undo" operations themselves may introduce bugs).

Steps To Reproduce

As more and more users use TASTE and the GUI to create increasingly more complex designs, being able to report how exactly the GUI reached a bad state is very important. As-is, when this happens, it is very difficult to reliably reproduce the bad state again - but if we had the ability to "dump the steps" that were taken since the GUI was launched on this particular design, then Ellidiss would be able to consistently and reliably reproduce the issues.

Such a history of "steps" should in fact already be there, since the "Undo" functionality is in all likelihood depending on something similar.

We therefore ask for some way to trigger a "dump history" functionality on the GUI, that would be used anytime we need to report a GUI bug. The dumped history should contain information that describes fully the steps that drove the GUI to the "bad" state being reported - so it must be minimal and complete. Note that in contrast to the "Undo" information, this list should never have things removed from it - only appended to it (since the "Undo" operations themselves may introduce bugs).

TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2018-09-11 13:23 ttsiodras New Issue
2018-09-11 13:23 ttsiodras Status

new => assigned

2018-09-11 13:23 ttsiodras Assigned To

=> ellidiss

2018-09-11 13:26 ttsiodras Description Updated View Revisions
2018-09-11 13:26 ttsiodras Steps to Reproduce Updated View Revisions
2018-09-11 13:27 ttsiodras Description Updated View Revisions
2018-09-11 13:27 ttsiodras Steps to Reproduce Updated View Revisions
2021-05-21 09:16 maxime Status

assigned => closed

2021-05-21 09:16 maxime Resolution

open => won't fix



Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker