Landing pages & notices

Landing page priority

1. The originally requested protected URL always wins.
2. A personal landing page is used when overrides are allowed.
3. The global landing page is used next.
4. Redmine's default destination is the fallback.

Supported targets are Redmine default, My page, My Work, and a validated internal Redmine path.

Configure the post-login destination

1. Open Configure → Appearance and select the global landing target.
2. For a custom destination, enter only a path inside the same Redmine installation, for example /issues or /projects/support. Full URLs, protocol-relative URLs, and path traversal are rejected.
3. Decide whether users may override the target in My account. Disabling overrides keeps saved personal choices but temporarily ignores them.
4. Test a normal login and then test a protected link from an email. The protected destination must win so users are not redirected away from the requested issue.

Why a user may reach a different page

A protected original URL takes priority, personal settings take priority over the global setting when overrides are allowed, and invalid custom paths fall back safely instead of redirecting outside Redmine.

Notices

The public login notice supports sanitized Redmine markup. New-issue guidance can combine global, project, and tracker text in that order; tracker guidance refreshes with Redmine's tracker-dependent form.

Publish login and issue guidance

1. Configure the public login notice and global new-issue notice under Configure → Notices.
2. For project guidance, open Project settings → Redmine UX Toolkit. The project module must be enabled for the project notice to appear.
3. Configure tracker guidance in the plugin settings and assign text to the relevant tracker.
4. Create a test issue, change the tracker, and wait for Redmine to refresh the dependent form. The visible order is global, project, then tracker guidance.

Issue creation guidance