Redmine

Description¶

Redmine already supports default queries for Issues (https://www.redmine.org/issues/7360) and default queries for Projects (https://www.redmine.org/issues/35795).
This feature request proposes extending the same concept to Time Entries, so that users, projects, and administrators can benefit from consistent, predefined views when working with time tracking data.
Time tracking is a central part of many Redmine workflows, but currently users must manually configure filters, columns, grouping, and sorting each time they open the Time Entries view. This results in unnecessary clicks and inconsistent data usage.

Proposed Behavior (Expected Result)¶

1. Global Default Query (Administration Level)¶

Administrators should be able to define a Global Default Query for Time Entries, including:

• Filters
• Columns
• Date range
• Grouping
• Sorting

This query should automatically apply whenever a user opens the Time Entries section—unless overridden by project or user settings.

2. Project-Level Default Query¶

Each project should optionally define a Project Default Query for its Time Entries.
If set, it should override the Global Default Query for users viewing Time Entries inside that project.

3. User-Level Default Query¶

Each user should be able to select one of their saved queries as a Personal Default Query for Time Entries.
This personal default should override:

1. the project default
2. the global default

This matches the existing logic for default queries in other modules.

4. Locations Where the Default Applies¶

The default query should automatically apply everywhere Time Entries are displayed:

• Global Time Entries view
• Project Time Entries view
• My Page Time Entries widget
• Any other list that uses the TimeEntryQuery model

Current Behavior (Problem Statement)¶

Currently, Redmine does not provide a way to define a default query for Time Entries.
Users must manually configure:

• Which columns they want to see
• Which filters to apply
• How entries should be grouped
• How entries should be sorted
• Which date range to display

This repetitive manual setup is inefficient and leads to inconsistent displays across users and projects.

Motivation & Benefits¶

1. Significant Time Savings¶

A default query reduces repeated manual steps required every time users open the Time Entries screen. This is especially beneficial for organizations with heavy time tracking usage, where even small efficiency gains add up.

2. Fewer Clicks, Less Friction¶

Users instantly see the information they need—without extra configuration.
This improves user experience and encourages more frequent and accurate time tracking.

3. Consistency Across the Organization¶

A global default ensures that all users start with a standardized view, improving:

• Data comparability
• Reporting quality
• Alignment across departments

Project- and user-level overrides ensure flexibility where needed.

4. Reuse of Existing Redmine Functionality¶

This feature requires no new UI paradigms.
It extends the existing Query mechanisms already used for:

• Issues
• Projects

This minimizes implementation complexity and maintains a consistent user experience.

Example Use Case¶

An organization wants the default Time Entries view to:

• Show only the current month
• Group entries by project
• Sort entries by date descending
• Display columns such as: User, Activity, Issue, Hours

Today, every user must configure this manually.
With the proposed feature, Redmine can load this configuration automatically based on defaults.