Activity
From 2017-07-23 to 2017-07-25
2017-07-25
-
22:45 Feature #26531 (New): Sections in issue fields
- For the moment, you can create custom fields for your trackers. When you add a lot of them, it can become painful to ...
-
22:45 Defect #26507: "attachment:filename" link syntax would not work if the file name contains "@"
- Go MAEDA wrote:
> Sounds great. I set the target version of #26443 to 3.4.3. Could you write a patch?
Here it is.... -
09:46 Defect #26507: "attachment:filename" link syntax would not work if the file name contains "@"
- Marius BALTEANU wrote:
> I can work on this, but the fix will be based on the one from #26443.
Sounds great. I se... -
21:25 Feature #26530 (New): Links to Wiki pages of unauthorized projects should be smarter
- I use to define a 'Sidebar' wiki page that contains links to wiki pages in various subprojects. This allows users to ...
-
19:33 Patch #26391 (Closed): Drop Darcs SCM support
- Patch committed, thanks.
-
19:29 Patch #26503 (Closed): Update nokogiri gem (~> 1.8.0)
- Committed, thanks.
-
19:25 Defect #26518 (Closed): Rails 5: Adding a block in My Page causes "Invalid form authenticity token."
- This is fixed by r16884. We now use jquery-ujs instead of the vanilla javascript ujs provided with rails 5.
-
04:40 Defect #26518: Rails 5: Adding a block in My Page causes "Invalid form authenticity token."
- A quick workaround.
-
04:09 Defect #26518 (Closed): Rails 5: Adding a block in My Page causes "Invalid form authenticity token."
- Steps to reproduce:
1. Open "My Page".
2. Add an any block. You will see "Invalid form authenticity token."
... -
19:03 Feature #26521 (Needs feedback): Identify over-allocated resource
- Please describe more details.
-
11:34 Feature #26521 (Needs feedback): Identify over-allocated resource
- To identify the over allocated resources, and improve the planification and the Gantt project
-
18:00 Defect #26513: Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
- Pavel Rosický wrote:
> @toshi it should be only a temporarly solution
>
> all classes should be explicitly requir... -
16:13 Defect #26513: Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
- @toshi it should be only a temporarly solution
all classes should be explicitly required or eager-loaded on produc... -
15:48 Defect #26513: Rails5: production env: NameError (uninitialized constant Redmine::SortCriteria)
- I tried this....
-
17:03 Feature #17801: When adding watchers to an issue, you should have the possibility to notify the watchers that they have been added to the issue
- related to #1757
-
17:02 Feature #26529: Email notification when watcher is added and removed
- duplicates #1757
-
16:05 Feature #26529 (New): Email notification when watcher is added and removed
-
15:51 Feature #26529: Email notification when watcher is added and removed
- Currently, when I enter or remove an watchers on the task (issue) he is not notified by email....
-
15:46 Feature #26529 (Needs feedback): Email notification when watcher is added and removed
- Please describe more details.
-
15:44 Feature #26529 (Closed): Email notification when watcher is added and removed
- Allow observers to be warned when they are inserted or removed from a task.
-
15:49 Defect #26524 (Closed): Redmine 500 error
- Fixed by r16881.
-
12:20 Defect #26524 (Confirmed): Redmine 500 error
- This error occurs in production mode like #26513.
Here is a workaround.... -
11:43 Defect #26524 (Closed): Redmine 500 error
- ...
-
15:33 Feature #4511: Allow adding user groups as watchers for issues
- +1
-
13:06 Feature #4511: Allow adding user groups as watchers for issues
- Andreas,
I just had a look into that, and found that the @ActiveRecord_Associations_CollectionProxy@ object does r... -
14:08 Defect #26526 (Closed): Rails 5: production env: Search engine returns 500 error
- Committed in trunk r16879, thanks.
-
13:09 Defect #26526: Rails 5: production env: Search engine returns 500 error
- Workaround:...
-
13:04 Defect #26526 (Closed): Rails 5: production env: Search engine returns 500 error
- ...
-
14:02 Feature #26527 (Closed): Show previous comment version when editing an issue comment
- I am able to edit an issue comment. I want to give this right to the other users too. But currently there is nowhere ...
-
12:49 Feature #16045: Add "Author / Previous assignee" group to assignee dropdown in issue form
- suggestions for specs
h2. Test Plan
h3. Edit Issue
# open issue edit form
# use select box
# expect: last ... -
12:38 Feature #16045: Add "Author / Previous assignee" group to assignee dropdown in issue form
- Luka Lüdicke wrote:
> If you like it and want to include it, I can make a "cleaner" diff and add a unit test for the... -
11:57 Feature #26525 (New): Add ability to configure the number of weeks to display on Calendar block in My Page
- In the current version, only the current week is displayed on Calendar block. But it is inconvenient on weekends beca...
-
11:43 Patch #26522 (Closed): Repository routing bug when file path starts with (browse|entry|raw|changes|annotate|diff)/
- If the first component of a path in a repository equals one of the strings above, the wrong route gets selected in th...
-
10:27 Feature #20481: Gantt: right and left resizable panel
- There were some minor problems with the previous version, so I fixed it.
-
10:22 Defect #26520: Blank "Issue" field on the "Log time" from the "Spent time - Details" page for an issue
- Thank you for the workaround. I was looking into this literally at the same time :). This change is the culprit - r15...
-
09:59 Defect #26520: Blank "Issue" field on the "Log time" from the "Spent time - Details" page for an issue
- Workaround:...
-
09:53 Defect #26520: Blank "Issue" field on the "Log time" from the "Spent time - Details" page for an issue
- The link URL is generated by the `_new_time_entry_path` helper method, but no issue id is given to the method even if...
-
09:39 Defect #26520: Blank "Issue" field on the "Log time" from the "Spent time - Details" page for an issue
- > Confirmed versions with expected behavior:
>
> Redmine 3.2.0
>
> At the step 12, the link URL is generated fo... -
09:38 Defect #26520 (Closed): Blank "Issue" field on the "Log time" from the "Spent time - Details" page for an issue
- When I tried to log time from a "Spent time - Details" page (like https://example.com/projects/project-identifier/tim...
-
10:12 Defect #26508: excel have wrong column name at custom field
- thank you for your feedback , but what is the relation between plugins and the custom fields ?
i notice this problem... -
09:43 Defect #26443: User link syntax (user:login) doesn't work for logins consisting of an email adress
- The patch attached in #26443#note-3 fixes this issue properly on the current trunk and 3.4-stable.
Setting target ve... -
07:18 Patch #26519 (Closed): Bulgarian translation
- Translated news strings, related to #24005
* error_exceeds_maximum_hours_per_day
* setting_time_entry_list_defaults... -
06:29 Defect #26504: Rails 5 unit and functional tests
- Toshi MARUYAMA wrote:
> But "Japanese document":https://railsguides.jp/testing.html#rake%E3%82%BF%E3%82%B9%E3%82%AF%... -
06:26 Defect #26504: Rails 5 unit and functional tests
- Jean-Philippe Lang wrote:
> Should we move the tests to the new models, controllers... folders?
I don't know.
Bu...
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:filenam... -
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...
-
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 ema... -
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-afte... -
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 @... -
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 fi...
-
14:26 Defect #26506: User link syntax causes an exception while sending email notification on Rails 5.1
- Go MAEDA wrote:
> Marius BALTEANU wrote:
> > Adding "include Rails.application.routes.url_helpers" to ApplicationHe... -
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,... -
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 th...
-
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 des... -
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 sta...
-
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 att... -
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 mi...
-
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 roa...
-
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...
-
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 ... -
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.PN... -
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 migratio... -
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 "...
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/un... -
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... -
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).
... -
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... -
06:44 Patch #26500 (Closed): Japanese translation update (r16833)
- Translated the following strings:
* error_exceeds_maximum_hours_per_day
* setting_time_entry_list_defaults
* set...
Also available in: Atom