Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Why most hosting providers support ticket systems allow text only (no formatting)?

Post

Why most hosting providers support ticket systems allow text only (no formatting)? [closed]

+0
−8

Closed as off topic by Alexei‭ on May 15, 2021 at 18:48

This question is not within the scope of Software Development.

This question was closed; new answers can no longer be added. Users with the reopen privilege may vote to reopen this question if it has been improved or closed incorrectly.

Through the years I have "tasted" several website hosting companies; none of them had Markdown available in their support-ticket-systems (if all any formatting method available).

Why is it? What's so problematic for hosting providers to let their customers comfortably format their support tickets (which is extremely important in cases of complicated problems and can save time and energy for both sides)?

Is there some information security reason for such a support-ticket-system development paradigm?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (5 comments)
General comments
hkotsubo‭ wrote over 3 years ago

From my experience, the main issue in any ticket system is when users can't explain their problem with enough details (and we need to contact them to get those details). Markdown, as a markup language, (with formatting purposes only), wouldn't help to solve this problem - because it's a communication issue, not a formatting/design one. Perhaps you're trying to solve the wrong problem...

Alexei‭ wrote over 3 years ago

I will try to migrate this to the newly created Power Users community, but I will have to clarify if it is on-topic there.

deleted user wrote over 3 years ago

@hkotsubo‭ I don't think I am --- a user not providing enough details is another issue which can be solved by creating good forms ; and yet, to prevent cognitive biases in processing the data --- I do believe formatting can help.

deleted user wrote over 3 years ago

Thanks @Alexei.

Alexei‭ wrote over 3 years ago

This question is being referenced by a Power Users meta post.