-
Task
-
Resolution: Fixed
-
None
-
High
-
A feedback button (same system as the error logging in the UI) can be enabled for specific users so that they can send detailed informations about problems in the UI even without real error occurrence.
-
Emptyshow more show less
problem
Some users report about problems in the UI we can not track, probably related to different latencies of request or what ever. Since no real JS error happens, no error and data can be logged from the UI.
solution
Since our UI logger provides also a feedback button we should provide a possibility to enable that feedback button. Currently we want to enable that only on user level, if it makes sense to evolve that feature we can improve the filter possibility for tasks / customers what ever.
further todos / realization
Currently I would just add an empty list runtimeOptions.debug.enableJsLoggerFeedback to the application.ini which then can be overwritten in the installation.ini. The list should get a list of logins of the users which should get the button then.
To enable the button just set showFeedbackButton to true when needed in jslogger.phtml.
Please check the therootcause API documentation, by default the feedback window contains a radio button to choose between bug and feature request. We don't want that, probably this can be disabled.
Test the Feedback button in different situations in the application, see for example the linked TRANSLATE-1037 issue. We should not introduce more UI problems by enabling the button.
- relates to
-
TRANSLATE-1037 VisualReview and feedback button are overlaying each other
- Done