Expand Progress Automation to Include “Want to Play”

📋 Summary

Allow the Game Progress Automation rule (“set to In Progress when…”) to also trigger for games marked Want to Play, not just Unplayed. Provide a configurable list of statuses that qualify for auto-transition to In Progress.

❗ Problem

Today, auto-progress only promotes Unplayed → In Progress. Games set to Want to Play are ignored, forcing manual updates when you start them—especially frustrating for users who curate “Want to Play” backlogs.

🎯 Proposal

• Add a configurable setting in Game Progress Automation to choose which statuses (e.g., Unplayed, Want to Play, custom statuses) should auto-transition to In Progress when the chosen trigger occurs (e.g., first launch, playtime > 0).

• Respect libraries where “Want to Play” was removed/renamed by letting users pick from available statuses, not a hardcoded list.

🛠️ Example

• In Settings → Game Progress Automation:

  • Trigger: “Set to In Progress when playtime > 0”

  • Eligible statuses: [✓ Unplayed, ✓ Want to Play, ☐ Backlog]

  • Result: A “Want to Play” game flips to In Progress on first play—no manual update needed.

📦 Benefits

• Reduces manual progress updates for backlog workflows.

• Works with customized status vocabularies.

• Keeps progress tracking consistent across how users actually plan and start games.