Yes, I think you’re describing the problem well.
@christo I think we need to consider a few different combinations here:
Given we’re merging topic A (a single post) into topic B, there are the following cases to consider
-
- topic A’s post in newer than the last post of topic B
- a. maintain chronology is selected
- b. maintain chronology is not selected
-
- topic A’s post is older than the last post of topic B
- c. maintain chronology is selected
- d. maintain chronology is not selected
I think the expected behavior is that the topic is bumped in all cases, except for 2(c).
In every case but 2(c), the post from topic A would be appended at the end of topic B, so I think the merge should cause the bump date to be set based on when the merge occurred.
I’m not exactly sure what I’d expect to happen though in the case of 2(d), if the admin later does “reset bump date”. I think it should probably update the bump date to be the date of the most recently created post in the topic (e.g. the penultimate post).
@martin you and I have been thinking about bump date logic in other scenarios – does the above make sense to you?