Open for Voting

Prevent custom Resolved status from overriding checklist requirements

How it works now

If you use the custom Resolved status to auto-close tickets after X amount of days, it will close the ticket even if you have unmet required checklist items. In this way you can close a ticket without ever completing all the "Required" items.

Proposed changes

Write code that does not allow use of custom status types that auto-close tickets unless all checklist requirements are met.

Business Case

This seems like common sense to me, but when I opened a ticket I was told it was working as intended, and was not a bug.

  • With checklist items, you can make the items required or not required individually. So in your example, the remaining steps would just be marked as not required before completion.

  • I could see this as working as intended if you have a SLA that says you will auto-close or auto-resolve tickets after so long if you are waiting on customer response that way you don't keep tickets open forever due to a customer not responding.  But I see your point in that you don't want the ticket waiting on a tech to close without all the steps being met.  With this kind of setup, how would you handle something that requires the remaining steps to be jumped.  say it was decided to replace the equipment making the remaining steps not necessary? 

    Just asking to learn possible ways of handling this before my company updates to the newer version that has the checklists.