-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
2
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
We would like to be able to customise the service desk customer portal so that, for example, all users would first be required to search for their issue (much like on support.atlassian.com) and only then when they don't find a solution, be able to create a new ticket.
I would suggest the summary is filled in with what they have searched from.
I understand this functionality is kind of there, but
a) It would be better to search first, then create ticket, instead of going down a path to create a ticket to then see matching KB articles only to return to creating the ticket
b) it doesn't do partial word matching, so if their problem is, for example, keyboard not working, then we only get a match when "keyboard" is typed, but really we should see it when "key" is matched.
- is related to
-
- Closed
- relates to
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[JSDSERVER-876] Ability to customise the Customer Portal
| Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3012314 ] | New: JAC Suggestion Workflow 3 [ 3647337 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664309 ] | New: JAC Suggestion Workflow [ 3012314 ] |
| Support reference count | New: 2 |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324438 ] | New: Confluence Workflow - Public Facing v4 [ 2664309 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JSD Suggestion Workflow [ 2053497 ] | New: JSD Suggestion Workflow - TEMP [ 2324438 ] |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048619 ] | New: JSD Suggestion Workflow [ 2053497 ] |
| Workflow | Original: JSD Suggestion Workflow [ 1280352 ] | New: JSD Suggestion Workflow - TEMP [ 2048619 ] |
| Description |
Original:
We would like to be able to customise the service desk customer portal so that, for example, all users would first be required to search for their issue (much like on support.atlassian.com) and only then when they don't find a solution, be able to create a new ticket.
I would suggest the summary is filled in with what they have searched from. I understand this functionality is kind of there, but a) It would be better to search first, then create ticket, instead of going down a path to create a ticket to then see matching KB articles only to return to creating the ticket b) it doesn't do partial word matching, so if their problem is, for example, keyboard not working, then we only get a match when "keyboard" is typed, but really we should see it when "key" is matched. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-876]. {panel} We would like to be able to customise the service desk customer portal so that, for example, all users would first be required to search for their issue (much like on support.atlassian.com) and only then when they don't find a solution, be able to create a new ticket. I would suggest the summary is filled in with what they have searched from. I understand this functionality is kind of there, but a) It would be better to search first, then create ticket, instead of going down a path to create a ticket to then see matching KB articles only to return to creating the ticket b) it doesn't do partial word matching, so if their problem is, for example, keyboard not working, then we only get a match when "keyboard" is typed, but really we should see it when "key" is matched. |