You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless I didn't find the option, when exporting a conversation, it doesn't export the threads in it.
I get a special cursor as for a link, but no link.
It would be great to also export the threads, with internal link.
Or even, as intermediate option, the thread it self as conversation.
Why would you like to do it?
Right now, when exporting a conversation in html, I don't get the threads in it and found no way to export the theads one by one.
How would you like to achieve it?
When exporting the chat, have an option "include threads" we can choose or not.
If chosen, export the threads with an html file by thread, and each thread's html file would be linked in the main one.
Have you considered any alternatives?
I google it and tried to explore the options, but I am not an expert to use a complex solution, just an end-user.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Your use case
What would you like to do?
Unless I didn't find the option, when exporting a conversation, it doesn't export the threads in it.
I get a special cursor as for a link, but no link.
It would be great to also export the threads, with internal link.
Or even, as intermediate option, the thread it self as conversation.
Why would you like to do it?
Right now, when exporting a conversation in html, I don't get the threads in it and found no way to export the theads one by one.
How would you like to achieve it?
When exporting the chat, have an option "include threads" we can choose or not.
If chosen, export the threads with an html file by thread, and each thread's html file would be linked in the main one.
Have you considered any alternatives?
I google it and tried to explore the options, but I am not an expert to use a complex solution, just an end-user.
Additional context
No response
The text was updated successfully, but these errors were encountered: