Writing History shows in Other column

I’ve read other topics but none with a solution.

I originally created a folder outside of manuscript. I started writing in it, and then I saw my writing history was in Other column and realized the folder was outside of manuscript at that point. I dragged back in.

The words stayed in the other column. Since then, anything I write in there stays in the other column.

Is there a way to reindex the word count or update it, so it keeps the dates but just moves the writing history to the right column?

I’m not using session targets, and don’t want to, but I use writing history to track my writing.

You can see in the images attached, for June 17, 1,005 words is in other, but I wrote in Chapter 8 which is under Manuscript.

I just need the numbers right, so some way to manually correct the counts or re-index it somehow.

Thanks!
Manuscript structure.png
writinghistory.png

The trigger for words being added to Draft rather than Other in Writing History is not just whether they are in the Draft folder or not, but also if they are checked as being included in the Compile. Are the documents that you moved included in the Compile? You can check in the Metadata tab of the Inspector. If you check a document as being included in the Compile and then type you should see the count added to Draft, but it won’t change any previous days in the history.

Thanks. Chapter 8 is not in the compile. I can do that going forward, but I think from a software perspective, that the analytics should be accurate.

I think it should be as simple as changing the association for the database field to the right category, depending on how you’ve coded it, upon moving folders scenes (keeping the day total as it is, but just updating the stats tables for it to associate to where it currently is). This allows for greater flexibility and accounts for when someone might right outside of drafts but decides to bring back in to drafts.

Then add one more condition to it instead of just the two, look at where it currently is, which should be the first check, and then other conditions after that.

I’m more about the accurate statistics, otherwise with my background in software, I’d call that a bug. :slight_smile: