-
Bug
-
Resolution: Fixed
-
Low
-
Severity 3 - Minor
-
Summary
When you're configuring the project Widget (Project settings > Widget) one of the settings options is to "Show all request types in the widget", which gives us the impression that when we open the widget in the web page its in all the request types will be shown without the need to type anything for them to show up, however when the open the widget it doesn't show all the request types available for the selected project, just the ones that match the seach.
Steps to Reproduce
- Create a Widget in the project
- Copy its code and save on an html file
- Open this html file and type some word and press Enter for the widget to open
Expected Results
When the widget opens all the request types would be shown as the "Show all request types in the widget" setting implies.
Actual Results
Only one or a few request types are shown, not all of them.
Workaround
None.
- relates to
-
JSDCLOUD-5974 Browse request type functionality for JSD widget
- Gathering Interest
[JSDCLOUD-5721] "Show all request types in the widget" option doesn't actually show all request types in the widget
Hi all, thanks for the feedback! We have corrected the wording the setting to make this more clear. We do understand the requirement for the ability to browse request types on the widget, but rather than tracking it via this bug ticket I have created a suggestion for it (https://jira.atlassian.com/browse/JSDCLOUD-5974). It will be great to have the discussion over on the suggestion 
In the mean time I will close off this bug.
- Vincent
I will third Joanne and Michal. This feature is useless without giving all support options.
Yep.. we liked the idea of it but the implementation was not what we expected nor desired. It seems like clicking the service desk widget should pop out to show all types(and maybe even a hyperlink to a linked confluence knowledge base ).
I agree with Joanne, widget without this function is useless for my organization.
That will not help. The users don't know what kind of request they can create, the options need to be shown.
Thanks all for your feedback - you're completely right, this setting is misleading. There was never an intention to "show all" request types, but rather to "allow searching" request types. We're rewording this setting, which will hopefully make it clearer.
Hi Vincent,
Surely it's harder to make this only show certain types by searching, the first thing it should do is show all types by default and then filter based on a search? Wouldn't that of taken a similar amount of time to fix than updating the text?