2024-01-29
| ||
06:09 | • Closed ticket [500a94b9]: link checkins and relevant tickets plus 4 other changes ... (artifact: 00df6f0a user: stephan) | |
05:50 | • Wiki page "To Do List" ... (artifact: 7f3dab46 user: stephan) | |
2023-03-13
| ||
13:03 | • Ticket [2cc5acf3] Split forum thread into a new thread and link the two threads status still Open with 7 other changes ... (artifact: 82962a44 user: stephan) | |
13:01 | • New ticket [2cc5acf3]. ... (artifact: be8198ee user: stephan) | |
Ticket Hash: | 2cc5acf3ba27e3e46252dbdcb63438152324da34 | |||
Title: | Split forum thread into a new thread and link the two threads | |||
Status: | Open | Type: | Feature_Request | |
Severity: | Minor | Priority: | Immediate | |
Subsystem: | Resolution: | Open | ||
Last Modified: | 2023-03-13 13:03:43 | |||
Version Found In: | 2.22 | |||
User Comments: | ||||
stephan added on 2023-03-13 13:01:41:
As discussed in forum:068eff0298... The ability to split a forum thread into a new top-level thread, to avoid threadjacking the first thread, would be useful from time to time. In essence this just means adding a "reply to new thread" option which leaves out the I-card of the response and requires a new thread title. Before implementing this, however, we need a mechanism to provide a formal two-way link between the new post and the split-from post so that the new thread can be automatically linked back to the origin and the older thread can have a "new thread started..." link where the split-off response would have been. That's a feature we had been discussing idly for several weeks prior to the above-linked post, but which has several potential implementations and we need to get that part "right" before committing to it because we'll be stuck with it after that. One proposed approach is demonstrated here: tag.tagname = linkto-TARGET_UUID, tagxref.rid = RID of the link's LHS Artifacts are from althttpd because it has forum posts and checkins in the same repo:
Add 2 links from the post to separate checkins:
Query FROM → TO:
Query TO ← FROM:
stephan added on 2023-03-13 13:03:43: Confirmed bug: the Contact email entered in a ticket is ignored if manually entered and a default exists for the user. e.g. a user's account has email address |