Moving in RoboHelp removes version control history

Title: Please vote: RH-14536, moving topics in a TFVC-bound project loses file history

Hi all,

If you use RoboHelp with Team Foundation Version Control (TFVC), please take a minute to vote on RH-14536.

The problem: In RoboHelp 2026.09.43 with a TFVC local workspace, renaming a topic keeps its version history. Moving a topic to another folder does not. TFS records the move as a delete at the old path and a brand-new add at the new path. The new file starts with a single “add” entry and none of its earlier changesets.

How to reproduce:

1. Create a topic and check it in.
2. Move it to a different folder in RoboHelp.
3. Check in from RoboHelp.
4. Open History on the new path. You’ll see only an add, and the old path shows a plain delete.

For comparison, I tested tf rename from the command line. It records a rename, keeps the full history, and also worked when I edited the file in the same changeset. So TFVC supports what’s needed, and the loss happens in how the move is recorded.

Why it matters: Anyone who reorganizes a project, whether they move 10 topics or 1,000, quietly wipes the history of every topic they touch. That removes change tracking, blame, and the audit trail, and it can’t be recovered afterward. Large projects are the ones that most need to be reorganized, and they’re also the ones that lose the most.

Workaround: There isn’t a good one inside RoboHelp. Moving files with tf rename at the command line keeps history, but RoboHelp won’t update the links or TOC entries for you, so you’d have to fix those yourself.

What I’m asking for:

• Vote on RH-14536 (use the vote button on the issue page; you’ll need to be signed in with your Adobe ID).
• If you use TFVC, add a comment with your RoboHelp version and whether you see the same behavior. Confirmations on other versions help Adobe prioritize.
• If you use Git or another system, tell us whether moves keep history for you, so we can see whether this is TFVC-specific.

Thanks!
Eric