-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable customer preferences #693
Comments
Hi Mohd, this screen is not implemented, yet (there shouldn't be a link to it, we seemingly forgot to disable direct access, though). Eventually it would be good to make this available, though, I guess. Thanks for pointing it out, Sven |
Hi Sven, Thanks for the update.. As OTRS 6 CE is no longer pushing security update, my team are looking to move over to OTOBO. |
Hi Mohd, not without some development, I fear. We will definitely reimplement this, I cannot make promises when it will happen, exactly, though. If you need it straight away, you can send us a message to hello@otobo.de to hire us, or if you have the capability, enhance OTOBO yourself (please open a pull request, if you do :) ). Best regards, Sven |
When CustomerPreferences is enabled, then the following test scripts should be reactivated too:
|
Also: use Test2::V0, eradicate $Self
This is fine, as customer preferences are not yet active. See #693.
…[type=field] should be improved somewhen.
Should be fixed. Standard settings still need some overhaul, but that is true for the agent interface, too and will be done in a separate issue. |
Avoid some possible exceptions from find_element().
Rename $ScriptAlias to $LoginPage, because seems more sensible
The is_displayed() test of CustomerPreferences.t can stay at TODO for now. The elements are enabled, just not visible on the screen. |
…avbar Issue #693 selenium customer navbar
Accessing to customer.pl?Action=CustomerPreferences return inconvenience display
The text was updated successfully, but these errors were encountered: