Help !

I agree with Phil that it's usually better to track with variables on a custom menu. This post about custom menus describes using T/F variables to track what scenes are completed. It also has a demo file. It controls the Player's Next button, but the same programming could be use to control a custom button or automatic advancing.

A few other things to know about Storyline:

An object with a Visited state automatically changes to that state when it is clicked. You don't need any triggers to change to Visited. (For more info, see the primer about built-in states.) For more control, it's sometimes better to use a custom "Done" state, and change to that state with a trigger.

Triggers run in order. However, any triggers that appear after a "jump to" trigger won't run, because the user has already left the slide. Thus, your "change to Visited" triggers that appear after the "jump to slide" triggers don't run. The objects changed to Visited because that's built-in functionality (as mentioned above). 

A "when the timeline starts on this slide" trigger runs every time the user visits the slide. That's true even if the Slide Properties are "Resume saved state." So that kind of trigger needs one or more conditions if you only want it to run in some situations.