Redmine: Issueshttps://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292014-09-10T11:44:31ZRedmine
Redmine Redmine - Defect #17830 (New): User creation: clear/plaintext password sent via unencrypted emailhttps://www.redmine.org/issues/178302014-09-10T11:44:31ZHendrik Jaeger
<pre>
henk | I just received an unencrypted mail from redmine containing my password in plaintext. Is that fixed in more recent versions? Is there a way to fix it in 1.4.4?
henk | https://twitter.com/RamsayDev/status/460048737994551296 hehe, yeah, kinda my thoughts …
salvor | henk: no.
salvor | henk: that's only on user creation, and it's up to the administrator to send this password or not
salvor | after that everything happen through tokens
henk | salvor: hm, ok, that’s not too bad then, but I still wonder why that’s not done through tokens as well?!
salvor | I guess we could do that even on user creation (= send a unique link to reset the password) ; or force password change on first connection (which is the same security wise I think)
salvor | do you see a legitimate case where an administrator would want to set a password manually for a user ?
henk | salvor: No, not really. IMHO it’s nice to have that feature and I wouldn’t want it to go away, but it’s not a good default way to handle things.
salvor | I totally agree
</pre>
<p>Another idea:<br />allow specifying a pgp-key and send the mail encrypted</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 #13927 (New): Reduce coupling between plugins and the "plugins/" directoryhttps://www.redmine.org/issues/139272013-05-02T10:54:01ZJean-Baptiste Barth
<p>Today plugins are just directories in <code><redmine root>/plugins/</code> directory. There are a few implicit assumptions in Redmine code that this is the case, which doesn't add much benefit I think. This reference is needed in the plugin discovery mechanism, but I can see obvious reasons why it may appear anywhere else.</p>
<p>It has at least one disadvantage: it prevents from easily distributing plugins as gems or via an other mechanism (which I think has a long list of advantages that I could enumerate an other day).</p>
<p>An other motivation is that removing this would lead to clearer code I think, we could remove some <code>Dir.glob</code> and <code>File.xxx</code> calls in favor of new, clear methods in <code>Redmine::Plugin</code>.</p>
<p>I'll try to work on that and link commit to this issue.</p> Redmine - Patch #13413 (New): Let users choose how many days in advance they want to receive issu...https://www.redmine.org/issues/134132013-03-09T17:15:40ZJan from Planio www.plan.io
<p>Here at <a href="http://plan.io/redmine-hosting" class="external">Planio Hosted Redmine</a>, we've recently activated our version of the issue due date reminders that can be triggered via the <code>redmine:send_reminders</code> rake task.</p>
<p>Our users told us that they'd like to set the number of days before such reminders themselves individually rather than obeying the default set by the admin. Here's a patch for this against Redmine 1.4.7 that should be easily portable to current trunk. It doesn't contain tests in itself, just fixes the fixtures to keep current tests running.</p> Redmine - Defect #12146 (Confirmed): Required (list-, user- or version) custom field "fixed versi...https://www.redmine.org/issues/121462012-10-18T00:21:01ZMateus Anacleto
<p>I created a custom field (type Version) called "fixed version" to be filled in at the close of a task.</p>
<p>Using a workshop to force a filled in field based on the situation:</p>
<table>
<tr>
<td>Type</td>
<td>Situation</td>
<td>Status</td>
</tr>
<tr>
<td>Custom Field Version with Multiple values</td>
<td> new</td>
<td> not required</td>
</tr>
<tr>
<td>Custom Field Version with Multiple values</td>
<td> closed</td>
<td> required</td>
</tr>
</table>
<p>If the task was created with a situation when the field is not required (new) and you change for a situation that the field is required (closed), the rule don´t work and allows saving without filling in the field that should be required in this situation.</p>
<p>Environment:<br /> Redmine version 2.1.2.stable<br /> Ruby version 1.8.7 (x86_64-linux)<br /> Rails version 3.2.6<br /> Environment production<br /> Database adapter MySQL<br />Redmine plugins:<br /> redmine_inline_attach_screenshot 0.4.2</p> Redmine - Defect #6324 (New): requires_redmine_plugin should defer loading plugins if not all dep...https://www.redmine.org/issues/63242010-09-07T20:01:07ZTim Felgentreff
<p>requires_redmine_plugin is a nice facility to track inter-plugin dependencies, however, it is useless if I do not want (or cannot) rename plugins I depend on.</p>
<p>I propose that plugins are deferred and loaded at a later time, if possible.<br />See attached patch for a proposed solution.</p> Redmine - Defect #4073 (Confirmed): Editing/deleting cross-projects custom query mistakenly redir...https://www.redmine.org/issues/40732009-10-21T15:56:43ZS Reid
<p>If I delete a custom query, the project menu dissapears until I navigate to another page and back again (browser refresh does not work).</p>