Redmine: Issueshttps://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292024-02-07T02:35:13ZRedmine
Redmine Redmine - Patch #40202 (New): Add LICENSE.txt in the root directoryhttps://www.redmine.org/issues/402022024-02-07T02:35:13ZGo MAEDA
<p>Currently, the COPYING file which describes the license of Redmine is placed under the doc directory. This placement might not be immediately obvious to people.</p>
<p>I propose the addition of a short license file, named LICENSE.txt, to the root directory. This file briefly states that Redmine is licensed under the GNU General Public License version 2 (GPLv2) and the full license text can be found in the doc directory.</p>
<p>This approach has several benefits:</p>
<ol>
<li>It makes it easier for people to find and understand the licensing information at a glance</li>
<li>GitHub will automatically detect the presence of the LICENSE.txt file and display a link to it in the repository's sidebar</li>
<li>It aligns with the common practice among open-source projects to include licensing information in the root directory</li>
</ol> Redmine - Patch #39895 (New): Add hook call in edit issue formhttps://www.redmine.org/issues/398952023-12-21T03:04:54ZAllan C
<p>In Time Spent module, there is a hook call to view_timelog_edit_form_bottom.</p>
<p>In Issue module, when edit issue, there is a section to input time spent but no hook call to view_timelog_edit_form_bottom.</p>
<p>A pull request has been created to add in the hook call and can be viewed <a href="https://github.com/redmine/redmine/pull/148" class="external">here</a>.</p>
<p>Appreciate if the PR can be reviewed. Thanks.</p> Redmine - Patch #38792 (New): Allow removing some watchers via bulk edit context menuhttps://www.redmine.org/issues/387922023-06-28T16:37:33Zsalman mp
<p>It's needed sometimes to remove some watchers in bulk edit.<br />This patch added this feature, but does not contains related tests!</p> Redmine - Patch #38732 (New): Adjusting elements position on Issue Edit Viewhttps://www.redmine.org/issues/387322023-06-16T10:29:09ZYasu Saku
<p>Currentry, elements are not same position on Issue Show View and Issue Edit View.<br />I think it will confuse people who are new to Redmine.<br />So, I propose this patch.</p>
<p><a class="thumbnail" title="adjusting_elements_position_on_issue_edit_view.png" href="https://www.redmine.org/attachments/30655"><img alt="adjusting_elements_position_on_issue_edit_view.png" src="https://www.redmine.org/attachments/thumbnail/30655/300" /></a></p>
<p>Note: You can easily apply similar content as this patch using jQuery.<br /><pre><code class="javascript syntaxhl"><span class="nx">$</span><span class="p">(</span><span class="dl">"</span><span class="s2">#parent_issue</span><span class="dl">"</span><span class="p">).</span><span class="nx">insertAfter</span><span class="p">(</span><span class="nx">$</span><span class="p">(</span><span class="dl">'</span><span class="s1">#issue_project_id</span><span class="dl">'</span><span class="p">).</span><span class="nx">parent</span><span class="p">()).</span><span class="nx">css</span><span class="p">({</span><span class="na">float</span><span class="p">:</span> <span class="dl">"</span><span class="s2">right</span><span class="dl">"</span><span class="p">});</span>
<span class="nx">$</span><span class="p">(</span><span class="dl">'</span><span class="s1">#issue_description_and_toolbar</span><span class="dl">'</span><span class="p">).</span><span class="nx">parent</span><span class="p">().</span><span class="nx">insertAfter</span><span class="p">(</span><span class="dl">'</span><span class="s1">#attributes</span><span class="dl">'</span><span class="p">);</span>
<span class="nx">$</span><span class="p">(</span><span class="dl">'</span><span class="s1">#issue_done_ratio</span><span class="dl">'</span><span class="p">).</span><span class="nx">parent</span><span class="p">().</span><span class="nx">insertAfter</span><span class="p">(</span><span class="dl">'</span><span class="s1">#due_date_area</span><span class="dl">'</span><span class="p">);</span>
<span class="nx">$</span><span class="p">(</span><span class="dl">'</span><span class="s1"><hr></span><span class="dl">'</span><span class="p">).</span><span class="nx">insertAfter</span><span class="p">(</span><span class="dl">'</span><span class="s1">#attributes</span><span class="dl">'</span><span class="p">);</span>
<span class="nx">$</span><span class="p">(</span><span class="dl">'</span><span class="s1"><hr></span><span class="dl">'</span><span class="p">).</span><span class="nx">insertAfter</span><span class="p">(</span><span class="nx">$</span><span class="p">(</span><span class="dl">'</span><span class="s1">#issue_subject</span><span class="dl">'</span><span class="p">).</span><span class="nx">parent</span><span class="p">());</span>
</code></pre></p> Redmine - Patch #38652 (New): Actual translation of Syntax Wiki Bulgarienhttps://www.redmine.org/issues/386522023-06-02T09:45:52ZC S
<p>Source: <a class="external" href="https://www.redmine.org/boards/2/topics/68465?r=68506#message-68506">https://www.redmine.org/boards/2/topics/68465?r=68506#message-68506</a></p> Redmine - Patch #38614 (New): add email handling by subjecthttps://www.redmine.org/issues/386142023-05-26T14:55:47ZAisha Tammy
<p>This change allows the email handler to find issues by subject and adds an option for this to be enabled (disabled by default as SQL full text search might be more expensive than needed).</p>
<p>I needed this as I am trying to use redmine for the openbsd project mailing lists, so I made redmine subscribe to that list and now redmine will add/update issues by looking at mails on this mailing list.</p> Redmine - Patch #38505 (New): Add an index into table custom_values on value columnhttps://www.redmine.org/issues/385052023-04-30T12:43:35Zsalman mp
<p>In my case (due to some custom fields on issues) querying issues was very time consuming.<br />This problem is almost solved by adding some index to the <code>custom_values</code> table on column <code>value</code>.</p> Redmine - Patch #37486 (New): Add JavaScript unit tests.https://www.redmine.org/issues/374862022-07-23T01:49:55ZTakashi Kato
<p>Currently, Redmine does not have JavaScript unit tests; I propose to add lightweight unit tests in a Node.js environment.</p>
<p>Prerequisite environment: Node.js 16 or later, yarn 1.22</p>
<p>Tools to deploy for unit testing: mocha, chai, jsdom</p>
<p>This patch does not require all Redmine developers, including plugins and themes, to install Node.js. This patch uses Node.js only for JavaScript unit tests (like when adding stylelint).</p>
<p>Applying this patch and running yarn install will install the necessary tools for testing.</p>
<p>As a first example of adding tests, I added tests to context_menu.js and refactored them.</p>
<p>As a prerequisite for testing, I convert JavaScript to ES modules. (<a class="external" href="https://javascript.info/modules-intro">https://javascript.info/modules-intro</a>)</p>
<ul>
<li>ES modules do not use global namespaces by default. There is no longer a need to fear duplicate function names; context_menu.js prefixed all functions "ContextMenu" to avoid function names conflict, but that practice is no longer necessary.</li>
<li>Modularizing the scripts will delay processing, waiting until the HTML document is fully ready, which should speed up HTML processing as we move forward.</li>
<li>It would be impractical to es-modularize all of application.js at once, as there is a lot of JavaScript tightly coupled to html (using onclick, link_to_function, etc.). We need to consider other ways to improve.</li>
</ul>
<p>This patch also contains fix <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Fix the unintentional selection of rows with the context menu (Closed)" href="https://www.redmine.org/issues/37481">#37481</a>.</p>
<p>The patch can be applied to <a class="changeset" title="Open Help in a separate tab (#1069). Contributed by Vijay Kiran." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/21737">r21737</a></p> Redmine - Patch #35769 (New): Add a Revision (Changeset) API end-point with support for inclusion...https://www.redmine.org/issues/357692021-08-16T23:22:41ZJan Catrysse
<p>This is a small patch to add an API call to get details about a revision and the linked issues.<br />It should be reviewed by someone with some more experience.</p>
<p>EDIT: app/controllers/repositories_controller.rb<br />ADD: app/views/repositories/revision.rsb</p>
<p>USE: <a class="external" href="https://www.redminexxx.org/projects/{project_name}/repository/{repository_name}/revisions/{revison_name}.json">https://www.redminexxx.org/projects/{project_name}/repository/{repository_name}/revisions/{revison_name}.json</a></p> Redmine - Patch #34654 (New): Accounting for the closing date of the issue when calculating the o...https://www.redmine.org/issues/346542021-01-29T08:14:40ZStan Efremov
<p>When calculating the overdue for issues, the closing date of the issues is not taken into account, despite the availability of relevant information. An overdue issue remains overdue even after it is closed.</p>
<p>Environment:<br /> Redmine version 4.0.4.stable<br /> Ruby version 2.6.5-p114 (2019-10-01) [x86_64-linux]<br /> Rails version 5.2.3<br /> Environment test<br /> Database adapter PostgreSQL<br /> Mailer queue ActiveJob::QueueAdapters::InlineAdapter<br /> Mailer delivery test\nSCM:<br /> Subversion 1.9.7<br /> Git 2.17.1<br /> Filesystem <br />Redmine plugins: no plugin installed</p> Redmine - Patch #33938 (New): Add missing fixtures to IssueNestedSetTesthttps://www.redmine.org/issues/339382020-09-01T03:04:56ZYuichi HARADA
<p>Sometimes IssueNestedSetTest fails.</p>
<pre>
$ RAILS_ENV=test bundle exec rake db:migrate:reset
$ RAILS_ENV=test bundle exec rake test
Run options: --seed 43474
# Running:
............F
Failure:
IssueNestedSetTest#test_destroy_should_destroy_children [./test/unit/issue_nested_set_test.rb:225]:
"JournalDetail.count" didn't change by -1.
Expected: 7
Actual: 6
bin/rails test test/unit/issue_nested_set_test.rb:216
.........F
Failure:
IssueNestedSetTest#test_destroy_child_issue_with_children [./test/unit/issue_nested_set_test.rb:270]:
"JournalDetail.count" didn't change by -1.
Expected: 7
Actual: 6
bin/rails test test/unit/issue_nested_set_test.rb:262
........
Finished in 410.935528s, 12.2404 runs/s, 56.5588 assertions/s.
5030 runs, 23242 assertions, 2 failures, 0 errors, 3 skips
You have skipped tests. Run with --verbose for details.
$
<pre></pre> Redmine - Patch #33722 (Resolved): migrate_from_trac dose not workhttps://www.redmine.org/issues/337222020-07-13T00:51:16ZHideyuki KATO
<p>Current migrate_from_trac rake task dose not work with 3.4.13, 4.0.7, 4.1.1.</p>
<p>There are many patches, but they have not been applied. and they are old (maybe they are for Redmine2.x or early 3.x)</p>
<ul>
<li><a class="issue tracker-3 status-1 priority-4 priority-default" title="Patch: migrate_from_trac.rake does not convert timestamps in Trac database version 23 (New)" href="https://www.redmine.org/issues/14567">#14567</a></li>
<li><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Exception in Migration from Trac to Redmine (incl. solution) (Closed)" href="https://www.redmine.org/issues/17898">#17898</a></li>
<li><a class="issue tracker-1 status-1 priority-4 priority-default" title="Defect: Issues with migrate_from_trac.rake from trac 0.12/1.0 (possible solutions provided) (New)" href="https://www.redmine.org/issues/18658">#18658</a></li>
<li><a class="issue tracker-1 status-1 priority-4 priority-default" title="Defect: Migrating from Trac to Redmine [Trac2Redmine] (New)" href="https://www.redmine.org/issues/24570">#24570</a></li>
</ul>
<p>I have merged these patches and available on Redmine 3.4.13. but not work with Redmine 4.x. because of the difference between Rails/ActiveRecord 4.2 and 5.2.</p>
<p><a class="external" href="https://github.com/hkato/migrate_from_trac.rake/blob/master/migrate_from_trac-trac-1.0.patch">https://github.com/hkato/migrate_from_trac.rake/blob/master/migrate_from_trac-trac-1.0.patch</a></p>
<p>Anyway, could you merge this patch for trunk. and we will support Rails/ActiveRecord 5.2 issue after this.</p>
<p>Redmine 3.4.13</p>
<pre>
$ rake redmine:migrate_from_trac RAILS_ENV="production"
rake aborted!
NoMethodError: undefined method `set_inheritance_column' for TracMigrate::TracAttachment(Table doesn't exist):Class
Did you mean? set_trace_func
/usr/local/bundle/gems/activerecord-4.2.11.1/lib/active_record/dynamic_matchers.rb:26:in `method_missing'
/usr/src/redmine/lib/tasks/migrate_from_trac.rake:121:in `<class:TracAttachment>'
/usr/src/redmine/lib/tasks/migrate_from_trac.rake:119:in `<module:TracMigrate>'
/usr/src/redmine/lib/tasks/migrate_from_trac.rake:25:in `block (2 levels) in <top (required)>'
/usr/local/bundle/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => redmine:migrate_from_trac
(See full trace by running task with --trace)
</pre>
<p>Redmine 4.1.1<br /><pre>
$ rake redmine:migrate_from_trac RAILS_ENV="production"
rake aborted!
NoMethodError: undefined method `set_inheritance_column' for TracMigrate::TracAttachment(Table doesn't exist):Class
Did you mean? set_trace_func
/usr/local/bundle/gems/activerecord-5.2.4.2/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
/usr/src/redmine/lib/tasks/migrate_from_trac.rake:121:in `<class:TracAttachment>'
/usr/src/redmine/lib/tasks/migrate_from_trac.rake:119:in `<module:TracMigrate>'
/usr/src/redmine/lib/tasks/migrate_from_trac.rake:25:in `block (2 levels) in <top (required)>'
/usr/local/bundle/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => redmine:migrate_from_trac
(See full trace by running task with --trace)
</pre></p> Redmine - Patch #32847 (New): Ability to add custom css classes to body taghttps://www.redmine.org/issues/328472020-01-21T09:44:45ZAleksandar Pavic
<p>This ability is important for plugin developers to avoid unnecessary use of deface gem.</p>
<p>If it's going to be implemented, also wiki page for plugin developers should<br />be updated, accordingly.</p> Redmine - Patch #32548 (New): Add new hook in projects/settings/_issues.html.erb for custom fieldshttps://www.redmine.org/issues/325482019-12-03T19:02:50ZJérôme BATAILLE
<p>This would be very helpful to add new features from plugins related to custom fields.</p>
<p>Thanks a lot to take in accout this very small patch<br /><pre><code class="ruby syntaxhl"> <span class="o"><</span><span class="sx">% unless </span><span class="vi">@issue_custom_fields</span><span class="p">.</span><span class="nf">empty?</span> <span class="sx">%>
<fieldset class="box tabular" id="project_issue_custom_fields"></span><span class="o"><</span><span class="n">legend</span><span class="o">><</span><span class="sx">%= toggle_checkboxes_link('#project_issue_custom_fields input[type=</span><span class="n">checkbox</span><span class="p">]</span><span class="ss">:enabled</span><span class="s1">') %><%=l(:label_custom_field_plural)%></legend>
<% @issue_custom_fields.each do |custom_field| %>
<label class="floating">
<%= check_box_tag '</span><span class="n">project</span><span class="p">[</span><span class="n">issue_custom_field_ids</span><span class="p">][]</span><span class="s1">', custom_field.id, (@project.all_issue_custom_fields.include? custom_field),
:disabled => (custom_field.is_for_all? ? "disabled" : nil),
:id => nil %>
<%= custom_field_name_tag(custom_field) %>
</label>
<% end %>
<%= hidden_field_tag '</span><span class="n">project</span><span class="p">[</span><span class="n">issue_custom_field_ids</span><span class="p">][]</span><span class="s1">', '</span><span class="err">'</span> <span class="o">%></span>
<span class="o"><</span><span class="sr">/fieldset>
<%
# The new hook
-%>
<%= call_hook(:view_project_settings_issues_custom_fields, { :issue_custom_fields => @issue_custom_fields, :project => @project }) %>
<% end %>
</span></code></pre></p> Redmine - Patch #32522 (New): Add Project.find_by_name to target_projecthttps://www.redmine.org/issues/325222019-11-27T12:35:23ZKeks Keksov
<p>Consider issue <a class="issue tracker-1 status-5 priority-5 priority-high2 closed" title="Defect: Bug in project name when create issue by email (Closed)" href="https://www.redmine.org/issues/6694">#6694</a>, fix is trivial. Think about all those reporters who struggle to memorizing all that ID stuff.</p>
<p>File app/models/mail_handler.rb<br />Line 410</p>
<p>target = get_project_from_receiver_addresses<br />target ||= Project.find_by_identifier(get_keyword(:project))<br />target ||= Project.find_by_name(get_keyword(:project)) # just one new line</p> Redmine - Patch #32370 (New): Action menu on issues details should not flip with the history orderhttps://www.redmine.org/issues/323702019-10-30T05:05:10ZBernhard Rohloff
<p>By now, when one choose <code>reverse chronological order</code> to display the history of an issue the action menu flips to the top between the issue and the history. Since the action menu isn't related to the history it's not expected by the user. It also causes occasional rendering problems for some users (<a class="external" href="http://www.redmine.org/boards/1/topics/57345">http://www.redmine.org/boards/1/topics/57345</a>), too. The action menu should always stay on the bottom of the view.</p> Redmine - Patch #32326 (Needs feedback): Update it.yml localehttps://www.redmine.org/issues/323262019-10-23T11:23:26Zpasquale [:dedalus]
<ul>
<li>added various missing strings;</li>
<li>reorder strings into the file;</li>
<li>made some changes to already translated strings for consistency.</li>
</ul> Redmine - Patch #32017 (New): A much happier blue palette for the header (#header + #top-menu)https://www.redmine.org/issues/320172019-09-04T17:11:15ZAnonymous
<p>This patch also makes search bar + project selector "camouflage" a bit until clicked.<br /><img src="https://www.redmine.org/attachments/download/23772/newheader.png" alt="" /><br /><img src="https://www.redmine.org/attachments/download/23773/focusedsearchbar.png" alt="" /><br /><img src="https://www.redmine.org/attachments/download/23774/focusedselector.png" alt="" /></p> Redmine - Patch #31987 (New): Add rake task which synchronize all revisions in repositories relat...https://www.redmine.org/issues/319872019-08-31T05:53:13ZKuniharu AKAHANE
<p>Hi, there.</p>
<p>Thank you JPL and all who contributed to improving Redmine such an excellent software.</p>
<p>I wrote a rake task patch changesets.rake .<br />This rake task synchronize all revisions in repositories which related with all active projects.<br />It is useful when some user mistake to write commit-comment for repository.</p>
<ul>
<li>Use Case
<ol>
<li>Refs # <- forgot to write issue_id and/or comment.</li>
<li>Refs #xxxxx <- wrong issue_id</li>
<li> <- forgot to write commit</li>
</ol></li>
</ul>
<p>I know Redmine has a feature to add a reference between issue and commit on web pages.<br />But it does not cover all case, and a bunch of mistakes by a thousand of users on a hundred repositories.<br />Also when i disconnect and reconnect between active project and repository, those additional reference above will be lost.</p>
<p>Even i fix wrong comments on repository, but it will not sync to redmine repository tab and issue reference.<br />So, i think it would be nice if i have a synchronize rake task.</p>
<p>( <a class="user active" href="https://www.redmine.org/users/58128">Kouhei Sutou</a> assisted me for writing this patch. Thanks <a class="user active" href="https://www.redmine.org/users/58128">Kouhei Sutou</a>. )</p> Redmine - Patch #31752 (Reopened): Show assigned people when displaying tickets which are related...https://www.redmine.org/issues/317522019-07-18T15:01:43ZMasatoshi TSUCHIYA
<p>When we hurry a release of a specific version, it is natural to want to know who stops the release.<br />To resolve the such case, I think that the attached patch is useful.</p> Redmine - Patch #31224 (Resolved): My page, add Time Entry querieshttps://www.redmine.org/issues/312242019-04-18T22:33:43ZJérôme BATAILLE
<p>This patch is pretty simple, it continues the work that has been done to add Issue Queries in My Page blocks.<br />It does the same for Time Entry queries, with very few modifications.</p>
<p><strong>Time Entry</strong> block has been renamed <strong>Time Entry Activity</strong></p>
<p>Please review it.<br />Thanks a lot.</p> Redmine - Patch #31151 (New): Add AppServer to Technical Information pagehttps://www.redmine.org/issues/311512019-04-05T12:49:52ZVincent Robert
<p>Hello</p>
<p>The Information page shows some useful data about the current environment. But one important information is missing: the app server.<br />So here is a patch which adds this information to the list.</p>
<p>Thank you</p>
<pre><code class="diff syntaxhl"><span class="gh">diff --git a/app/controllers/admin_controller.rb b/app/controllers/admin_controller.rb
</span><span class="gd">--- a/app/controllers/admin_controller.rb
</span><span class="gi">+++ b/app/controllers/admin_controller.rb
</span><span class="p">@@ -77,5 +77,6 @@</span> class AdminController < ApplicationController
[:text_rmagick_available, Object.const_defined?(:Magick)],
[:text_convert_available, Redmine::Thumbnail.convert_available?]
]
<span class="gi">+ @request = request
</span> end
end
diff --git a/app/views/admin/info.html.erb b/app/views/admin/info.html.erb
<span class="gd">--- a/app/views/admin/info.html.erb
</span><span class="gi">+++ b/app/views/admin/info.html.erb
</span><span class="p">@@ -12,7 +12,7 @@</span>
</table>
<br />
<div class="box">
<span class="gd">-&lt;pre&gt;&lt;%= Redmine::Info.environment %&gt;&lt;/pre&gt;
</span><span class="gi">+&lt;pre&gt;&lt;%= Redmine::Info.environment(@request) %&gt;&lt;/pre&gt;
</span> &lt;/div&gt;
&lt;% html_title(l(:label_information_plural)) -%&gt;
diff --git a/lib/redmine/info.rb b/lib/redmine/info.rb
<span class="gd">--- a/lib/redmine/info.rb
</span><span class="gi">+++ b/lib/redmine/info.rb
</span><span class="p">@@ -6,17 +6,17 @@</span> module Redmine
def help_url; 'https://www.redmine.org/guide' end
def versioned_name; "#{app_name} #{Redmine::VERSION}" end
- def environment
<span class="gi">+ def environment(request = nil)
</span> s = "Environment:\n"
<span class="gd">- s &lt;&lt; [
- ["Redmine version", Redmine::VERSION],
- ["Ruby version", "#{RUBY_VERSION}-p#{RUBY_PATCHLEVEL} (#{RUBY_RELEASE_DATE}) [#{RUBY_PLATFORM}]"],
- ["Rails version", Rails::VERSION::STRING],
- ["Environment", Rails.env],
- ["Database adapter", ActiveRecord::Base.connection.adapter_name],
- ["Mailer queue", ActionMailer::DeliveryJob.queue_adapter.class.name],
- ["Mailer delivery", ActionMailer::Base.delivery_method]
- ].map {|info| " %-30s %s" % info}.join("\n") + "\n"
</span><span class="gi">+ environment_data = [["Redmine version", Redmine::VERSION],
+ ["Ruby version", "#{RUBY_VERSION}-p#{RUBY_PATCHLEVEL} (#{RUBY_RELEASE_DATE}) [#{RUBY_PLATFORM}]"],
+ ["Rails version", Rails::VERSION::STRING],
+ ["Environment", Rails.env],
+ ["Database adapter", ActiveRecord::Base.connection.adapter_name],
+ ["Mailer queue", ActionMailer::DeliveryJob.queue_adapter.class.name],
+ ["Mailer delivery", ActionMailer::Base.delivery_method]]
+ environment_data &lt;&lt; ["App server", request.get_header("SERVER_SOFTWARE")] if request.present?
+ s &lt;&lt; environment_data.map {|info| " %-30s %s" % info}.join("\n") + "\n"
</span>
s &lt;&lt; "SCM:\n"
Redmine::Scm::Base.all.each do |scm|
</code></pre> Redmine - Patch #30999 (Needs feedback): Datepicker javascript files locale in uppercase not foundhttps://www.redmine.org/issues/309992019-03-08T16:50:00ZJérôme BATAILLE
<ul>
<li>In public / javascripts / i18n<br />Files like datepicker-en-GB.js are not found because file is searched with locale that is lowercase.<br />These files should be in lower case.</li>
</ul>
<pre>
The error :
Started GET "/javascripts/i18n/datepicker-en-gb.js" for 127.0.0.1 at 2019-03-08 17:43:44 +0100
17.43.44.110 09924:
17.43.44.110 09924: ActionController::RoutingError (No route matches [GET] "/javascripts/i18n/datepicker-en-gb.js"):
17.43.44.110 09924:
17.43.44.110 09924: actionpack (5.2.2) lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
17.43.44.110 09924:actionpack (5.2.2) lib/action_dispatch/middleware/show_exceptions.rb:33:in `c
</pre> Redmine - Patch #29738 (New): Add last_updated_by feature in issues index apihttps://www.redmine.org/issues/297382018-10-06T12:49:34ZKeita Kariya
<p>Related with [<a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Last updated by colum in issue list (Closed)" href="https://www.redmine.org/issues/6375">#6375</a> Last updated by column in issue list]. This feature is very useful. <br />This patch just adds this feature to issue's index api.</p>
<p>/issues.xml returns like following.<br /><last_updated_by id="1" name="foo bar"/></p>
<p>Tested with version 3.4.3. <br />Version 3.4.3 and trunk revision 17570, the target files were the same.</p> Redmine - Patch #29594 (New): Add view hook to insert content between issue details associated ch...https://www.redmine.org/issues/295942018-09-12T08:09:32ZTim Fischbach
<p>I created a plugin that renders links to associated Github/GitLab merge requests. To insert the box above the associated changesets section, a new view hook is needed.</p>
<p>Patch is attached.</p> Redmine - Patch #29378 (Needs feedback): More call_hooks for projects, issue statusses, time entr...https://www.redmine.org/issues/293782018-08-13T12:33:45ZJonas Ineveld, van
<p>Currently there are only functional call_hooks for issues, and with that, i mean the 'controller_issues_edit_after_save' etc.<br />Because i'm working on a seperate app, connected with redmine on the backend, i need more hooks to hook my 'update API' to.</p>
<p>For now i've created the call_hooks for creation of a project, and for the deletion of a issue.</p>
<p>Would it be something if these changes would go back into core? I can imagine more uses for these type of hooks.</p>
<p>Svn patch file is included</p> Redmine - Patch #29185 (New): Add my_page to the application menuhttps://www.redmine.org/issues/291852018-07-04T08:30:09ZMizuki ISHIKAWA
This patch makes the following two changes
<ul>
<li>Add my page to application menu</li>
<li>Change to display application menu on my page screen</li>
</ul>
<p>This patch makes it easier to move from My Page to issues and activities.<br /><img src="https://www.redmine.org/attachments/download/21023/my_page.png" alt="" /></p> Redmine - Patch #29184 (New): Add home to the application menuhttps://www.redmine.org/issues/291842018-07-04T08:16:46ZMizuki ISHIKAWA
<p>This patch makes the following two changes<br />・Add home to application menu<br />・Change to display application menu on home screen</p>
<p>By applying this change you can check issues and activities as soon as you login.</p>
<p><img src="https://www.redmine.org/attachments/download/21022/home.png" alt="" /></p> Redmine - Patch #28861 (New): Add a date item to the context menuhttps://www.redmine.org/issues/288612018-05-23T08:23:51ZMizuki ISHIKAWA
<p>The context menu is very convenient because you can change the information without making a screen transition.<br />I would like to change the date information by context menu.</p>
<p>By applying this patch you can open a modal to change the date.</p>
<table>
<tr>
<td><img src="https://www.redmine.org/attachments/download/20748/screenshot1.png" alt="" /></td>
<td><img src="https://www.redmine.org/attachments/download/20747/screenshot2.png" alt="" /></td>
</tr>
</table> Redmine - Patch #28771 (New): Allow adding multiple entities when performing multiple searches in...https://www.redmine.org/issues/287712018-05-14T22:26:25ZMarius BĂLTEANU
<p>This ticket is related to <a class="issue tracker-1 status-1 priority-4 priority-default" title="Defect: Adding Watchers UX Is Not Clean (New)" href="https://www.redmine.org/issues/17071">#17071</a> and <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Edit Watchers List Loses Checked Watchers When Performing Multiple Searches (Closed)" href="https://www.redmine.org/issues/17579">#17579</a>.</p>
<p>In <a href="https://zitec.com" class="external">Zitec</a>, we are trying to find a clean UI/UX solution to allow users to add multiple entities when performing multiple searches in modals like Add Watchers, Add members, Add projects. The current issues are very well explained in the related tickets.</p>
<p>We came up with 3 proposals:</p>
<p>1. <strong>add_to_bottom.jpg</strong> which display the selected entities (users for example) under the search results section:<br /> <img src="https://www.redmine.org/attachments/download/20662/add_to_bottom.jpg" style="width: 50%;border: 1px solid #ccc;" alt="" /></p>
<p>2. <strong>add_to_right_with_checkbox.jpg</strong> which display the selected entities to the right of the search results</p>
<p><img src="https://www.redmine.org/attachments/download/20663/add_to_right_with_checkbox.jpg" style="width: 50%;border: 1px solid #ccc;" alt="" /></p>
<p>3. <strong>add_to_right_with_x.jpg</strong> same as 2, but an "X" icon is used to remove the selected entities.</p>
<p><img src="https://www.redmine.org/attachments/download/20664/add_to_right_with_x.jpg" style="width: 50%;border: 1px solid #ccc;" alt="" /></p>
<p>Personally, I like the 3rd solution. Any feedback is welcome.</p> Redmine - Patch #28025 (New): Access project jump box with hotkeyhttps://www.redmine.org/issues/280252018-01-19T15:43:36ZBernhard Rohloff
<p>Accesskeys are a very convenient though quite unknown feature of Redmine.<br />This patch adds an additional accesskey ('j' for "jump") to the project jump box in the header section.<br />With this hotkey you are able to switch between projects very fast and without the need of touching the mouse.</p> Redmine - Patch #26439 (New): Plugin load order defined by plugin checkshttps://www.redmine.org/issues/264392017-07-14T13:36:40ZTiago Gonçalvestgoncalves@microio.pt
<p>This patch allows for a plugin to delay loading until a set of requirements is met. This could be because I need for other plugin to be loaded first.</p>
<p>The ideia is to to have each plugin check at the top of init.rb for it's requirements and if they are not met to raise Redmine::Plugin::PluginDeferLoadError. This will signal the plugin load logic to try loading this plugin later.</p>
<p>The algorithm prevents infinite looping (by direct or indirect circular dependencies) by loading plugins by iterations. In each iteration amount of plugins to load must be lower.</p>
<p>The most common check made by plugins can be simplified by using at the top of the init.rb this line:</p>
<pre><code class="ruby syntaxhl"><span class="no">Redmine</span><span class="o">::</span><span class="no">Plugin</span><span class="p">.</span><span class="nf">requires_plugin</span><span class="p">(</span><span class="s1">'redmine_plugin_name'</span><span class="p">)</span>
</code></pre>
<p>Regards</p> Redmine - Patch #26139 (Reopened): Follow Gemfile's plugin loader as #24007https://www.redmine.org/issues/261392017-06-12T09:31:12ZSho HASHIMOTO
<p>Plugin's Gemfile can't settable from Redmine::Plugin.directory yet.</p> Redmine - Patch #26122 (Resolved): Implementation of visible conditions with inner join instead o...https://www.redmine.org/issues/261222017-06-07T20:51:37ZPavel Rosický
<p>The change from <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Project#allowed_to_condition performance (Closed)" href="https://www.redmine.org/issues/21608">#21608</a> should be reverted because it's a speed regression:</p>
<p>1/ current version<br /><pre>EXISTS (SELECT 1 AS one FROM enabled_modules em WHERE em.project_id = projects.id AND em. NAME = 'issue_tracking')</pre></p>
<p>2/ previous version (actually faster even without an index on enabled modules)<br /><pre>projects.id IN (SELECT project_id FROM enabled_modules em WHERE em.project_id = projects.id AND em. NAME = 'issue_tracking'</pre></p>
<p>3/ fastest version (in some cases better indexes were used)<br /><pre>INNER JOIN `enabled_modules` ON `enabled_modules`.`project_id` = `projects`.`id` WHERE `enabled_modules`.`name` = 'issue_tracking'</pre> or<br /><pre>INNER JOIN `enabled_modules` ON `enabled_modules`.`project_id` = `projects`.`id` AND `enabled_modules`.`name` = 'issue_tracking'</pre></p>
Patches:
<ul>
<li>revert of <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Project#allowed_to_condition performance (Closed)" href="https://www.redmine.org/issues/21608">#21608</a>, because the previous version was faster (about 30%)</li>
<li>new index "enabled_modules_name", but it's not very helpful unless you have many projects (3000+)</li>
<li>implementation of visible conditions with inner join instead of subselect, it passes all tests, but it should be refactored. I want to know what do you think about it first</li>
</ul>
<pre>
Rails version 4.2.8
Ruby version 2.1.9-p490 (x64-mingw32)
RubyGems version 2.6.12
Rack version 1.6.8
Middleware Rack::Sendfile, Rack::ContentLength, ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x00000007745610>, Rack::Runtime, Rack::MethodOverride, ActionDispatch::RequestId, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::DebugExceptions, ActionDispatch::RemoteIp, ActionDispatch::Reloader, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::XmlParamsParser, Rack::Head, Rack::ConditionalGet, Rack::ETag, RequestStore::Middleware, OpenIdAuthentication
Environment development
Database adapter mysql2
Database schema version 20170607051650
</pre> Redmine - Patch #25491 (Needs feedback): List of role membershttps://www.redmine.org/issues/254912017-03-31T21:12:38ZAnonymous
<p>This simple patch provides a list of all members of a role grouped by projects.</p>
<p>Tested and working with Redmine 3.2 & 3.3</p> Redmine - Patch #25114 (Needs feedback): Context menu positioning inside positioned DOM elementshttps://www.redmine.org/issues/251142017-02-17T13:23:25ZSerge Galanin
<p>In my theme the #content element is positioned relatively. It leads to an incorrect positioning of the context menu wich living inside the #content. A most simple fix is to bubble the context menu up to the top of DOM. Can we use this way?</p>
<p>Patch based on <a class="changeset" title="remove trailing white space from test/unit/setting_test.rb" href="https://www.redmine.org/projects/redmine/repository/svn/revisions/16333">r16333</a>.</p> Redmine - Patch #24837 (Needs feedback): Bulk update issues with authorhttps://www.redmine.org/issues/248372017-01-16T07:55:14ZMarcin Świątkiewicz
<p>It would be nice, to add option to bulk update many different issues with option 'assigned to author'.<br />Below is my diff with this feature.</p> Redmine - Patch #24435 (New): Add `view_account_contextual` and `view_account_list_buttons` hookshttps://www.redmine.org/issues/244352016-11-23T11:40:03ZArthur Andersen
<p>This patch adds two view hooks:</p>
<ul>
<li>`view_account_contextual`</li>
<li>`view_account_list_buttons`</li>
</ul>
<p>to be able to let plugins add user specific links to the user profile and the userlist in the admin interface.</p> Redmine - Patch #24072 (New): Added formatting for email notificationshttps://www.redmine.org/issues/240722016-10-14T19:10:49ZBryan Settles
<p>This is meant to allow email notifications to show due date, and separate the issues that are past due from the ones that are due in the next (custom amount) of days</p> Redmine - Patch #24051 (Resolved): As a non-admin user using API, I want to be able to filter use...https://www.redmine.org/issues/240512016-10-11T18:36:15ZAnonymous
<p>We created an Odoo -> Redmine connector for uploading time spent from Redmine to HR tools in Odoo (<a class="external" href="https://github.com/savoirfairelinux/connector-redmine/tree/ddufresne_port_to_8_0">https://github.com/savoirfairelinux/connector-redmine/tree/ddufresne_port_to_8_0</a>).</p>
<p>When we call that function from a superuser API key, all works well, but when it is normal user API key, it does return a forbidden exception :</p>
<pre>
redmine_api.user.filter(name="SOMEUSERNAME")
</pre>
<p>I think that to reinforce security by not giving superuser Redmine API key to Odoo would be interesting.</p>
<p>That would be possible by allowing standard Redmine users to use API to filter users by their username instead of throwing an exception.</p> Redmine - Patch #24007 (Reopened): Change plugins directory through the configuration.yml filehttps://www.redmine.org/issues/240072016-10-05T18:18:02ZHelder Manuel Torres Vieira
<p>This patch adds the possibility to change the directory "plugins" of the application through the file configuration.yml.</p>
<p>The patch has been tested with the last Trunk version (15839)</p> Redmine - Patch #23498 (New): Add plugin view hook for wiki context menuhttps://www.redmine.org/issues/234982016-08-02T16:50:53ZTom Smyth
<p>I believe subject is self explanatory.</p> Redmine - Patch #21808 (Needs feedback): Make the Sidebar collapsible, statefulhttps://www.redmine.org/issues/218082016-01-23T20:58:50ZDaniel Ritz
<p>This adds a button to the sidebar to make it collapsible. The state is preserved between requests with a cookie.</p>
This seems to be a feature that is missed. There's a few plugins that implement something similar. Some of them:
<ul>
<li><a class="external" href="https://www.redmine.org/plugins/sidebar_hide">https://www.redmine.org/plugins/sidebar_hide</a></li>
<li><a class="external" href="http://www.redmine.org/projects/redmine/wiki/PluginCollapse">http://www.redmine.org/projects/redmine/wiki/PluginCollapse</a></li>
<li><a class="external" href="https://github.com/thambley/redmine-sidebar-hide">https://github.com/thambley/redmine-sidebar-hide</a></li>
</ul>
<p>And there are related issues, at least: <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Collapsible Sidebar (Closed)" href="https://www.redmine.org/issues/12032">#12032</a>, <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: A new button to hide/show the sidebar (Closed)" href="https://www.redmine.org/issues/10525">#10525</a></p>
<p>Because of high demand from my users, I did something similar in a theme at work. This is basically that plus it's stateful now.</p>
This patch:
<ul>
<li>Adds the relative URL root as a meta property in the head tag</li>
<li>Adds a simple <a> to the sidebar as collapse/expand button</li>
<li>Makes the .content a BFC taking the remaining width</li>
<li>Few lines of javascript to toggle CSS and set a cookie</li>
<li>Sidebar is hidden by setting its margin-right</li>
<li>Nice hiding animation using CSS for browsers that support it</li>
<li>The state of the sidebar is read from the cookie and applied on page load</li>
<li>Good theming support since it's mostly just CSS</li>
</ul>
<p>Based on <a class="changeset" title="Typo (#21421)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/15095">r15095</a>, passes all tests with Ruby 2.1.5. Tested on FF, Chrome, Safari (+ an earlier, stateless version on IE11)</p>
<p>Screenshot: <img src="https://www.redmine.org/attachments/download/15176/collapsible_sidebar.png" title="Screenshot" alt="Screenshot" /></p> Redmine - Patch #21550 (Needs feedback): New option in html redmine link parsing - attachmentshttps://www.redmine.org/issues/215502015-12-16T21:32:09ZOndřej Ezr
<p>Option for parsing to choose if attachment link should be download link or not.</p> Redmine - Patch #21101 (New): Add go-to action schemahttps://www.redmine.org/issues/211012015-10-29T15:33:02ZAn Phan
<p>This is to add a <a href="https://developers.google.com/gmail/markup/reference/go-to-action" class="external">go-to action schema</a> that should enable a "View issue" button in Gmail (similar to that in Github emails).</p> Redmine - Patch #20888 (New): Add a button in the textile formatting toolbar to convert tabulated...https://www.redmine.org/issues/208882015-10-01T10:09:29ZOlivier Houdas
<p>When pasting from Google sheets or Microsoft Excel or Open Office ODS into the Description or Notes area of issues, the values are automatically converted to text, and cell limits to tabulations, in Firefox, Internet Explorer, or Chrome.</p>
<p>Based on this observation, a Table button in the Textile toolbar which would replace tabulations with pipes and add pipes at lines start and ends would be very useful.</p>
<p>Attached is a patch for Redmine 3.1.1 which adds this feature.</p>
<p>The patch includes the tooltip text only for English and French, other languages require to be updated.</p>
<p><img src="https://www.redmine.org/attachments/download/14330/TextileTableButton-1.png" alt="" /></p>
<p><img src="https://www.redmine.org/attachments/download/14331/TextileTableButton-2.png" alt="" /></p> Redmine - Patch #20287 (New): Administration: Using grids instead of tableshttps://www.redmine.org/issues/202872015-07-10T20:09:37ZFrederico Camara
<p>We are a brazillian government agency and we've been using Redmine to control ExpressoBr (groupware) tickets.</p>
<p>Some time ago, it became difficult to manage the workflow status transitions. In a complex workflow, the table becomes so large it would scroll horizontally and vertically away from the first line and column. Zooming out and filters helped somehow, mainly if the status transition would be nearer the top left. The most recently created statuses would be too far right and down for zoom to help.</p>
<p>This patch transforms the administration tables into grids, so the first row and first column are always visible, like in a worksheet. Also, I got rid of the button that selected the whole line or column, because it became completely useless in a large grid, but I think it is easy to put it back.</p>
Redmine has 5 pages with tables in administration:
<ul>
<li>Roles and Permissions > Permission Report</li>
<li>Trackers > Summary</li>
<li>Workflow > Summary</li>
<li>Workflow > Status transitions</li>
<li>Workflow > Field permissions</li>
</ul>
<p>The grid itself is something like a table, it has four parts: A floating first cell, a first line stuck to the top of the grid, a first row stuck to the left, a body that on scroll, repositions the first row and first line using javascript. The other javascript resizes the width of columns in the grid.</p> Redmine - Patch #20063 (New): Add "issue#<number>" syntax for issue linkshttps://www.redmine.org/issues/200632015-06-10T09:50:46ZOlivier Houdas
<p>For most Redmine items (news, documents, wiki articles...), the link displays the title as the link's text, and follows the syntax: news#<number>, document#<number>, etc.</p>
<p>For issues, the only syntax is simply #<number>, and shows the issue number as the link's text.</p>
<p>This patch adds the syntax issue#<number>, and will display the bug title followed by the bug status as the link text.<br />The patch does not remove anything, it only adds a new syntax.</p> Redmine - Patch #19108 (New): Ability to limit search to last week/month/yearhttps://www.redmine.org/issues/191082015-02-14T10:53:16ZPierre Pretorius
<p><strong>Problem</strong></p>
<p>Redmine search doesn't support or use full text searching features of mysql, postgres, lucene or elasticsearch, etc. which means it unfortunately doesn't scale well. The <code>like %keyword%</code> query basically does a table scan which can easily take 10+ seconds on a medium database with decent hardware (Amazon EC c3.large - high CPU instance).</p>
<p>We tried the <a href="https://github.com/Undev/redmine_elasticsearch" class="external">elastic search plugin</a> (it's still in early beta) for Redmine but it gave unreliable results and turned out to degrade our user confidence in the search.</p>
<p><strong>Solution</strong></p>
<p>After looking at what other ticketing/issue/case management solutions do, I see many of them include a "past week/month/year" in their search and it usually has a default value of past year or month.</p>
<p>This patch adds a dropdown to select last week/month/year/all time on the search screen and defaults to last year as shown in attached screen shot. I was able to use existing translations except for the newly added "label_last_year". I followed the conventions of the rest of your code base as far as possible. The patch was generated on your 2.6 stable branch.</p> Redmine - Patch #18778 (New): Add new alias for issue note links ('comment')https://www.redmine.org/issues/187782015-01-08T05:41:20ZKatsuya HIDAKA
<p>This patch adds an new redmine link <code>"#123#comment-1"</code> as an alias for issue note link <code>"#123#note-1"</code>. I think easy to understand better "comment" than "note" in some cases.</p> Redmine - Patch #18496 (Resolved): Migrate to Redmine 2.5.3 (or 2.6.0) from Mantis 1.2.17https://www.redmine.org/issues/184962014-11-28T14:03:46ZGergely Révész
<p>Migrate to Redmine 2.5.3 (or 2.6.0) from Mantis 1.2.17.</p>
<p>The original migrate script quits with errors when migrating from Mantis 1.2.17.<br />I'm attaching the patch to get it to work.<br />And the working full "migrate_from_mantis.rake" file if anyone finds it difficult to apply a patch.</p>
<p>You have to patch or replace the "%redmine%/lib/tasks/migrate_from_mantis.rake" file.</p> Redmine - Patch #18209 (New): Add e-mail notification option: Tracker updatedhttps://www.redmine.org/issues/182092014-10-27T14:24:16ZMartin Cizek
<p>The "global" email notifications settings (Administration -> Settings -> Email notifications) currently allow to specify the following issue updates to be watched by users who have chosen to watch "any events on...":<br /><pre>
[ ] Issue updated
[x] Note added
[x] Status updated
[x] Assignee updated
[x] Priority updated
</pre><br />We suggest to add "Tracker updated", as we consider it a substantial event for certain people (e.g. a customer willing to know whenever a Bug is changed to a Feature, but don't want to be spammed by issue reassignments). The new 'Issue updated' action notifications would be:<br /><pre>
[ ] Issue updated
[x] Note added
[x] Status updated
[x] Assignee updated
[x] Priority updated
[x] Tracker updated
</pre></p>
<p>This update would be especially beneficial for <a href="http://www.redmine.org/plugins/event_notifications" class="external">Event notifications</a> plugin users, who are able to set these standard notification options also per-user and per-project.</p>
<p>The patch against current trunk (<a class="changeset" title="Latvian translation updated by Jānis Elmeris (#18182)" href="https://www.redmine.org/projects/redmine/repository/svn/revisions/13520">r13520</a>) is attached; if there is anything we should improve, please let us know.</p>
<p>P.S. I've noticed this feature is similar to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Option to send email on "Assignee updated" (Closed)" href="https://www.redmine.org/issues/16362">#16362</a>, where assignee change was added.</p>
<p>(thanks to Sandra Tatarevicova, sponsored by Orchitech Solutions)</p> Redmine - Patch #18059 (Resolved): Activity when issue change assigned to.https://www.redmine.org/issues/180592014-10-10T11:59:15ZMarcin Świątkiewicz
<p>Hi. There is patch to change activity for project. It's will shows you when issue status was changed, assigned_to was changed, and when status and assigned_to was changed together.</p>
<p>I wrote test for this and everything works fine.</p>
<p>See files.</p> Redmine - Patch #17900 (New): Allow change value of the time_entry object via controller_issues_e...https://www.redmine.org/issues/179002014-09-17T14:34:49ZTieu-Philippe Khim
<p>At the moment we could not made some modification on time_entry from <code>controller_issues_edit_before_save</code> hook.<br />Because the object created is push in <code>time_entries</code> attribute, so a plugin using the <code>controller_issues_edit_before_save</code> hook could not access to the latest entry and change the value if needed.</p>
<p>The attached patch make that possible.</p> Redmine - Patch #16116 (Needs feedback): Sort of version optionshttps://www.redmine.org/issues/161162014-02-18T08:51:15ZDaniel Felix
<p>Hi there,</p>
<p>currently all versions are just sorted by an array.</p>
<p>This causes that our version field results in an unsorted order. Either id nor name or date (all dates are nil) is respected.</p>
<p>This way could improve the version sort.</p>
<p>See <a class="source" href="https://www.redmine.org/projects/redmine/repository/svn/entry/trunk/app/models/issue.rb#L743">source:trunk/app/models/issue.rb#L743</a></p>
<p>Replace this line with<br /><pre><code class="ruby syntaxhl"><span class="vi">@assignable_versions</span> <span class="o">=</span> <span class="n">versions</span><span class="p">.</span><span class="nf">uniq</span><span class="p">.</span><span class="nf">sort_by</span><span class="p">{</span><span class="o">|</span><span class="n">v</span><span class="o">|</span> <span class="p">[</span><span class="n">v</span><span class="p">.</span><span class="nf">effective_date</span><span class="p">,</span> <span class="n">v</span><span class="p">.</span><span class="nf">name</span><span class="p">]}</span>
</code></pre></p>
<p>This will sort the result in first place by effective date and otherwise by name.</p>
<p>Any regressions?</p>
<p>Best regards,<br />Daniel</p> Redmine - Patch #16045 (New): Add "Previous Assignee" entry when changing issue assigneehttps://www.redmine.org/issues/160452014-02-06T17:45:05ZGurvan Le Dromaguet
<p>Intention : assign ticket back to previous assignee easily, without scrolling down the list until I found it.</p>
<p>attached proposed implementation as svn patch. It needs to run "db:migrate"</p>
<p>Missing in the implementation:<br />- previous assignee in contextual menu<br />- maybe reusing changes done in <a class="changeset" title="Fixed that previous assignee is not notified on issue update (#15714)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/12419">r12419</a></p>
<p>Works good and very popular in my firm.</p> Redmine - Patch #15906 (Needs feedback): Create a default forum by defaulthttps://www.redmine.org/issues/159062014-01-20T08:35:28ZJan from Planio www.plan.io
<p>In my experience, new or inexperienced users find it hard to get started with the forums. This is because of the fact that it doesn't suffice to enable the module, one has to also create a first forum in the project settings.</p>
<p>I therefore propose this patch which adds an empty "general" forum when the module is activated. It uses the same mechanism that creates the project's wiki.</p>
<p>This way, users will see the "Forums" tab in their project immediately after they enabled the module.</p> Redmine - Patch #15234 (New): A popup message after session timeouthttps://www.redmine.org/issues/152342013-10-31T16:30:12ZKarel Pičman
<p>When the session timeout is set and a user leaves an unsaved form for a while so their session expires and clicks on the <em>Save</em> button, they is redirected to the login page and all unsaved data from the form just being edited are lost.</p>
<p>The same frustrating situation can happend when you write a long wiki page.</p>
<p>The flash message on the login page does't help to recover lost data.</p>
<p>I thing that the user should be warn before data are lost.</p>
<p>Please take into account the attached simple patch that add a Javascript popup message with the warning text about session expiration.</p> Redmine - Patch #14148 (Reopened): Double translation: label_f_hours vs. x_hourshttps://www.redmine.org/issues/141482013-05-25T13:05:52ZFilou Centrinov
<p>It seems that the translations <code>x_hours</code> and <code>label_f_hours</code> are identic. (Same with <code>x_hour</code> and <code>label_f_hour</code>.) Moreover for many languages only <code>label_f_hours</code> (respectively <code>label_f_hour</code>) is translated. I suggest to replace <code>label_f_hours</code> by <code>x_hours</code>, because we have also x_minutes, x_seconds, ...</p>
<p>Finally I suggest to delete the labels <code>label_f_hour</code> and <code>label_f_hours</code> from all translation files and repository.</p> Redmine - Patch #13545 (Needs feedback): Workflow permissions are broken if user has multiple rol...https://www.redmine.org/issues/135452013-03-21T13:51:23ZAlexander Kriventsov
If user has multiple roles in project workflow permissions don't work.<br />It works in two cases:
<ol>
<li>User has one role</li>
<li>User has two roles with the same workflow permisions</li>
</ol> Redmine - Patch #13239 (Resolved): migrate_from_mantis script doesn't work for later mantis versionshttps://www.redmine.org/issues/132392013-02-20T21:46:28ZDiego Antunes
<a name="Redmine-Info"></a>
<h2 >Redmine Info<a href="#Redmine-Info" class="wiki-anchor">¶</a></h2>
<p>Environment:<br /> Redmine version 2.2.2.stable<br /> Ruby version 1.9.3 (x86_64-linux)<br /> Rails version 3.2.11<br /> Environment production<br /> Database adapter Mysql2<br />Redmine plugins:<br /> no plugin installed</p>
<a name="Mantis-BT-info"></a>
<h2 >Mantis BT info<a href="#Mantis-BT-info" class="wiki-anchor">¶</a></h2>
<p>Site Information<br />MantisBT Version 1.2.11<br />Schema Version 185</p> Redmine - Patch #12983 (New): "Only for things I watch or I'm involved in" sends notifications on...https://www.redmine.org/issues/129832013-01-25T14:05:20ZFelix Schäfer
<p>The e-mail notifications setting "Only for things I watch or I'm involved in" currently only sends notifications for issue updates. This has confused some of our (Plan.io) users because they didn't receive notifications for other things than issues they'd watch.</p>
<p>Patch is upcoming.</p> Redmine - Patch #12746 (New): Add include=journals support to issues REST apihttps://www.redmine.org/issues/127462013-01-05T11:05:46ZDerek Slone-Zhen
<p>To see what has changed on an issue it seems necessary to obtain the history of journal objects that are associated with the issue. I was trying to do this through the REST API and discovered that I could get the journals for a SINGLE issue by adding "include=journals" as a query argument, but that it appeared to be ignored when used on the issues index. I coded my way around this client side by requesting each issue individually to get around this, but it seemed inefficient. So, attached is a patch that will add this functionality into <code>app/views/issues/index.api.rsb</code>.</p>
<p>This was made against svn+ssh://rubyforge.org/var/svn/redmine/trunk@11110</p>
<p>This is my first Open Source contribution and my first venture into Ruby and Rails - I'm open to polite coaching if required!</p> Redmine - Patch #11500 (New): Add --unknown-user=register to create inactive usershttps://www.redmine.org/issues/115002012-07-24T12:54:54ZAlex Shulgin
<p>This patch adds a new value for the <code>--unknown-user</code> option of the mail handler script.</p>
<p>When given, it will behave similar to <code>--unknown-user=create</code>, but the user account will not be automatically activated. Depending on the site configuration, either token activation or manual activation by administrator will be required. The purpose is to help keep spam level low on public projects.</p>
<p>The change is a bit involved as it required moving the registration logic from accounts controller to the User model.</p> Redmine - Patch #10869 (New): Add Full PDF output to issue summary listhttps://www.redmine.org/issues/108692012-05-10T02:45:32ZCarl Nygard
<p>The PDF output is very useful for providing information to outside stakeholders without requiring access to Redmine itself. This is very useful for progress reports and meetings. However, there is no way to output a set of issues with full details. Currently you only get the summary list, which just shows the Subject etc., or an individual PDF for an individual issue's full comment history.</p>
<p>This patch provides an additional 'Full PDF' option to the main issues summary page, which will output the issue summaries, followed by the detail for each of the issues selected.</p>
<p>This will obey current filters and only show what has been selected.</p>
<p>In order to implement this, some of the PDF export code was reorganized a bit to allow better re-use of the individual issue output functionality. Also, a new function was added to dispatch to the actual pdf generation function, depending on whether a normal summary or a full output was selected.</p> Redmine - Patch #10767 (New): Adding completed ratio support to log messageshttps://www.redmine.org/issues/107672012-04-25T09:44:09ZAngelo Compagnucci
<p>Hi,</p>
<p>This patch enables adding completed ratio to issues via commit messages, the syntax is like</p>
<p>ref #12345 @1h20m 50%</p>
<p>Patch modifies only app/models/changeset.rb</p> Redmine - Patch #10509 (New): Add view_groups_form hookhttps://www.redmine.org/issues/105092012-03-21T13:53:30ZMax Haventon
<p>Useful hook for plugins that extend groups.</p> Redmine - Patch #10456 (New): Add view_roles_form_upper_box hookhttps://www.redmine.org/issues/104562012-03-15T17:03:43ZMax Haventon
<p>Useful hook for plugins that extend roles.</p> Redmine - Patch #9697 (Resolved): Projects list with progresshttps://www.redmine.org/issues/96972011-11-30T10:25:33ZDmitry Babenko
<p>Redesign of project list page (<a class="external" href="http://www.redmine.org/projects">http://www.redmine.org/projects</a>) to show the progress of every project and their versions. See <a class="attachment" href="https://www.redmine.org/attachments/6836">Redmine-project-list-with-progress.png</a>.</p>
<p>Gihub pull request: <a class="external" href="https://github.com/edavis10/redmine/pull/46">https://github.com/edavis10/redmine/pull/46</a></p> Redmine - Patch #9317 (New): Admin users should be always authorized when no context is givenhttps://www.redmine.org/issues/93172011-09-25T08:52:02ZAlex Shulgin
<p>In a situation where <code>@project</code> might or might not be set by filters before the call to <code>authorize</code> you would need to check for that and either call <code>authorize</code> or <code>authorize_global</code> (otherwise admin user will get '403 You are not authorized to access this page', which is ridiculous).</p>
<p>With this patch applied, a plain <code>before_filter :authorize</code> may be used instead.</p> Redmine - Patch #8934 (New): Add support for annotate with subversion when username contain spacehttps://www.redmine.org/issues/89342011-07-28T11:46:46ZYaacov Akiba Slama
<p>When username contains space(s), annotate doesn't work for subversion because it uses the "<code>blame</code>" subcommand which returns the file given prefixed by the revision number and the author separated by spaces. So any parsing based on that will break if author can contain spaces.</p>
<p>The attached patch uses the same subcommand but with the additional <code>--xml</code> option in order to obtain a full xml instead of space separated fields.<br />The drawback is that the lines themselves are not returned by svn when <code>--xml</code> is used. Consequently, one needs to call both <code>blame --xml</code> and <code>cat</code> subcommands to have both the metadata and the content.</p>
<p>The included patch can be used on top on 1.2 and 1.2.1 (at least).</p> Redmine - Patch #8757 (New): Add hook for bulk edit post-save statehttps://www.redmine.org/issues/87572011-07-06T21:40:53ZRamesh Nair
<p>There is a hook which gets invoked just after an individual issue gets updated, which allows for plugins to perform any post-save actions. There ought to be a similar hook for when a number of issues have been updated via the bulk-editing process. I've patched the core code to enable such a hook - `controller_issues_bulk_edit_after_save`.</p>
<p>Patch available at <a class="external" href="https://github.com/7citylearning/redmine/commit/f88c6ca01e89246b5bcd62fa26cc651ee33ba212">https://github.com/7citylearning/redmine/commit/f88c6ca01e89246b5bcd62fa26cc651ee33ba212</a></p> Redmine - Patch #8222 (Needs feedback): Setting model should use Rails.cache instead of class var...https://www.redmine.org/issues/82222011-04-25T17:44:22ZJan from Planio www.plan.io
<p>The <code>Setting</code> model uses two local class variables called <code>@cached_settings</code> and <code>@cached_cleared_on</code> to prevent reloading the settings from database and/or <code>settings.yml</code> at every request.</p>
<p>Rails has been supporting different cache implementations for some time now, why not let the <code>Setting</code> model use them as well? Besides the fact that this will help with tenant switching which we've implemented for Planio, it should also improve Redmine's performance when running it with more than processes and a custom cache mechanism, like memcached.</p>
<p>A patch is attached.</p> Redmine - Patch #8196 (New): Adding a project param to perl auth modulehttps://www.redmine.org/issues/81962011-04-20T08:48:41ZDiego Suárez García
<p>Hello,</p>
<p>In my job we use Redmine and recently we had the need for authenticating the access to a test domain, based on which users have access to the related project. I created a small patch to the Redmine.pm module, that adds a new optional apache directive (RedmineDbProject), so you can link a VirtualHost to a specific project and ask for credentials on user access. That way, only the users included in that project can see that VirtualHost contents.</p>
<p>I felt somebody else might have the same needs. The directive is optional and the behaviour is transparent if it's not included in the conf file, therefore I think it can make it to the core.</p>
<p>The revision is 5506 (last change on Redmine.pm on 5232), and it's the trunk version.</p>
<p>Best Regards,</p>
<p>Diego Suárez García.</p> Redmine - Patch #6722 (New): Add a summary to projectshttps://www.redmine.org/issues/67222010-10-21T19:47:13ZHolger Just
<p>There are two places where projects are displayed in mass: <code>/projects</code> and the project's admin. On both places, part of the description is displayed. This is suboptimal as the view gets really messy if you include some more verbose status information into the description.</p>
<p>Thus I propose adding a short summary to the project which is displayed in these locations. It would make the view much clearer and more usable because of better content.</p>
<p>The attached patch introduces this.</p> Redmine - Patch #6475 (New): Add an option to set the project name from apache when authenticatin...https://www.redmine.org/issues/64752010-09-23T12:08:16ZSergio Talens-Oliag
<p>I have some repositories that are configured with <code>SVNPath</code> instead<br />of <code>SVNParentPath</code> (I'm doing it to be able to use additional<br />authentication methods them, see issue <a class="issue tracker-3 status-1 priority-4 priority-default" title="Patch: Added FLAG to Redmine.pm to AllowAlternateAuth methods on apache (New)" href="https://www.redmine.org/issues/6414">#6414</a>).</p>
<p>With the current <code>Redmine.pm</code> code (1.0.1) the authentication against<br />Redmine fails because the <code>project_id</code> is not guessed as it should<br />(the apache <code>Location</code> points to the repository, not to it's parent<br />path).</p>
<p>To solve the problem I've patched <code>Redmine.pm</code> to allow the use of a<br />new option that adjusts the <code>project_id</code> to use; if the option is set<br />the get_project_identifier function returns that name instead of<br />calculating it from the URI and the apache location).</p>
<p>The attached patch is against an export of the redmine-1.0.1 tag.</p> Redmine - Patch #6414 (New): Added FLAG to Redmine.pm to AllowAlternateAuth methods on apachehttps://www.redmine.org/issues/64142010-09-16T11:23:00ZSergio Talens-Oliag
<p>I want to use <code>Redmine.pm</code> to authenticate users when accessing<br />subversion, but I also want to be able to authenticate non-Redmine<br />users.</p>
<p>To be able to do it I've added an additional flag to the <code>Redmine.pm</code><br />module to allow the use of multiple authentication methods.</p>
<p>The name of the flag (<code>RedmineAllowAlternateAuth</code>) has been taken from<br />the variable used on the <code>Apache2::AuthNetLDAP</code> and <code>Apache2::AuthenNIS</code><br />modules that is used for the same purpose.</p>
<p>The attached patch is against an export of the <code>redmine-1.0.1</code> tag.</p> Redmine - Patch #6177 (New): "bignum too big to convert into `long'" in migrate_from_trac.rakehttps://www.redmine.org/issues/61772010-08-19T14:43:16ZJonas Pfenniger
<p>When importing from a sqlite3 trac database, I have tons of those issues, which the patch fixes.</p>
<p>Maybe this only happens for people using sqlite3 so the patch may need some cleanup but at least it's there.</p>
<p>diff was generated with `diff -u` on the redmine-1.0.0 release (but the file didn't change since 0.9)</p> Redmine - Patch #5838 (New): add call to :view_repositories_show_contextual hook in app/views/rep...https://www.redmine.org/issues/58382010-07-08T10:41:39Zchantra .
<p>This hook is called in quite a few places, but in order to get my <a href="http://redmine.debuntu.org/projects/gitrevision-download/wiki" class="external">Git Revision Download</a> working properly, I needed to override <a class="source" href="https://www.redmine.org/projects/redmine/repository/svn/entry/trunk/app/views/repositories/revision.rhtml">source:trunk/app/views/repositories/revision.rhtml</a></p>
<p>see:</p>
<p><a class="external" href="http://redmine.debuntu.org/projects/gitrevision-download/repository/revisions/master/changes/app/views/repositories/revision.rhtml">http://redmine.debuntu.org/projects/gitrevision-download/repository/revisions/master/changes/app/views/repositories/revision.rhtml</a></p>
<p>I would appreciate to have this hook called from <a class="source" href="https://www.redmine.org/projects/redmine/repository/svn/entry/trunk/app/views/repositories/revision.rhtml">source:trunk/app/views/repositories/revision.rhtml</a> as this would prevent overriding customized redmine UI.</p>
<p>It is somehow a follow up on <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Hook for repository page (Closed)" href="https://www.redmine.org/issues/2073">#2073</a><br />Tks</p> Redmine - Patch #5530 (New): Additional hooks on top of the issue new/edit/bulk edit viewshttps://www.redmine.org/issues/55302010-05-14T15:12:38ZHolger Just
<p>This patch adds hooks on top of the new, edit and bulk edit view of issues.</p>
<p>It could be used to add some introductory text there (similar to the one on redmine.org)</p> Redmine - Patch #5510 (Resolved): Enable Mutliple Versions Per Issuehttps://www.redmine.org/issues/55102010-05-12T06:14:28ZCharlie Savage
<p>Attached is a patch against head (as of today) that enables multiple versions per issue. If there is interest, we would be happy to do what is necessary to integrate this into Redmine core. I've attached a screen shot of the issue page so people can see what it looks like.</p>
<p>There have been several past discussions about supporting multiple versions per issue - see <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add 'affected version' as a standard field (Closed)" href="https://www.redmine.org/issues/1675">#1675</a>, <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Issues fixed in multiple versions (Closed)" href="https://www.redmine.org/issues/284">#284</a>, <a class="issue tracker-2 status-1 priority-5 priority-high2" title="Feature: Feature: Allow setting multiple target-milestones (New)" href="https://www.redmine.org/issues/1266">#1266</a>.</p>
<p>In our use case, we have 60 projects, each of which has 7 phases (each a version) and work orders (each a version) and weekly development releases (global versions). Thus an issue can be added to the May 14th development release, added to Phase I and added to a work order. Basically, we find versions a great way to group issues together to a) keep track of progress b) roll up time entries c) roll up estimated times.</p>
<p>A quick over of the patch:</p>
<ul>
<li>Because it changes models, controller and views, its not really workable as a plugin</li>
</ul>
<ul>
<li>It adds a new table, issues_versions, with issue_id and version_id columns. This is a habtm relationship between versions and issues. This could be done as :has_many :through if that is preferable.</li>
</ul>
<ul>
<li>It includes migrations to setup the new table and then renames the fixed_version_id column in issues to fixed_version_id_old (so as to not delete the data). Note that as far as I can tell, rails migrations don't allow the creation of a two column habtm table with both fields as primary keys, thus part of the migration is in sql currently (tested on postgresql).</li>
</ul>
<ul>
<li>It adds a new issue_version controller modeled after issue_relation as well as the necessary controller permissions.</li>
</ul>
<ul>
<li>It updates all the various places issue.fixed_version is used (issue update form, mass edit form, move form, reports, etc).</li>
</ul>
<ul>
<li>The ugliest part of the patch is Issue#by_version since it has to repeat code from Issue#count_and_group_by which isn't flexible enough for this change.</li>
</ul>
<p>The one caveat of the patch is time reports. These reports remain unchanged if you do not group by version. But if you group by version, and add an issue to two versions, then its time is added to both versions. That is exactly the behavior we want, but it might not be appropriate in all cases. The easy way to avoid it is don't add an issue to two versions (or if you do, don't sum up the times between the two versions). Or in other words, multiple versions give a great deal more flexibility to managing a product, but you do have to understand what you are doing.</p>
<p>Like I said, if there is interest we'd like to see this integrated into Redmine core and are happy to make changes/update tests, etc. to make it happen. Note we've been running the patch in production for a couple days now, so believe it works as designed. We'll keep the patch updated against head, and fix any issues that we run into obvously.</p> Redmine - Patch #5119 (New): "User group" custom fieldhttps://www.redmine.org/issues/51192010-03-18T16:19:41ZFri Flaj
<p>This patch adds a "user group" custom field that will allow selecting one the the existing user groups tied to the active project.</p> Redmine - Patch #4878 (Resolved): More Hook Featureshttps://www.redmine.org/issues/48782010-02-18T17:28:59ZThomas Löber
<p>Hi!</p>
<p>I added some features to <code>hook.rb</code>:</p>
<ul>
<li>cleaned-up <code>call_hook</code></li>
</ul>
<ul>
<li>added an <code>:if</code> option to <code>render_on</code>, so you can write:<br /><pre>
render_on :view_issues_form_details_bottom, :partial => "test", :if => :really?</pre></li>
</ul>
<ul>
<li>added <code>render_to_string</code> to <code>ActionMailer</code> so <code>call_hook</code> can also be called from the mail templates in <code>app/views/mailer</code></li>
</ul>
<p>Unfortunately I didn't manage to write the matching test for @hook_test.rb" so far.</p> Redmine - Patch #4277 (New): Add "hide prefixed projectname from issuesubject on issuelist" settinghttps://www.redmine.org/issues/42772009-11-24T00:54:39ZMischa The Evil
<p>This issue is extracted from <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Better display of subprojects activiry and tickets. (Closed)" href="https://www.redmine.org/issues/3100">#3100</a> and it's relatives. The patch adds a new system-wide, issue-tracking setting (<code>hide_prefixed_projectname_from_issuesubject_on_issuelist</code>) which provides the administrator an option to hide the subproject name (which is prefixed in front of the issue descriptions on mainproject issue lists) completely.<br />Such a setting can be useful if the site is configured to display the <code>project</code>-column be default.</p>
<p>The default setting is equal to as it is currently(the projectnames are shown prefixed to the descriptions).</p> Redmine - Patch #4071 (New): Accept more input when replying to a ticket using e-mailhttps://www.redmine.org/issues/40712009-10-21T14:18:43ZOxan -
<p>Currently, you can only set the status field when you reply at a ticket using e-mail. This patch adds the possibility to change the priority, category, tracker, target version, done ratio, project and custom fields, with respecting the allow_override setting.</p>
<p>You can delete the target version field with setting it to 'none'. The target version is named Target and the done ratio is named Done.</p>
<p>Example mail:<br /><pre>Here your comment
Target: 0.9
Done: 50
Tracker: Defect
Priority: Low</pre></p>
<p>Diff is made against 0.8.6, but should work for trunk too.</p> Redmine - Patch #3827 (New): Allow (SVN) repository browsing in Redmine.pmhttps://www.redmine.org/issues/38272009-09-06T00:12:06ZStefan Rubner
<p>Currently, you cannot enable repository browsing (SVNListParentPath ...) when using Redmine.pm to grant/deny access to the various SVN repositories. The reason for that is that there obviously is no project_id for the svn root directory and thus, access is denied.<br />I fixed that by changing the function is_public_project in Redmine.pm like this:</p>
<pre>
sub is_public_project {
my $project_id = shift;
my $r = shift;
my $ret = 0;
if ($project_id) {
my $dbh = connect_database($r);
my $sth = $dbh->prepare(
"SELECT * FROM projects WHERE projects.identifier=? and projects.is_public=true;"
);
$sth->execute($project_id);
$ret = $sth->fetchrow_array ? 1 : 0;
$sth->finish();
$dbh->disconnect();
} else {
$ret = 1;
}
$ret;
}
<pre>
This will allow access if the project_id is empty, and use the normal access checks otherwise. I don't know whether this will have side effects on other types of repositories like git, bzr, etc.
This patch should work for the curent stable version as well as for the current trunk.</pre> Redmine - Patch #3754 (New): add some additional URL paths to robots.txthttps://www.redmine.org/issues/37542009-08-18T17:40:50Zmark burdett
<p>My apache logs show that some redmine URLs are being heavily indexed by robots, and it seems like it would be best to have them blocked by robots.txt:<br />/issues<br />/projects/*/time_entries<br />/projects/N/wiki/* (where N is the numeric project id)<br />/repositories/annotate/*<br />/repositories/browse/*<br />/repositories/changes/*<br />/repositories/diff/*<br />/repositories/entry/*</p> Redmine - Patch #3358 (New): Advanced LDAP authenticationhttps://www.redmine.org/issues/33582009-05-13T19:24:44ZDaniel Marczisovszky
<p>This patch adds the following new features to LDAP authentication:</p>
<ul>
<li>using dereferencing aliases on search</li>
<li>ability to select protocol LDAPv2 or LDAPv3</li>
<li>connect using STARTTLS</li>
<li>selecting server certificate validation level</li>
<li>user-definable custom search filter</li>
<li>bind as current user instead of admin account, see Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: LDAP - authenticate as user (Closed)" href="https://www.redmine.org/issues/1913">#1913</a></li>
<li>searching is sub-tree by default, in future GUI option may be added to configure this</li>
</ul>
<p>If custom search filter is used, <code>$login</code> is replaced with the username. For example, to search for users with objectClass posixAccount, use this filter string: @(&(uid=$login)(objectClass=posixAccount))</p>
<p>Note that this patch uses Ruby/LDAP instead of Net::LDAP, so this should be installed, for example on Debian, use <code>apt-get install libldap-ruby1.8</code></p>
<p>After applying this patch, run <code>rake db:migrate RAILS_ENV="production"</code>, as auth_sources table is modified in the database. (filter, dereference, starttls, require_cert and protocol_version columns are added)</p> Redmine - Patch #3123 (Needs feedback): Check additional mail headers when creating issues via emailhttps://www.redmine.org/issues/31232009-04-05T15:54:45ZDuncan Harris
<p>We have a setup with Redmine where users often send mail using different from addresses in the email. We use Google Apps for email, but this would apply to other mail systems where users can set up multiple from addresses in their email.</p>
<p>If users send email with a different from address than their registered one then Redmine ignores the incoming email.</p>
<p>To fix this issue I created the attached modification which checks the mail headers "Return-Path", "Sender" and finally "From" (as before) for a match to a user account.</p>
<p>The "Return-Path" header relies on getting mail server to set this to the envelope sender address. I use the preline program with qmail to get this set.</p>
<p>This works because Google Apps email (and GMail) always set the Sender and envelope sender addresses to the users main or canonical email address even if they choose a different "From" address.</p> Redmine - Patch #3117 (New): Add the possibility to select the comment field to /timelog/reporthttps://www.redmine.org/issues/31172009-04-03T13:53:28ZNicolas Maeder
<p>Sometimes, I need to see the comments in the report, so I added <strong>comment</strong> to the list of additional details</p>
<p>URL for details report: <code>/timelog/report</code></p> Redmine - Patch #2696 (New): Add subcategory to categoryhttps://www.redmine.org/issues/26962009-02-07T22:40:44ZRob Elsner
<p>This patch contains 2 migrations to add a column to issues and a table called issue_subcategories. This will allow users to have Categories, and a subcategory grouping below that.</p>
<p>I have tried to add the necessary parts for English, and use similar names for category.</p>
<p>This was diff'd against svn trunk revision 2399.</p> Redmine - Patch #2457 (Needs feedback): Different style of new issue/timelog interfacehttps://www.redmine.org/issues/24572009-01-07T13:49:09ZMischa The Evil
<p>For my own Redmine instance I modified the interface regarding the "entry-links" for new issues and new timelogs a long time ago. I used several other patches and sources to come to the final result. I always wanted to create a configurable patch for others who might be interested, but never came to it. Now, here it finally is...</p>
<p>The urge for the modifications came from the fact that I needed to have cross-project, direct-access to the new-links for both the issues and the timelogs (the only two things which a user enters frequently).</p>
I added/modified the following things:
<ul>
<li>Added setting <code>main_new_links_enabled</code> which enables the changes from this patch (defaults to 0/false) and at the same time removes the default "New issue"-tab on the project-menu</li>
<li>Added new-issue link right above the main issuelist (view: issues/index) which get rendered <code>if_authorized</code></li>
<li>Added JavaScripted top-menu items for new issue and new timelog (only rendered when the visitor is a logged-in user && the current logged-in user has at least one membership (role)) which opens dynamic-menu's (based on the project-selector) showing the projects for which the current logged-in user has a role.</li>
</ul>
As mentioned earlier I based my modifications on some other patches and contributions:
<ul>
<li>Patch <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Patch for #1003 (Closed)" href="https://www.redmine.org/issues/1022">#1022</a> (Patch for <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow "New Issue" from anywhere (Closed)" href="https://www.redmine.org/issues/1003">#1003</a> [Allow "New Issue" from anywhere]) by Rocco Stanzione; This was my starting point for this patch. I've refactored the CSS to better fit the current trunk's default theme. I've also modified the conditions under which the links are displayed.</li>
<li>Patch <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Jump-in for 'add time' (Closed)" href="https://www.redmine.org/issues/249">#249</a> (Jump-in for 'add time') by Michael Pirogov; This patch made me realize I wanted the new timelog-liks integrated just as the new issue-links. This also gave me the insights about how this could be merged with patch <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Patch for #1003 (Closed)" href="https://www.redmine.org/issues/1022">#1022</a> to implement my needs for the new timelog-links.</li>
<li><a href="http://forge.typo3.org/repositories/diff/team-forge?rev=905" class="external">Revision 905</a> of Typo3's Redmine-fork by Sebastian Kurfürst; This changeset gave me the idea and basic-code for adding the new issue-link also in the main issuelist and for removing the new-issue tab.</li>
</ul>
<p>Like stated before I've added a setting for the modifications I've made. This means that with the patch applied (but no configuration) the default behaviour/UI isn't modified. The modifications specifically needs to be configured to be used.</p>
<p>This patch is not specifically shared/posted to get integrated into the Redmine core since I think it is more a personal request to have these changes integrated rather then that it is a community one.</p>
<p>Hope someone can appreciate the patch. Just to note: I've kept the code as seperated as possible (ie duplicated lots of it for both the JavaScripted menu's, instead for combining it at a higher-level). This will allow more easy extraction of parts of this patch.</p> Redmine - Patch #2173 (Needs feedback): Update the Git repository automaticallyhttps://www.redmine.org/issues/21732008-11-13T08:03:48ZDavid Holm
<p>The Wiki suggests (<a class="external" href="http://www.redmine.org/wiki/redmine/RedmineRepositories">http://www.redmine.org/wiki/redmine/RedmineRepositories</a>) that you should set up a cron job to update the Git bare repository, the one redmine points to, automatically. This is unneccessary since you could just as easily use Git's hooking mechanism to have it automatically update the repo on each push.</p>
<p>1. chmod a+x post-receive-redmine<br />2. Put post-receive-redmine in <redmine dir>/doc/git-hooks<br />3. Change into your main git repo dir (the one you push to)<br />4. Edit ./hooks/post-receive and add a line that says ". <redmine dir>/doc/git-hooks/post-receive-redmine" <br />5. Run "git config --add hooks.redmineGitBase <base path to redmine bare repos, i.e. /var/lib/redmine/git_repos>" <br />6. You're done!</p>
<p>The script could be updated to create the bare repo if it doesn't already exist but it would need to know which permissions to change it to for redmine to read it so I didn't add this feature.</p> Redmine - Patch #2106 (New): Ability to choose period in 'Spent time' and count of watched issues...https://www.redmine.org/issues/21062008-10-29T16:47:50ZAleksei Gusev
<p>This patch add ability to choose period in 'Spent time' and count of watched issues on 'My page'.</p>
<p>Please, include it if you think this feature is useful for your. Thanks!</p> Redmine - Patch #1764 (New): Add session_config option-stubs to environment-confighttps://www.redmine.org/issues/17642008-08-11T01:56:41ZMischa The Evil
<p>This is a multi-branch (trunk and stable-0.7.3) patch which simply adds two session-related configuration-directive stubs to <em>./config/environment.rb</em>.</p>
The given stubs are for:
<ul>
<li><code>session_key</code></li>
<li><code>session_path</code></li>
</ul>
<p>I created (and provide) this patch due to the fact that one of both directives is required to run multiple Redmine (or other apps which use the same session-names as Redmine) deployments on the <strong>same domain</strong> (though <strong>seperate installs</strong> under several <strong>different sub-URI's</strong>) without suffering from <em>session-mangling</em>.<br />Both directives aren't documented (sufficiently) imho at the Redmine website or the Redmine Code-base. That is the reason why I'd propose to add something like provided with this patch. If it is not taken into the project I would propose to add an entry to the Redmine FAQ about these issues. I am volunteering already... :-)</p>
I already found some related issues and threads:
<ul>
<li><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Append suffix to cookie name (Closed)" href="https://www.redmine.org/issues/540">#540</a></li>
<li><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: login problem with 2 redmine installation on the same server (Closed)" href="https://www.redmine.org/issues/1041">#1041</a></li>
<li><a class="external" href="http://www.redmine.org/boards/2/topics/show/150#message-163">http://www.redmine.org/boards/2/topics/show/150#message-163</a></li>
</ul>
<p>Both issues contain comments which faulty "documents" the session_key directive. This faultyness is due to the fact that rake will crash if the session_key directive is used in <em>./config/enviroment.rb</em> as commented in both issues probably caused by the rake-scripts which aren't accepting Rails 2.1 syntaxis.<br />The mentioned forum-thread gives to correct syntaxis though it is mixed with another config-directive in some another case.</p>
<p><strong>Beware</strong>: This patch only adds config-stubs which solves the session-mangling behaviour in the given environment. It does not fix any related problems with the so-called autologin-cookie. I created a sepereate specific issue for that (<a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Autologin-cookie should be configurable (Closed)" href="https://www.redmine.org/issues/1763">#1763</a>).<br />See also <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Append suffix to cookie name (Closed)" href="https://www.redmine.org/issues/540">#540</a> and partly <a class="issue tracker-2 status-1 priority-3 priority-lowest" title="Feature: option to set secure flag on session and autologin cookie (New)" href="https://www.redmine.org/issues/982">#982</a> regarding the problems with the autologin-cookie.</p> Redmine - Patch #1568 (New): Added Support for htpasswd authenticationhttps://www.redmine.org/issues/15682008-07-03T12:32:24ZRobert Shell
<p>In moving from trac wanted to keep same htpasswd based authorization so passwords in sync with subversion. To do this have added new AuthSource and forms to support this.</p>
Key Changes
<ul>
<li>Added AuthSourceFile</li>
<li>Modified User to pass password to auth_source for update</li>
<li>Added passwd and passwd? methods to add/update users and passwords in auth_source</li>
<li>Change auth_sources views to support multiple subtypes</li>
</ul> Redmine - Patch #1382 (New): Add a global notification cc https://www.redmine.org/issues/13822008-06-05T07:27:21ZJames Turnbull
<p>We cc'ed all notifications to a mailing list when we were using Trac and I wanted to add the same functionality to Redmine. Attached is a patch that adds a global cc to all notifications and adds a setting, mail_cc, to the Email Notifications settings panel.</p> Redmine - Patch #691 (New): Add column totals to Issus Summary Reporthttps://www.redmine.org/issues/6912008-02-19T00:07:41ZDavid Petersen
<p>The Issue Summary Reports (simple and detailed) has row totals but does not have column totals. Both row and column totals are needed to be able to pull all the information that is needed.</p>
<p>Patch file adds the column totals.</p> Redmine - Patch #684 (New): Add journal count on issues listhttps://www.redmine.org/issues/6842008-02-18T08:26:59Zjinwoo lee
<p>I think that viewing journal count is better than nothing.<br />Because it is easy to understand issues's activity.<br />so I make this patch.</p> Redmine - Patch #239 (New): Adds two blocks for my/page and fixes a report bughttps://www.redmine.org/issues/2392007-12-07T11:11:00ZRocco Stanzione
<p>This fixes a report query filter bug where assigned_to="me", and adds two new blocks for my/page, for a manager's<br />dashboard - issues due in the next week and past due issues.</p>