{"action":"created","issue":{"url":"https://api.github.com/repos/osTicket/osTicket-1.8/issues/2061","labels_url":"https://api.github.com/repos/osTicket/osTicket-1.8/issues/2061/labels{/name}","comments_url":"https://api.github.com/repos/osTicket/osTicket-1.8/issues/2061/comments","events_url":"https://api.github.com/repos/osTicket/osTicket-1.8/issues/2061/events","html_url":"https://github.com/osTicket/osTicket-1.8/issues/2061","id":76347110,"number":2061,"title":"Custom field needs to be populated for closure","user":{"login":"hawkhead99","id":1635142,"avatar_url":"https://avatars.githubusercontent.com/u/1635142?v=3","gravatar_id":"","url":"https://api.github.com/users/hawkhead99","html_url":"https://github.com/hawkhead99","followers_url":"https://api.github.com/users/hawkhead99/followers","following_url":"https://api.github.com/users/hawkhead99/following{/other_user}","gists_url":"https://api.github.com/users/hawkhead99/gists{/gist_id}","starred_url":"https://api.github.com/users/hawkhead99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hawkhead99/subscriptions","organizations_url":"https://api.github.com/users/hawkhead99/orgs","repos_url":"https://api.github.com/users/hawkhead99/repos","events_url":"https://api.github.com/users/hawkhead99/events{/privacy}","received_events_url":"https://api.github.com/users/hawkhead99/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/osTicket/osTicket-1.8/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/osTicket/osTicket-1.8/labels/ux","name":"ux","color":"006b75"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-05-14T12:40:49Z","updated_at":"2015-05-14T16:33:57Z","closed_at":null,"body":"This is more of a request then an issue, but - \r\nOn the 1.10 release notes - \"Fields can be marked for required for closed. Therefore they can inhibit closure of a ticket without a valid value.\"\r\n\r\nWhat if when you go to close the ticket - an in-line popup displays giving the user the opportunity to populate a required field (so they don't have to go into the edit screen).  I am wondering how practical it would be to use this new feature for setting a \"resolution\" before closure, but I don't want users to have to go to the edit screen every time before closing a ticket\r\n\r\nIf that is not really what the custom field is designed for, I can work on a pull request that includes setting a resolution capability if you feel that would be a good addition?  I have it as a mod for 1.9.7 already (http://osticket.com/forum/discussion/85479/add-resolution-to-ticket-upon-closing) "},"comment":{"url":"https://api.github.com/repos/osTicket/osTicket-1.8/issues/comments/102095479","html_url":"https://github.com/osTicket/osTicket-1.8/issues/2061#issuecomment-102095479","issue_url":"https://api.github.com/repos/osTicket/osTicket-1.8/issues/2061","id":102095479,"user":{"login":"hawkhead99","id":1635142,"avatar_url":"https://avatars.githubusercontent.com/u/1635142?v=3","gravatar_id":"","url":"https://api.github.com/users/hawkhead99","html_url":"https://github.com/hawkhead99","followers_url":"https://api.github.com/users/hawkhead99/followers","following_url":"https://api.github.com/users/hawkhead99/following{/other_user}","gists_url":"https://api.github.com/users/hawkhead99/gists{/gist_id}","starred_url":"https://api.github.com/users/hawkhead99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hawkhead99/subscriptions","organizations_url":"https://api.github.com/users/hawkhead99/orgs","repos_url":"https://api.github.com/users/hawkhead99/repos","events_url":"https://api.github.com/users/hawkhead99/events{/privacy}","received_events_url":"https://api.github.com/users/hawkhead99/received_events","type":"User","site_admin":false},"created_at":"2015-05-14T16:33:57Z","updated_at":"2015-05-14T16:33:57Z","body":"@greezybacon I agree, that could work well! :)  The only thing to consider is what would it do if you are doing a mass-close instead?  \r\n\r\nSo, with that solution still in mind, I assume there would be an array of ticket id's for links to a popup edit for each ticket that is being requested to be closed and is missing a required field?  That might still be a little more time consuming for the user, but would be faster then having to re-open each ticket with the problem.\r\n"}}