I will start off by stating I am using mainly the 1.10RC.3 but I am testing with several versions and seem to be having the issue across all of them. Also, I have been unsuccessful in locating anything similar to my issue.I have created a basic custom form (see Image 1) to use for a specific help topic. In the help topic (see Image 2) I changed to use the new form and unchecked the normal Summary list items (Issue Summary, Issue Details, Priority Level) since they are not needed (all information required is included on the form).(Image 1)blank(Image 2)blankNow once I create a ticket using this new form it ends up creating a ticket w/o a Subject (see Image 3). I attempted to fix this by creating an 'Issue Summary' in the custom form with the same settings/info as the Issue Summary in the included Summary form but this still does not work. (Image 3)blankLong story short, is there a way I can force a specific Subject based upon the Help Topic w/o needing to include the Issue Summary in the form as well?osTicket Version v1.10-rc.3 (907ec36)Web Server Software ApacheMySQL Version 5.1.73PHP Version 5.4.45

screenshot.057.png

screenshot.058.png

screenshot.060.png

Just to clarify, this is the update I made to the custom form to attempt to force a Subject, but it did not work.

screenshot.061.png

To add to this issue I have found that tickets opened that do not include the Summary Form (included with osTicket) and its fields set to 'Require entry to close a thread' cannot be changed to Resolved or Closed unless you remove the requirement (see image).

screenshot.062.png

It is my understanding that Issue Summary (email subject) and Issue Details (email body) are required fields.  You should not be able to disable them.  Moving them to another form doesn't count as having them active."tickets opened that do not include the Summary Form (included with

osTicket) and its fields set to 'Require entry to close a thread' cannot

be changed to Resolved or Closed unless you remove the requirement (see

image)."Precisely.  Tickets that have ANY field with that ticked cannot be closed unless the field is populated.  This is intentional.

Well so far I have gotten around this by enabling the Issue Summary and making it required but I am leaving out Issue Details and Priority (and disabling the requirement to have them filled to close a ticket - though the fields are still required to be filled to create a ticket when the fields are present).The issue this leaves now is the ability to populate the Issue Summary based upon a Help Topic. Since custom forms are generally used for specific issues being able to have that topic create a Summary as a default for that topic would make it easier for both side (user and agent) when creating a ticket.In the example I am using above its a form requesting access to certain locked doors with a swipe card. Since the form only request specific information and everyone knows its for a door access request, having to create a Summary seems redundant especially if it cannot be created based upon the form or help topic selected.So to reiterate the question: Is there a way to force an Issue Summary to be auto-filled based upon a selected Help Topic or Custom Form?

Q: Is there a way to force an Issue Summary

to be auto-filled based upon a selected Help Topic or Custom Form?A: No.  This is not a feature in osTicket at this time.

Can it be? Where would the feature request go to add this type of functionality?

https://github.com/osTicket/osTicket/issues/newfor the title use: feature name

Write a Reply...