We should have a way of referring to posts even if they are moved between forums, projects, etc. This could be a global redirect service (e.g. http://sf.net/go/b64446c6). The link would be tied to the (immutable) ObjectId of the underlying post/thread, not any particular path to get to it.
Where would we use this?
This is a motorola request in case they have posts that move around (between threads, forums, etc).
On Jun 27, 2011, at 1:36 PM, Dave Brondsema wrote:
====
This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
I am not sure we should do this. Our core linking functionality is with artifact references. We'd have to build up a lot of functionality around guids to make it work well (markdown syntax for it, the redirect URL, a global search). I explained to Motorola what we do have, and that threads are already keyed by a constant id, so changing thread titles won't break thread links. (threads don't move between forums or projects). We don't want to simply mimic whatever teamforge has.
We have the artifact syntax, but posts are part of a project and we currently don't have plans to support moving them between projects, though it is should be supported to have backlinks between posts on different projects. (And this is possible if you use artifact links now.)