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 Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Archive to mark as "resolved", without locking the comment?

Parent

Archive to mark as "resolved", without locking the comment?

+2
−0

I've recently come across a situation where I thought archiving the comment thread was appropriate: A user suggested an improvement in the thread, and that improvement was then implemented (by me).

Then I realized that archiving actually also locks the thread and prevents anyone from responding further, which is a problem since if there's any further feedback, they would have to make a new thread cross-referencing the old one.

Could the Archive tool be made to not also lock the thread? We already have a lock tool; if I wanted to archive and lock then I would just use both tools.

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

Why not just delete the thread? (3 comments)
Post
+2
−0

I think what you might be looking for is "resolved" -- you want to indicate that a thread has been handled, but you want to leave the door open for feedback.

I would expect a hypothetical "resolve" option to do the following:

  • Hide the thread by default, as with archived threads.
  • Show "resolved" in its title when the thread is shown under a post.
  • Add a "resolved by $user at $timestamp" comment into the thread, so that any post-resolution comments are clear in their timing.

Would this do what you're looking for?

Just as you can restore an archived or deleted thread, I'd expect resolving a thread to be reversible.

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

1 comment thread

Visual difference between comments and system messages (3 comments)
Visual difference between comments and system messages

The «resolved by user» comment should be visually distinct from normal comments, to clearly mark the difference between an actual comment, and a system message. Something similar to how Github/GitLab handle replies and system messages in PRs and issues, should work.

Monica Cellio‭ wrote over 1 year ago

I was thinking of "resolved by $user" being in the same place as "Andreas wrote $time ago" is in this thread -- meta-information provided by the system, as distinct from the actual comment text.

As long as the message type information is preserved for easy redesigns in the future. I do think that design risks being confusing, though. It'll look like a message header with a missing message.