Activity
From 2017-07-22 to 2017-07-24
2017-07-24
-
22:44 Defect #26507: "attachment:filename" link syntax would not work if the file name contains "@"
- I can work on this, but the fix will be based on the one from #26443.
-
06:32 Defect #26507 (Closed): "attachment:filename" link syntax would not work if the file name contains "@"
- A file name which contains "@" is treated as email address.
Probably all versions that support "attachment:filename" syntax are affected. redmine.org is also affected. Please see this example: attachment:wrong-attachment-link@2x.png
... -
22:34 Defect #26515: Email not being sent for NEW issues using async_smtp AND non-standard emission address
- #8157 relates to sending emails if one of the recipient emails is wrong. This is different and very specific. It only occurs if you have two projects with 2 inbound emails, 1 where the standard redmine emission email is the same as the i...
-
18:47 Defect #26515 (Needs feedback): Email not being sent for NEW issues using async_smtp AND non-standard emission address
- What difference with #8157?
-
17:45 Defect #26515 (Closed): Email not being sent for NEW issues using async_smtp AND non-standard emission address
- This is similar to an old issue about async_smtp mail. To reproduce -
Project A - setup with inbound/outbound email the same like tracker@example.com
Project B - setup with inbound email like test@example.com but outbound the same t... -
21:30 Defect #26504: Rails 5 unit and functional tests
- Should we move the tests to the new models, controllers... folders?
-
19:42 Defect #26376: Wrong issue counts and spent time on project overview
- I just want to mention that I have the same problem with the following environment (on Ubuntu 16.04.2 LTS):
-
19:15 Defect #26513 (Closed): Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
- Fixed in r16877.
-
16:12 Defect #26513: Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
- A workaround for this issue.
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#autoloading-is-disabled-after-booting-in-the-production-environment -
15:57 Defect #26513 (Confirmed): Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
- Confirmed the problem.
-
15:38 Defect #26513 (Closed): Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
-
19:11 Defect #26506: User link syntax causes an exception while sending email notification on Rails 5.1
- Jean-Philippe Lang wrote:
> This should be fixed in r16876 by using @_url@ helper instead of @_path@ like in other @link_to_@ methods. It also fixed that generated links to users were missing the host name.
Thanks Jean-Philippe Lang ... -
19:00 Defect #26506 (Closed): User link syntax causes an exception while sending email notification on Rails 5.1
- This should be fixed in r16876 by using @_url@ helper instead of @_path@ like in other @link_to_@ methods. It also fixed that generated links to users were missing the host name.
-
14:26 Defect #26506: User link syntax causes an exception while sending email notification on Rails 5.1
- Go MAEDA wrote:
> Marius BALTEANU wrote:
> ...
Unfortunately some tests fail because of the fix.
{{collapse(error log) -
12:01 Defect #26506: User link syntax causes an exception while sending email notification on Rails 5.1
- Marius BALTEANU wrote:
> Adding "include Rails.application.routes.url_helpers" to ApplicationHelper fixes the issue, but still I'm not sure that is the best solution.
> ...
The issue was fixed by your patch.
Thank you for inspecting i... -
10:05 Defect #26506: User link syntax causes an exception while sending email notification on Rails 5.1
- Adding "include Rails.application.routes.url_helpers" to ApplicationHelper fixes the issue, but still I'm not sure that is the best solution.
-
09:19 Defect #26506: User link syntax causes an exception while sending email notification on Rails 5.1
- Indeed, I'm able to reproduce the issue, but I'm not sure how to fix it.
-
05:41 Defect #26506 (Closed): User link syntax causes an exception while sending email notification on Rails 5.1
- Steps to reproduce:
# Open "New issue" page.
# Enter something in the subject field.
# Enter "@admin" in the description field.
# Press "Create" button. You will see "NoMethodError" exception (please see the attached screenshot).
... -
18:32 Patch #26514: German translation for 404-error-page is semantically not correct and misleading
- +1 LGTM
-
16:50 Patch #26514: German translation for 404-error-page is semantically not correct and misleading
- Any feedback?
-
16:06 Patch #26514 (Closed): German translation for 404-error-page is semantically not correct and misleading
- The german translation for the server's page-request-reply *404* is not correct and misleading. While the english statement describes that the page is missing or has been removed, the german translation tells the user that _"the attachme...
-
16:45 Defect #26508: excel have wrong column name at custom field
- Randa Bustami wrote:
> sorry i didn't get your point, u means i have to delete all the plugins i installed ( see attached pic)
Yes. But on test environment. -
15:50 Defect #26508: excel have wrong column name at custom field
- sorry i didn't get your point, u means i have to delete all the plugins i installed ( see attached pic)
-
15:43 Defect #26508: excel have wrong column name at custom field
- Try without plugins because Redmine core does not provide i18n custom fields feature.
-
14:04 Defect #26508: excel have wrong column name at custom field
- attached screenshot for our redmine version
do u need anything else pls ?
-
13:49 Defect #26508 (Needs feedback): excel have wrong column name at custom field
- Please see [[submissions]].
-
10:35 Defect #26508 (Needs feedback): excel have wrong column name at custom field
- i had added some custom fields , but when i export to excel it display beside the name of the field " translation missing: en."
pls check attached image
-
13:15 Feature #26491: mark incomplete total sums as such
- There are many areas today where displayed items are filtered, in fact, its everywhere. Issue are filtered in the roadmap, time entries are filtered in the reports, ... As for time entries, there is even a separate permission to allow us...
-
12:25 Feature #26184: wiki page in project top page
- ok that is feature, and if takes time then can you please tell me how can i just set my one wiki page on my home page (redmine 3.x)?
I googled much for find how to set wiki page as my home page on remine version 3.2.1, but as per i ... -
11:56 Defect #26509: Page layout went crazy when migrating to 3.4.2.stable
- Go MAEDA wrote:
> Please reload the page using CTRL + F5.
I love you Go MAEDA! I'm so silly I failed to realize it was just a cache problem. ^^
-
11:50 Defect #26509 (Closed): Page layout went crazy when migrating to 3.4.2.stable
- Please reload the page using CTRL + F5.
-
11:07 Defect #26509 (Resolved): Page layout went crazy when migrating to 3.4.2.stable
- Sorry, it doesn't belong to issues but to Help Forums,
-
11:04 Defect #26509 (Closed): Page layout went crazy when migrating to 3.4.2.stable
- Something wrong with styles/css? Menu layout is a complete mess... as you can see in attached picture.
!Capture.PNG!
Environment:
Redmine version 3.4.2.stable
Ruby version 2.3.3-p222 (2016-11-... -
10:04 Feature #4939: List of tasks filtered as OR and not AND
- +1
-
09:49 Patch #26500 (Closed): Japanese translation update (r16833)
- Committed in trunk r16875, thanks.
-
02:34 Feature #23630: Migrate to Rails 5.2
- Good News and I am looking forward to this new version. Thank you so much!
Jean-Philippe Lang wrote:
> The migration to Rails 5.1.2 is complete and will be merged in trunk very soon.
-
00:22 Defect #26443: User link syntax (user:login) doesn't work for logins consisting of an email adress
- The attached patch fixes both issues.
Because I couldn't modify the regex to ignore the emails that starts with "@" or "user:", I chose to use the same logic from markdown formatting also for textile.
@Mischa, when I've implemente...
2017-07-23
-
19:23 Defect #26504: Rails 5 unit and functional tests
- I have committed r16873.
-
19:08 Defect #26504 (Closed): Rails 5 unit and functional tests
- On trunk r16872, "rake test:units" and "rake test:functionals" cannot run.
Rails 5 changes directories.
* test/unit -> test/models
* test/functional -> test/controllers
http://guides.rubyonrails.org/testing.html#rails-sets-... -
18:48 Feature #23630 (Closed): Migrate to Rails 5.2
-
12:41 Feature #23630: Migrate to Rails 5.2
- The migration to Rails 5.1.2 is complete and will be merged in trunk very soon.
-
18:14 Patch #26323 (Closed): Remove ActiveRecord workaround (fixed in Rails 5)
-
16:58 Patch #26503 (Closed): Update nokogiri gem (~> 1.8.0)
- Now we can update Nokogiri to 1.8.0 because Ruby 2.1 support has been dropped by #25538 and #23630.
Quotation from "CHANGELOG of Nokogiri 1.8.0":https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md#180--2017-06-04 :
b... -
13:42 Feature #25807 (Closed): Upgrade to roadie-rails 1.2
-
13:38 Feature #25538 (Closed): Drop support for Ruby 2.2.1 and ealier, 2.2.2+ is now required
-
13:38 Feature #19755 (Closed): Drop protected_attributes gem
-
12:38 Defect #26499 (Closed): DEPRECATION WARNING due to changes in dirty attributes methods in Rails 5.1
- No more deprecation warnings when running tests or database migration.
-
11:02 Defect #26499: DEPRECATION WARNING due to changes in dirty attributes methods in Rails 5.1
- Yes, not only in migrations but pretty much everywhere. I'm working on this.
-
02:48 Defect #26499 (Closed): DEPRECATION WARNING due to changes in dirty attributes methods in Rails 5.1
- A lot of DEPRECATION WARNING messages are displayed while running @rake db:migrate@ (please see the attached file).
This is due to a change of Rails: https://github.com/rails/rails/pull/25337#issuecomment-225166796 -
07:49 Patch #26501 (Closed): Change English translation for setting_issue_list_default_columns
- I found inconsistent English translation. Please see the attached screenshot.
This patch changes English translation for setting_issue_list_default_columns to "Issues list defaults".
!{width: 460px;}.inconsistent-translation@2x.png! -
06:44 Patch #26500 (Closed): Japanese translation update (r16833)
- Translated the following strings:
* error_exceeds_maximum_hours_per_day
* setting_time_entry_list_defaults
* setting_timelog_accept_0_hours
* setting_timelog_max_hours_per_day
2017-07-22
-
18:38 Feature #7349: Per-project email notification settings
- +
need ability to specify different mail-from address for different projects
Is this plugin actual? https://github.com/ajwalters/redmine_project_specific_email_sender -
12:49 Defect #26498 (Closed): Rails5: scm entry *.html causes 404 Not Found
- Fixed, thanks for pointing this out.
-
12:38 Defect #26498 (Closed): Rails5: scm entry *.html causes 404 Not Found
- source:trunk/public/404.html
r16848: -
12:39 Feature #20366: upgrade jquery-rails to 4.0
- As Redmine 3.4 bundles jquery-ujs, we could simply remove the gem dependency in 3.4. Would it help?
-
12:33 Feature #20366 (Closed): upgrade jquery-rails to 4.0
- jquery-rails won't be no longer used in Redmine 4 as Rails does not rely on jquery for its UJS any more.
The gem dependency is removed in r16850. -
09:12 Patch #26492 (Closed): % is not valid without a format specifier
-
08:40 Patch #26492 (Resolved): % is not valid without a format specifier
- Patch committed, thanks.
-
07:54 Patch #26492: % is not valid without a format specifier
- Certainly "%%" is correct to display a percent sign itself in sprintf format string.
Setting target version to 3.4.3. -
09:12 Defect #26468 (Closed): Using custom fields of type "File" leads to unsolvable error if filetype is not allowed
-
09:11 Defect #26471 (Closed): Issue Query: inconsistency between spent_hours sum and sum of shown spent_hours values
-
09:09 Defect #26403 (Resolved): The second and subsequent lines of commit messages are not displayed in repository browser
- r16843 restores the same behaviour as 3.3 for displaying commit messages in the revision list.
-
08:42 Patch #26395 (Closed): Jump to project autocomplete: focus selected project
- Committed, thanks.
-
08:31 Feature #26488: Project settings : Move issue tracking settings to their own tab
- Jean-Philippe Lang wrote:
> I think we should remove the Modules tab and leave the modules below the project form just like it is when creating a new project.
+1