I think whats good for email should be good for api. (ie no.  both email
and api should respect this rule)

Couldn't staff add a user first?  (or can you make it throw and error when
staff tries to open a ticket for a non-existant user)



On Tue, Mar 25, 2014 at 5:08 PM, Jared Hancock <notifications@github.com>wrote:

> In include/class.ticket.php:
>
> > @@ -2281,10 +2278,18 @@ function create($vars, &$errors, $origin, $autorespond=true, $alertstaff=true) {
> >                          || !($user=User::fromVars($user_form->getClean())))
> >                      $errors['user'] = 'Incomplete client information';
> >              }
> > +
> > +            // Reject emails if not from registered clients (if configured)
> > +            if (!$cfg->acceptUnregisteredEmail() && !$user->getAccount()) {
>
> Should this required the source to be email (which would allow bypass of
> this feature via api). As is, enabling this option would forbid staff
> members to create tickets on behalf of users without registered accounts
> via the staff interface.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/osTicket/osTicket-1.8/pull/725/files#r10953689>
> .
>