search

agileware-jp / redmine_issue_templates

Redmine Issue Template. Pull requests, reporting issues, stars and sponsoring are always welcome!
https://www.redmine.org/plugins/redmine_issue_templates
GNU General Public License v2.0
71 stars 33 forks source link

Update 2014020191500_add_should_replaced_to_issue_template_settings.rb #99

Open popy2k14 opened 6 months ago

popy2k14 commented 6 months ago

Change should_replaced default value from false to true

agileware-oss commented 5 months ago

@popy2k14 Why did you decide to include this change? In general, we do not like to modify a migration file once it has been created and then modify it later.

popy2k14 commented 5 months ago

@agileware-oss i found it rather annoying that if you change the issue template to another one, the template of the new one get's added at the bottom of the current descritpion. In our case we have some tamplets like github, which are over a screen long. Hence, the user changes the template and does'nt see that the new tenplate is added at the bottom. With the function "should_replace" a nice popup will come up and asks the user to replace the content, so the user can decide.

I know it's an db migration script which alters the default setting of the "should_replace" behaviour. But changing this will not change old installations (they are already migrated) but just new ones.

So new users will benefit from the should_replace feature by default and can deactivate it per project.