Marissa Zugec, pmp

Our team would also like to be able to report in Guide with more flexibility on what criteria and content to show, such as pulling a view/list of articles by creator/editor, dates, including tags, etc

I want to vocalize again for this request that we are in need of a solution for agents submitting tickets, This need has not changed, and we continue to see others on the request that are in the same predicament as our company. What are the plans for the future development? 

Checking to see if this has been promoted for development yet? if not, will this be added for consideration in the near future? 

Agree with Scott Patterson's comment, this was worded well, in that we need the same functions: 

Another reason for us is with automation of tickets flowing between two Zendesk instances with sharing turned on, making sure the tickets are automatically shared with the right fields and the right details entered. Especially when fields can be set as 'required' by end users when submitting a form, but not required when an agent manually creates a ticket. This makes our automation and sharing of fields not have all the necessary details filled in for agents that create them manually.

It's also not great for consistency to tell some users to submit forms some way, and other users to submit in another way, and having to give out different URLs depending on who we might be talking to. Having things simple and consistent for any users (or able to be turned on for any users) would work much better.

Sending in my vote on this- my use case is the same as all others mentioned- we need to allow internal staff to submit tickets - viewed as the end user.