Requesters are unable to mark tickets as solved in the Help Center

Have more questions? Submit a request

25 Comments

  • Mallory Welch
    Comment actions Permalink

    The code above only added an extra attachment field.

    0
  • Jessie Schutz
    Comment actions Permalink

    Hi Mallory!

    I have to ask, just to be sure - are you absolutely sure that the criteria met? The ticket type is Question, Task, or Incident, and the ticket is assigned?

    In the screenshot I can see the assignee, so that's probably fine. I see a Web Job Type set as Question, but I can't tell from here whether that's a custom field, or if you used custom code to to change the name of that field.

    If it's the former, you'll need to make sure that the system ticket type field is set appropriately as well.

    If it's the latter, I suppose it's possible that the change is preventing the "Solve" option from showing. I'm not super skilled with coding, so this is a sort-of-educated guess.

    If you wanted to post some screenshots of the relevant bits of code, that might help us parse out what's going wrong. We have a couple Moderators who are great at this.

    0
  • Michael Potts
    Comment actions Permalink

    How can we change the criteria so that Problem is able to be marked as solved.  Our Customer tickets are always assigned to an agent or the admin on the ZD account.  50% of our tickets are Problem classified and we have Customers who would like to mark them solved, it really doesn't make sense.

    Please provide a way to allow this to work.

    Thanks so much.

    - Michael

    2
  • Jessie Schutz
    Comment actions Permalink

    Hey Michael!

    To the best of my knowledge it's not possible to do this, even with custom code, but I'll check to see if I can find out some kind of workaround for you.

    Can you give some additional information about why you're marking these tickets as Problems?

    0
  • Joerg Klaas
    Comment actions Permalink

    This behaviour seems to be really a like a piece of strange functionality definition.

    Why should a customer not be able to close/solve it's own service request, if he wants to do so?Regardless of what type, status, assigned or not....

    This doesn't sound "End-User" friendly and additionally it increases unneccessary agent overhead without any advantages...

    5
  • jmitchell
    Comment actions Permalink

    I must say, I agree fully with Joerg.

    I've no way of rationalising the exclusion of the "problem" type with our customers. Partially because I'm not sure of the rationale for this myself. Could you please explain why you engineered the option this way?

    Thanks

    Jason

    2
  • Steven Bridle
    Comment actions Permalink

    This code appears to no longer function. 

     

    We receive the following error message: 

    "Upload does not exist" 

     

    Any thoughts? 

     

     

    2
  • Nicole - Community Manager
    Comment actions Permalink

    Hey Steven - 

    I've asked some folks to take a look at the code and let us know what's up. Standby. 

    0
  • Saajan Shah
    Comment actions Permalink

    Hey Steven,

    I have created a ticket on the issue, so we can look into this further, for your account specifically.

    Regards,

    Saajan.

    0
  • Chris Avila
    Comment actions Permalink

    I just tried the code and having the same issue as Steven. I'm not sure what's going on here.

     

    1
  • Catherine Michalak
    Comment actions Permalink

    Hello,

    Is there a reason for this change? What problem is this answering? I'm struggling to clarify the reasoning for this change to our end-users.

    They want to be able to do so and frankly speaking this is quite useful as we don't want our agents spending time on closing tickets or answering queries that are no longer valid.

    Thanks

    1
  • Nicole - Community Manager
    Comment actions Permalink

    Hi Catherine - 

    What change are you referring to? The above troubleshoots what to do if the requesters are having trouble marking as solved. 

    -1
  • Catherine Michalak
    Comment actions Permalink

    Hi Nicole,

    I was under the impression that all requesters could mark their tickets as solved and that not being able to do so unless certain conditions were fulfilled is a new thing.

    1
  • Nicole - Community Manager
    Comment actions Permalink

    Hi Catherine - I answered you on the other thread as well, but for anyone else following, these are not new conditions. 

    -1
  • Alexia Wolfhagen
    Comment actions Permalink

    ehm... what? Why remove the option for customers to mark their request as solved if it's a problem? This is not logic!?

    1
  • Jessie Schutz
    Comment actions Permalink

    Hi Alexia!

    Problem tickets are meant to be used in tandem with Incident tickets to track and resolve issues being experienced by many users, or other similar use cases. If a Problem ticket has many Incidents associated with it, and a customer were to solve that Problem ticket, it would solve all the Incidents as well, and whatever comment the customer left on the ticket would be added to all the Incident tickets as well. This would create a huge problem for teams that are using Problem tickets to track problems that impact many customers.

    One way that you can work around this would be to create a brand new Problem ticket with yourself (or any other agent) as the requester. Then you can add the customer's ticket as an Incident, and the customer would be able to Solve that ticket whenever they'd like.

    1
  • Alexia Wolfhagen
    Comment actions Permalink

    I can't help but wonder why you have created a ticket system that suits your need rather than the customers. 

    Why are you the ones that decide how the system is used, instead of letting your customers use it to fit their need?

    0
  • Jessie Schutz
    Comment actions Permalink

    Hey Alexia!

    I know it's frustrating when things don't work the way you expect, and I'm sorry that you're running into difficulties. We build functionality into Zendesk to address our customers' most common use cases; as much as we might want to, it's just not possible to build for every edge case out there. The Problem/Incident relationship works the way it does because this is how the majority of customers use this type functionality.

    The bright side of this particular situation is that you can circumvent the issue with a small workflow change, as I mentioned in my previous comment. I hope that you're able to make it work for you!

    0
  • Stassa Miller
    Comment actions Permalink

    Please add me to the response with the updated code for our organization as well,  please.  Our customers would also like to be able to close their own tickets.  I do understand the problem status and how it affects all other tickets associated with it.   

    0
  • Brett - Community Manager
    Comment actions Permalink

    Hey Stassa,

    Can you clarify what you're looking for on your end? Are you not seeing this option for users even when the appropriate conditions are met listed above?

    Thanks in advance!

    1
  • Stassa Miller
    Comment actions Permalink

    Correct, And we also want the client to be able to mark their tickets as solved regardless if the agent has responded or not.   I get the Problem status and am okay with that.  Otherwise, The client shoudl be able to close their own tickets whenever they like. 

    0
  • Brett - Community Manager
    Comment actions Permalink

    Hey Stassa,

    I did some testing in my own account and it looks like as an end-user I'm able to solve my ticket regardless of who commented last. Screenshot below: 

    If you're not seeing the option to mark as solved and you're using the default Copenhagen theme then most likely someone removed the following code:

    <div class="comment-form-controls">
    {{checkbox 'mark_as_solved'}}

    {{#if request.can_be_marked_as_solved}}
    <button type="button" class="button-large button-secondary mark-as-solved"
    data-solve-translation="{{t 'mark_as_solved'}}"
    data-solve-and-submit-translation="{{t 'mark_as_solved_and_submit'}}">
    {{t 'mark_as_solved'}}
    </button>
    {{/if}}

    <span class="request-submit-comment {{#validate 'body'}}shown{{/validate}}">
    {{input type='submit'}}
    </span>
    </div>

    Here's a screenshot of what the code looks like in my Guide theme:

    I hope this points you in the right direction!

    1
  • Andre Ribeiro Queiroz
    Comment actions Permalink

    Hi there,

    my team made some tests here and this sentence is not accurate:

    """ The last comment must be made by an agent. """

    We created a ticket using an end-user profile. Even without any comment from the agent, the button appeared normally

    0
  • Brett - Community Manager
    Comment actions Permalink

    Thanks for the update Andre!

    I'm going to flag this article to be updated. I believe the only requirement is that the ticket is assigned to an agent in this case.

    Cheers!

    0
  • Stassa Miller
    Comment actions Permalink

    O went ahead and opened up a ticket, the code is already there in the Copenhagen theme identical to what is provided and still on marked as solved and submit button.   Thanks for your help

    0

Please sign in to leave a comment.

Powered by Zendesk