First template will always be loaded for tracker (also when second, third, ... is selected)

[popy2k14]

Summary

An issue occurs when you have activated should_replace, creating an new ticket and selecting another template after the first default was loaded. Than ALWAYS the first template will be loaded, not the selected (ex.: second)

Description

To reproduce:

• activate should_replace (per project setting)
• activate an default template globally (so it's selected for ex.: tracker bug)
• Add an second template to the tracker with other content (so you can differentiate between the two)
• New ticket -> tracker and template bug should be selected and the first default template visible
• change template to the second one
• question pops up if you want to replace -> yes
• issue occurs and the content will NOT be replaced with the second template content

Environment

These informations are greatly helpful to support quickly.
You can get these informations from Redmine's information page.
(E.g. http://example.com/admin/info)

• Redmine version: 5.0.5
• Installed plugins:
• • redmine_auto_assign_group
• • redmine_checklists
• • redmine_ckeditor
• • redmine_closed_date
• • redmine_dashboard
• • redmine_dmsf
• • redmine_drawio
• • redmine_email_attachments
• • redmine_hide_sidebar
• • redmine_home_page_redirector
• • redmine_impersonate
• • redmine_indicator
• • redmine_issue_favicon
• • redmine_issues_tree
• • redmine_issue_templates
• • redmine_landing_page
• • redmine_logs
• • redmine_release_notes
• • redmine_workflow_enhancements
• • redmine_xlsx_format_issue_exporter
• Ruby version: 3.0.2-p107 (2021-07-07) [x86_64-linux-gnu]
• OS Platform: Ubuntu 22.04.4 LTS
• Database: MySQL Ver 8.0.36-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu))
• Rails Env: 6.1.7.2

Visual Proof / Screenshot

There is no error in the production.log.
Just the issue occurs.

Expected Results

Content will we replaced with the selected template content

Actual Results

Content will NOT be replaced with the selected template content.
It stays on the first template content.