In our instance one of the other admins created a prompted journal entry report which was useful in learning the syntax needed. (we just added all the useful looking journal fields [like Scope, Change Type, etc.] as prompts)
For example, in Benetta's case, with our prompted report I would have started with project ID = xxxxxxxxx, which would pull up all the entries in one project.
By scrolling down the resulting report, I can see that the project status changes are listed under a blank scope, so going back to the prompts list, I can add a filter for Scope is blank.
I can see that the status changes are also listed as an "edit," so that goes under my Change Type prompt. And so on.
By starting with one filter in the prompt and using additional prompts to narrow down the list, it's a really good way of avoiding building it in the filter section of a report and then having to go back and re-edit, which is quite time consuming when you're learning a new report type. It also gives us a level playing field (i.e. classroom) where we're all learning the same thing. And it allows us to use the one report instead of creating a bunch of practice reports for all our different situations.
