Activity
From 2015-04-27 to 2015-04-29
2015-04-29
-
22:32 Patch #19742 (Closed): RedmineInstall: MySQL: collation_database
- Currently, the code sample creates a database with @collation_database=utf8_general_ci@. This potentially creates issues[1] when sorting some unicode languages. A better approach would be to specify the collation.
-
22:25 Defect #19741 (Closed): RedmineInstall: Step 9 not correct for Redmine 3.x
- Need a new bullet.
-
22:17 Defect #19711: Plugin check not working if name does not equal page
- Yes, but... a 301 redirect will be added from the old to the new address?
-
21:56 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
- Toshi MARUYAMA wrote:
> If your project tree of Redmine 3.0 is broken, it was broken in Redmine 2.6.
Ok, thank you for the quick answer. We'll try this fix. We did not have any issues in *2.6.0*. Since migrating to *3.0.1* last wee... -
19:42 Defect #18018 (Closed): Project Sorting by Name broken (for large project lists) in v2.x
- Hugues Clouâtre wrote:
> We are also seeing this issue, following a migration from *2.6.0* to *3.0.1*.
Migration from Redmine 2.6 to 3.0 does not touch :lft and :rgt of project table.
If your project tree of Redmine 3.0 is broken, i... -
18:36 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
- We are also seeing this issue, following a migration from *2.6.0* to *3.0.1*.
-
18:17 Defect #19740: "Truncate emails after one of these lines" setting is not working
- #16962#note-25
-
16:51 Defect #19740 (Closed): "Truncate emails after one of these lines" setting is not working
- This may be related to the problem reported on #19737, but along with the improper handling of Outlook emails the Truncate option doesn't appear to be working. I've tested using Outlook emails, Exchange webmail and Mozilla Thunderbird.
... -
18:15 Defect #15716: Scraped emails include CSS from HTML emails
- Note: this is still a problem as of Redmine 3.0.2. We see it often for current versions of Mac OS X and iOS. I'm still using iOS 7 on a work device, and I see the behavior with it as well.
-
16:56 Defect #19737: HTML Sanitizer not working for Outlook mails
- +1
I can confirm that Outlook emails are improperly handled:
{{collapse(View details) -
15:55 Defect #19737: HTML Sanitizer not working for Outlook mails
- This is Redmine 3.0 regression according to #19537#note-9.
-
12:41 Defect #19737 (Closed): HTML Sanitizer not working for Outlook mails
- HTML Sanitizer not working for Outlook mails.
There are some unwanted tags not stipped from the mail body. -
15:56 Defect #19537: Broken HTML sanitizer refence breaks email receiving
- Thank you for creating #19737.
-
12:39 Defect #19537: Broken HTML sanitizer refence breaks email receiving
- Ok, I will create a regression bug.
It worked in
* 2.6.x
* 3.0.1 using the gem 'rails-deprecated_sanitizer'
-
12:27 Defect #19537: Broken HTML sanitizer refence breaks email receiving
- Rupesh J wrote:
> The text striping is not handled.
> ...
Did it work on Redmine 2.x?
> Please let me know if this needs to be reported as another bug ?
If it is regression of Redmine 3.0,
please create new issue because versi... -
10:41 Defect #19537: Broken HTML sanitizer refence breaks email receiving
- The text striping is not handled.
I am getting some unwanted Outlook mail tags.
Please let me know if this needs to be reported as another bug ?
-
12:17 Defect #4608: Mail attachment name encoding is incorectly handled
- I think this issue is fixed by #12399.
-
12:13 Defect #4608 (Closed): Mail attachment name encoding is incorectly handled
- This issue is too old.
Ruby 1.8 support was dropped on Redmine 3.x. -
12:09 Patch #2059 (Closed): broken subject when submitting issue via email written in japanese
-
12:09 Patch #2059: broken subject when submitting issue via email written in japanese
- Original issue is fixed.
#2059#note-2 is duplicate of #4608. -
09:21 Defect #19735: Email addresses with slashes are not linked correctly
- RFC 2822 does not forbid to use "/".
https://www.ietf.org/rfc/rfc2822.txt -
05:44 Defect #19735 (Closed): Email addresses with slashes are not linked correctly
- Email addresses with slashes (e.g. foo/bar@example.com) are not linked correctly because Redmine does not recognize slashes in local-part of email addresses.
I use email addresses that include a slash. Such email addresses are also us... -
07:43 Feature #15225 (Closed): Need to be able to have separate markup formats for bugs and wiki pages
- I am closing this issue as a duplicate of #5112.
-
07:34 Feature #12588 (Closed): Text Formatting should be able to be applied beyond a paragraph
- I am closing this issue as a duplicate of #3888.
-
07:09 Feature #13588 (Closed): Make long-text and string fields textilizable by default
- Implemented by #1179 (Redmine 2.5).
You can enable/disable text formatting for each custom fields. -
06:42 Defect #13726 (Closed): Link not clickable
- Fixed by #18349 (Redmine 2.6.1).
-
03:37 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- I cloned the production box I tried to upgrade earlier and manually removed the @email_addresses@ table. I then went back through the process from the beginning and am now running the 3.0.2 version of Redmine on the clone. I'm going to k...
2015-04-28
-
22:23 Feature #19732 (Closed): create subtask from mail
-
20:37 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- Deoren Moor wrote:
> I'll diff them to see if there are any other tables still hanging around from the failed 3.0.1 upgrade.
I just found the one table when I compared them. -
20:17 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- Thanks for the follow-up. I went back and compared a database backup taken the day before a previous failed 3.0.1 backup and the day after and found that is when the table first appeared. I was operating under a bad assumption that the @...
-
16:02 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- It seems your entries were created by Redmine.
source:tags/3.0.2/db/migrate/20150113211532_populate_email_addresses.rb
I think there is inconsistency in "schema_migrations".
http://www.redmine.org/boards/2/topics/46173?r=46179#messa... -
15:53 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- Toshi MARUYAMA wrote:
> Thank you for your feedback.
> ...
I checked and the table has 205 entries.
@mysql> describe email_addresses;@ -
15:42 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- There is same post: message#46173.
-
15:38 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- Thank you for your feedback.
If you have no idea who created "email_addresses" table,
you can drop or rename this table.
Ensure you have backup and table has no data. -
15:29 Defect #19721: Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- Toshi MARUYAMA wrote:
> I think your plugin created "email_addresses" table.
Thank you for your feedback. We are running a vanilla installation with no plugins installed.
From the info page: -
06:41 Defect #19721 (Needs feedback): Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- I think your plugin created "email_addresses" table.
-
06:07 Defect #19721 (Closed): Upgrade from 2.6.4 to 3.0.2 fails with Mysql2::Error: Table 'email_addresses' already exists:
- I started with a working Redmine 2.6.4 installation on an Ubuntu 12.04 LTS box with Ruby 1.8.7. These are the steps I took in my attempt to upgrade to Redmine 3.0.2:
# @apt-get install ruby1.9.3 -y@
# @apt-get remove ruby1.8 ruby1.8-... -
19:36 Defect #19731 (Closed): Issue validation fails if % done field is deactivated
- Creating a new issue fails with a validation message "% done is not valid" when then field has been removed for the tracker.
Temporarely solved the problem by changing issue.rb: -
15:49 Defect #19729 (Closed): create task from message
- Please use forum for questions.
-
14:25 Defect #19729 (Closed): create task from message
- Receiving messages works. But when I create a task, not all items are filled in. But I fill out all the items in the message.
-
11:17 Defect #19542 (New): [Email Notifications] Email are not sent according to user settings
- I have no idea.
-
09:21 Defect #19542: [Email Notifications] Email are not sent according to user settings
-
08:40 Defect #19542 (Needs feedback): [Email Notifications] Email are not sent according to user settings
- Read [[Submissions]].
-
08:53 Defect #2316: Problem tags with email issues.
- You should use user language or default language.
source:tags/3.0.2/app/models/mail_handler.rb#L336 -
08:19 Defect #2316: Problem tags with email issues.
- I'm on Redmine 3.0.1.
I too am seeing tracker and priority not being updated after Redmine server received the email.
The server will update Status and Assignee.
MTA has ...unknown_user=ignore allow_override=tracker,priority,sta... -
08:46 Feature #9479: Add a custom filtered issues block to 'My page'
- Duplicate of #1565?
-
06:57 Defect #19398: Failed to get attachment with Chinese filename.
- You can use Rails 4-2-stable branch to change Gemfile.
-
06:53 Defect #19398 (Closed): Failed to get attachment with Chinese filename.
- Rails 4.2.2 will fix.
https://github.com/rails/rails/commit/4df216cb12e35c09ae5ec271755e581d692d0326#diff-6897a0b59abaaa3bbc85da93757c39d9L32 -
04:37 Defect #19398 (Reopened): Failed to get attachment with Chinese filename.
- The problem comes back after upgrading to 3.0.2 & fixed by adding the same code in C:\Ruby193\lib\ruby\gems\1.9.1\gems\actionpack-4.2.1\lib\action_dispatch\middleware\static.rb
-
06:45 Defect #19185: Update Install/Upgrade guide for 3.x version and get gid of DEPRECATION WARNING: You didn't set config.secret_key_base
- I have updated wikis.
* http://www.redmine.org/projects/redmine/wiki/RedmineInstall/243
* http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade/75 -
05:48 Feature #19720 (Closed): Create a issue on the mail problem
- Please use forum for questions.
-
05:33 Feature #19720 (Closed): Create a issue on the mail problem
- Requirements: when the message create issue, the message subject is or not repeated for issue list
Now the development progress:
1.The script successfully with imap
( rake -f /opt/redmine/web/Rakefile redmine:email:receive_imap RAIL...
2015-04-27
-
17:20 Feature #8016: Drag-and-drop issue (ticket) ordering
- See also: #9184...
Would like this for the purposes of re-ranking a list. I use a custom field ("Rank") to order my list by priority. It is supremely time consuming to edit each ticket individually when priorities change. -
16:24
Feature #8016: Drag-and-drop issue (ticket) ordering
- +1
-
16:34 Feature #973: Assign different status sets and workflows for separate projects
- +1 it is highly desirable feature for multy-project deployments.
-
16:21 Feature #19718 (New): GANTT; zoom backwards: half-year granularity
- The Redmine software is delivered with a GANTT diagramme for which the zoom functionality makes it possible to choose the granualirty between Day, Week or Month. This is great but for projects covering several years, it would be nice to ...
-
15:07 Patch #2268: Patch to show Total Estimated Time at the bottom of each list of issues.
- To clarify - the previous post by Muhammad Azmi contains the current version of our patches to show estimated time totals on groups and at the foot of pages as originally described.
-
12:05
Patch #2268: Patch to show Total Estimated Time at the bottom of each list of issues.
- Hi All,
This patch is work on redmine 2.6.4.
Regards
-
12:20 Defect #19273: acts_as_searchable.rb only seems to be case insensitive if postgresql
- I don't know if it's related, but when running the test suite against PostgreSQL, this test fails:
-
08:54 Defect #19482: Custom field (long text format) displayed even if empty
- Thanks for the fix!
Best regards,
Oana -
07:52 Feature #19458: Add the ability to expire passwords after a configurable number of days
- Could it be included in next version?
-
06:09 Patch #19520: LDAP authentication exception handling
- I don't like catching all exception in controller.
I think it is better catching in model.