Redmine

• Wouldn't such default custom queries be useful also for the other Query subclasses?
• Regarding your comment that "[...] Currently, it is a bit difficult for beginners to find the feature. "Save" button is the only way to find it [...]": what about the documentation? It may be rudimentary, but it is clearly explained in RedmineIssueList#Applying-and-saving-filters that filters can be saved. I agree though that this is not (yet) the case for Query subclasses other than IssueQuery.
• On a more general note: I wouldn't suggest to run redmine:load_default_data while provisioning a new Redmine instance in a (corporate) production environment in the first place, but this depends heavily on the scale of the deployment and the kind of environment it's deployed in, so, YMMV.

I'll combine my response on two notes:

Marius BALTEANU wrote in #note-2:

Maybe it's a good idea to add some default queries on a fresh install and not only as default data?

Do you mean via (a) Rails migration(s) or somehow programatically?

Go MAEDA wrote in #note-3:

Updated the patch. Now the rake task adds project queries and time entry queries.

The patch file seems to miss the time entry queries changes.

Mischa The Evil wrote:

I'll combine my response on two notes:

Marius BALTEANU wrote in #note-2:

Maybe it's a good idea to add some default queries on a fresh install and not only as default data?

Do you mean via (a) Rails migration(s) or somehow programatically?

Yes, via a migration that should run only when the queries table has no entries. But it's just an idea :)

Marius BALTEANU wrote:

Marius BALTEANU wrote in #note-2:

Maybe it's a good idea to add some default queries on a fresh install and not only as default data?

Do you mean via (a) Rails migration(s) or somehow programatically?

Yes, via a migration that should run only when the queries table has no entries. But it's just an idea :)

Since only JPL can add new migrations, I think the way will take a longer time to be implemented. On the other hand, updating lib/redmine/default_data/loader.rb is much easier to implement.

I confirm that this should not be done in migrations. It's generally a bad idea to use models in migrations and we should avoid this whenever it's possible.