Ability to merge discussions
Hey everyone,
it would be a really awesome feature to be able to merge different discussions into one.
As you know, there are often different discussions about the very same topic. This does not only add noise to the forum, it can also lead to duplicate information.
Let's say someone started a new discussion about something that has already been answered before. Instead of just referencing the old discussion (with the answer) in a comment, it would be cool to press a merge button, which then opens something like a merge window.
Then I can search for the old discussion (with AJAX on the same page), select it, and in the next step, select somehow (i not sure yet how to do it) which comments I'd like to include in the merged discussion and in which order. The new discussion should then be deleted, and all the relevant content integrated into the old discussion.
The implementation needs to support moving comments from one discussion to another, and also somehow merge the body of the discussion (automatically and if the user wants also customized). You'd also need to create the merge window, which allows selecting similar discussions, and then listing all the comments from both discussions. I am not sure how much work that is, but it sounds (at least to me) like a really cool feature, that'd make Tender more unique.
Greetings, Dennis
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Kyle Neath (Git... on 26 Jan, 2009 10:27 AM
One of the feature's we've been talking about internally addresses this problem but in a slightly different way. What we have envisioned is a way to attach & forward a discussion to another one.
Once you find a duplicate issue, you'd attach the issue with more authority to it and close the issue. The user who created the duplicate issue would become a watcher (get email updates) about the authoritative issue and no further updates would be allowed on the duplicate issue.
We've got a few steps to get there (attaching discussions, locking discussions, etc) -- but I think that's the general direction we'd like to head.
Will closed this discussion on 08 Jun, 2010 03:12 AM.