Scenario where an Existing (registered) client's ticket CAN get stuck when not logged in

[turner2f]

Just discovered an odd phenomena.

 

SCENARIO 1 : An existing (registered) client sends a ticket from outside of the Blesta System, the ticket gets allocated to their account ( This is GOOD )

SCENARIO 2 :  An existing (registered) client LOGS IN, and then sends a ticket from within the Blesta System, the ticket gets allocated to their account   ( This is GOOD )

SCENARIO 3 :  An existing (registered) client DOES NOT LOG IN, and then sends a ticket from within the Blesta System, the ticket DOES NOT get allocated to their account, hence the ticket is posted and stuck outside of their account   ( NOT SO GOOD )

====================
 

SUGGESTED RESOLUTIONS

1) - Can you please make it so Blesta will recognize the email address even if the person is not logged in, and posts from within the Blesta system ?

NOTE : It should be able to successfully function in the same way as when a person is posting outside the system ( from like yahoo or gmail ).

 

2) - Can you please make it so that we can MANUALLY allocate the ticket so that it is not posted and stuck outside of their account ?

 

Look forward to your reply.

 

Thanks in advance

[Paul]

23 hours ago, turner2f said:

1) - Can you please make it so Blesta will recognize the email address even if the person is not logged in, and posts from within the Blesta system ?

No. This is a potential security risk. I could open a ticket spoofed as anyone and possibly trick staff into making changes to their account. This is also a possibility with email tickets, but companies are not required to accept tickets via email.. and if they don't, only authenticated users can open tickets.

23 hours ago, turner2f said:

2) - Can you please make it so that we can MANUALLY allocate the ticket so that it is not posted and stuck outside of their account ?

Yes, this is planned.

[turner2f]

Thanks for the reply.

Makes sense since in order to send from outside the Blesta system the person would have to know the login credentials of the email account it is being sent from .

[turner2f]

 

Quote

" Can you please make it so that we can MANUALLY allocate the ticket so that it is not posted and stuck outside of their account ? "

 

Is there a URL or a "Feature" ticket that we can follow concerning the implementation of #2 ?

[evolvewh]

1 hour ago, turner2f said:

 

 

Is there a URL or a "Feature" ticket that we can follow concerning the implementation of #2 ?

Look at dev.blesta.com and if it's there, it's publicly available to track. If not, they don't want to the public to see it yet. FYI, there is a reason they put out information at dev.blesta.com, docs,blesta.com etc. I do the same thing and go look around there to see if certain features or explanations exist too. It's really useful and I know the Blesta team spends a lot of time to create these resources for all of us.

[turner2f]

Thanks.

I did not want to take a chance of missing it and posting it twice.

 

 

[evolvewh]

1 hour ago, turner2f said:

Thanks.

I did not want to take a chance of missing it and posting it twice.

 

 

Just use the search feature at dev.blesta.com and it's really effective. If it doesn't turn up a result, it's probably not publicly announced yet.

[Paul]

I couldn't find it, so I created CORE-2347.