Closed jacobvanetten closed 1 year ago
What happens is that if the users write in the chat, we have all that information, in the case of creating the ticket from this interface there is information that we cannot have by default.
Yes, for now check the form, it has been updated according to your suggestions.
Thank you very much @jacobvanetten
But right now, most questions will only be answered several hours later, due to the time zone difference. Also, if it does not generate much input now, I think that it is better to take out and use this space to place an icon that leads to the ticketing system, removing the current large button. This would make the ticketing system available from anywhere in the software.
On Wed, Mar 8, 2023 at 4:13 PM Brandon Madriz @.***> wrote:
What happens is that if the users write in the chat, we have all that information, in the case of creating the ticket from this interface there is information that we cannot have by default.
Yes, for now check the form, it has been updated according to your suggestions.
Thank you very much @jacobvanetten https://github.com/jacobvanetten
— Reply to this email directly, view it on GitHub https://github.com/BioversityCostaRica/py3ClimMob/issues/256#issuecomment-1460311746, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGF5FOPOHZIRHKM7YC56L3W3COYLANCNFSM6AAAAAAVTSJX2Q . You are receiving this because you were mentioned.Message ID: @.***>
https://support.climmob.net/en/support/tickets/new
This is not yet fully integrated into ClimMob, because it asks information that is already available in ClimMob. We should avoid asking for information that users don't know.
I think for now, we can ask the following only:
ClimMob user email ClimMob project name Subject Description of your issue
These ones, we should suppress: Requester: strange way to put it, with user email it should be enough ClimMob site: users will not know this. Better to ask the project name ClimMob user: people may not know their user name, perhaps better to ask their email for now? This is to be resolved in the future by integration with ClimMob