Activity
From 2018-06-17 to 2018-06-19
2018-06-19
-
19:55 Patch #29045: Change Japanese translation for Tracker
- It's right that fields depend on the tracker.
But I think first about the workflow when I add a new tracker.
I create new tracker when there is no appropriate workflow,
but I don't create only because the appropriate field set doesn't... -
19:17 Patch #29045: Change Japanese translation for Tracker
- I think that it is better for the Japanese display of Tracker to be unified by "チケット種別" without mixing "チケット種別" and "種別".
The reason is as follows
In order not to be misunderstood, consistency of the terms is necessary.
"種別" and... -
16:34 Patch #29045: Change Japanese translation for Tracker
- +1
-
10:36 Patch #29045: Change Japanese translation for Tracker
- +1
I also think the change should be made because it is easier to understand. -
08:42 Patch #29045: Change Japanese translation for Tracker
- Goh Matsumoto wrote:
> In my opinion, the tracker expresses workflow's name or type.
> ...
Thank you for your feedback. But I still prefer "チケット種別" than "ワークフロー種別". The reasons are as follows:
* A tracker defines not only workflow b... -
08:06 Patch #29045: Change Japanese translation for Tracker
- -> #29045-11
Workflows are set to every tracker, and, property-sets are also set to every tracker.
Thus, the name of tracker depends on which materials are to be enphasized for our users.
Most users are not very aware of workflows... -
06:06 Patch #29045: Change Japanese translation for Tracker
- I agree that "トラッカー" isn't well known in Japan
and many Japanese can't imagine the meanings.
But..
What's the difference between the tracker and the category?
Does the tracker express the issue's type?
In my opinion, the tracker... -
05:01 Patch #29045: Change Japanese translation for Tracker
- +1
I would like the unification of "Roadmap/ロードマップ" and "Version/バージョン" related to this issue. -
03:57 Patch #29045: Change Japanese translation for Tracker
- +1
I also agree with this fix. -
01:26 Patch #29045: Change Japanese translation for Tracker
- +1
-
00:39 Patch #29045: Change Japanese translation for Tracker
- +1
"The tracker" explained the kind of the form.
I thought that was troublesome every time. -
16:41 Defect #29069 (Needs feedback): API reports wrong date for time spent if issue start date is greater than spent_on date
- If time is entered on a date prior to an issue's start date, the API reports the start date of the issue in the XML response, not the "spent_on" date entered into the time commit.
Environment:
Redmine version 3.2.6.s... -
16:19 Defect #29068 (Closed): [Redmine 3.4.5] - Assignee is removed
- All,
When moving an issue to "Assigned" (from New for instance), the "assignee to" field is erased.
The user has to update twice the issue to assigned the correct person.
Here is an example of history message:
"
Assigned to... -
14:00 Defect #29055 (Closed): Searching for issue number with REST API redirects to issue HTML page
- Search REST API queries matching issue number (with or without "#") are being redirected to HTML issue page if the issue exists.
The redirect is caused by quick jump to issue at source:/tags/3.3.0/app/controllers/search_controller.rb#L4... -
13:28 Feature #11969: Subtask display fields
- +1
-
12:00 Feature #29053 (Closed): Add check/unchek all icon in "Email notifications" section on "My account" page
- "Email notifications" section on "My account" page, you can select which project notifications to receive if you choose "For any event on the selected projects only...".
you cannot select/deselect all projects at once because there is... -
11:16 Feature #29048: Wiki page permission level
- Gregor Schmidt wrote:
> Did you consider using multiple projects and cross-project wiki links?
It can be a solution but I have lot of project active and in some cases I have only few pages to lock, then I will have so many project to m... -
08:56 Feature #16410: Bulk delete wiki attachments
- This patch adds features similar to #13072 to the wiki.
!changed_wiki.png! -
02:49 Defect #28925: Custom field values for enumerations not saved
- Mizuki ISHIKAWA wrote:
> I did not know available_custom_fields. I think that the code you propose is good.
Thank you for reviewing the change I suggested in #28925#note-5. I have slightly changed your patch.
Setting target versio... -
01:45 Defect #28925: Custom field values for enumerations not saved
- Go MAEDA wrote:
> Maybe we can use @available_custom_fields@ to collect ids of custom fields. I think the following change can make the patch simpler and faster. Mizuki, do you think it is correct?
> ...
I did not know available_custom... -
01:14 Feature #23555: Add cancel button to create/edit item page (issues, files, news, etc.)
- Jean-Philippe Lang wrote:
> Thanks for the patch Marius but linking to @url_for(:back)@ does not work after a validation error:
> ...
I think I've found a solution to this issue and I've attached a patch to #8888 to validate the implem... -
01:11 Feature #8888: Add a link / button to get back to the Issue/Time tracking screen from the "Log time" screen
- I think I've found a solution to avoid the problem reported by Jean-Philippe Lang in #23555#note-6. The "Cancel" link added by the attached patch works as expected from my tests.
-
00:53 Patch #3195: issue's start date could be the latest due date of predecessors
- My bad, I made a mistake and I wasn't aware that it is possible to set negative values in the delay field.
Still, I consider not so transparent for users that hardcoded "+ 1". For me, filling 0 in the delay field and receiving the sta...
2018-06-18
-
21:36 Feature #29048: Wiki page permission level
- Did you consider using multiple projects and cross-project wiki links?
-
18:42 Feature #29048: Wiki page permission level
- User with lover level will see pages of high level and not vice versa
-
18:36 Feature #29048 (New): Wiki page permission level
- I would like to set different permission level in a wiki page.
i.e:
| *Level* | *Description*|
| 1 | developers |
| 2 | service |
| 3 | marketing |
| 4 | customer |
And I would like to set permission in the Roles setting.
-
19:54 Defect #28925: Custom field values for enumerations not saved
- why enumerations use strong params instead of safe_attributes like all other models do?
-
17:38 Defect #28925: Custom field values for enumerations not saved
- Maybe we can use @available_custom_fields@ to collect ids of custom fields. I think the following change can make the patch simpler and faster. Mizuki, do you think it is correct?
-
08:18 Defect #28925: Custom field values for enumerations not saved
- I changed the test a little.
-
07:44 Defect #28925: Custom field values for enumerations not saved
- I wrote a patch to fix this defect.
The key of custom_field_values allows only id of custom field of enumeration. -
15:44 Patch #29045: Change Japanese translation for Tracker
- +1
I am also a Japanese. I think that this change is reasonable. -
15:28 Patch #29045: Change Japanese translation for Tracker
- +1
Yes, I agree, too.
Documentations and manuals are to be changed, but it must progress the understandability of Japanese ordinary people. -
15:17 Patch #29045: Change Japanese translation for Tracker
- +1
I also ageree. -
14:22 Patch #29045: Change Japanese translation for Tracker
- +1
I agree with this fix.
In Japanese, "トラッカー" is not a general term, it does not understand intuitively what it means.
If it is "チケット種別" (means "issue type") its meaning is easy to infer.
-
09:04 Patch #29045: Change Japanese translation for Tracker
- Here are some screenshots:
!{width: 1024px; border: 1px solid #ccc;}.trackers-index@2x.png!
!{width: 445px; border: 1px solid #ccc;}.issues-index@2x.png!
!{width: 742px; border: 1px solid #ccc;}.issues-edit@2x.png!
-
08:01 Patch #29045: Change Japanese translation for Tracker
- +1
-
06:51 Patch #29045 (Closed): Change Japanese translation for Tracker
- The current Japanese translation for the word "tracker" is "トラッカー". It is not a true translation but just an imitation of English pronunciation of "tracker". So, most Japanese people cannot understand the word "トラッカー" without someone's e...
-
15:37 Defect #27153: Custom query breaks calendar view with error 500
- Created issue in issue_hot_buttons plugin https://github.com/panicinc/issue_hot_buttons/issues/15
-
12:02 Defect #28125: PNG images on a wiki page don't appear in exported PDF
- bundle update and restart webserver should be enough?
For me it is not working... -
11:50 Defect #28125 (Resolved): PNG images on a wiki page don't appear in exported PDF
-
11:10 Defect #28125: PNG images on a wiki page don't appear in exported PDF
- tested right now after bundle update, it's ok for we with redmine 3.4.5 stable, it works !
-
08:14 Feature #29042 (Closed): Add links to Users, Projects and Versions (at least) in timelog report
- Committed. Thank you for improving Redmine.
-
07:24 Feature #5358: Share Issues Categories for sub-projects
- +1
2018-06-17
-
22:40 Defect #29043 (New): Dropdown Project Search list is sorted in weird order
- Since #19299 was implemented (I'm assuming somewhat here), the sort order of projects in the dropdown list is sort-of-alfabetical. If used to be in the same order as the project list, in other words, alfabetical, but with sub-project so...
-
21:56 Feature #24568 (Closed): Show locked users in 'Users' filter for 'Spent time' report
- Go MAEDA wrote:
> The patch #24568#note-10 looks good.
> ...
Done (#29042).
In this case, I'm closing this one as fixed by r17371 in #15201. -
09:10 Feature #24568: Show locked users in 'Users' filter for 'Spent time' report
- The patch #24568#note-10 looks good.
But I think it would be better to create a new issue for the patch. The reasons are as follows:
* The feature requested in this issue has already been implemented by #15201.
* Your patch bring... -
21:53 Feature #29042 (Closed): Add links to Users, Projects and Versions (at least) in timelog report
- This issue is extracted from 24568#note-8.
*Before:*
!{width: 60%; border: 1px solid grey;}timelog_report_before.png!
*After:*
!{width: 60%; border: 1px solid grey;}timelog_report.png!
In this way, the locked users will have ... -
21:39 Defect #27283: Failed to run "rake db:migrate" command against clean database on MySQL 5.7
- Official Docker image:
-
16:53 Defect #27283: Failed to run "rake db:migrate" command against clean database on MySQL 5.7
- Jean-Philippe Lang wrote:
> Migration is working fine for me with mysql 5.7.22 and default config using current trunk.
> ...
I can reproduce the problem.
* Ubuntu 16.04.2 LTS
* MySQL 5.7.22-0ubuntu0.16.04.1
/etc/mysql/my.cnf: -
15:40 Defect #27283: Failed to run "rake db:migrate" command against clean database on MySQL 5.7
- Migration is working fine for me with mysql 5.7.22 and default config using current trunk.
Please provide your my.conf in order to reproduce. -
21:15 Defect #26892: Link to user in wiki syntax only works when login is written in lower case
- I agree with the workaround posted above by Go Maeda, it is enough to fix the failing test. It seems that on my local environment, the search is case insensitive and the test doesn't fail.
-
16:28 Defect #26892: Link to user in wiki syntax only works when login is written in lower case
- Jean-Philippe Lang wrote:
> Marius, I have applied #26443 and I'm getting a failure for the test included in this patch:
This is a workaround for the error. -
07:56 Defect #26892: Link to user in wiki syntax only works when login is written in lower case
- Marius, I have applied #26443 and I'm getting a failure for the test included in this patch:
-
20:00 Feature #28952: Update User#last_login_on only once per minute
- done #29041
-
16:54 Feature #28952 (Closed): Update User#last_login_on only once per minute
- Patch committed, thanks.
Pavel Rosický wrote:
> I'm wondering if something like this could be also applied for
> ...
Please fill a separate issue so we can keep track of that. -
19:57 Feature #29041 (Closed): Update session token only once per minute
- this is simmilar to #28952
if Rails.application.config.redmine_verify_sessions is enabled, basically each read request triggers an update to tokens table. This is bad for performance because it blocks the database.
My patch transform... -
18:29 Feature #2471: Add my activities to my page
- Setting target version to 4.1.0.
-
18:23 Patch #28940: Use Regexp#match? to reduce allocations of MatchData object
- I combined all patches into a single file and I retested it on Ruby 2.3 and Ruby 2.4
-
18:01 Feature #28947: Show the existing attachments on the wiki editing page
- Tomomi Yuzuriha wrote:
> I wrote a patch to implement this feature.
Thank you for submitting the patch.
Would you explain why the patch disables 'Delete' button on wiki#edit page?
-
17:29 Defect #29038: Thumbnail macro causes attachment file not found and broken filename and link
- in thumbnail macro (lib/redmine/wiki-formatting/macros.rb),
-
17:00 Defect #29038 (Closed): Thumbnail macro causes attachment file not found and broken filename and link
- Wiki's thumbnail macro seemed to break attachment's filename attribute when the attachment has non-blank description.
* case 1
On a wiki page attached an image file with description, and wrote twice thumbnail macros of the image fil... -
15:00 Defect #28951 (Closed): Cannot clear category field on copying an Issue
-
08:37 Defect #28951: Cannot clear category field on copying an Issue
- Jean-Philippe Lang wrote:
> But the OP is using a stable branch, can you confirm?
No, I cannot reproduce it on 3.4.6. Probably the reporter is using the master branch of https://github.com/redmine/redmine. It is not an svn working co... -
08:26 Defect #28951: Cannot clear category field on copying an Issue
- Go MAEDA wrote:
> Confirmed the problem. This is due to r17320. The trunk is affected but stable branches are not.
This problem should be fixed by r17395.
But the OP is using a stable branch, can you confirm? -
07:23 Defect #28951 (Confirmed): Cannot clear category field on copying an Issue
- Confirmed the problem. This is due to r17320. The trunk is affected but stable branches are not.
-
08:00 Defect #27968 (Closed): Image filename for HDPI monitors (image@2x.jpg) are misrecognized as email address
- Patch committed, thanks Marius.
-
07:57 Defect #26507 (Closed): "attachment:filename" link syntax would not work if the file name contains "@"
- Thanks Marius.
-
07:47 Defect #26443 (Closed): User link syntax (user:login) doesn't work for logins consisting of an email adress
- Patch committed, thanks Marius.
Marius BALTEANU wrote:
> Just a technical note: An interesting approach is the "html-pipeline":https://github.com/jch/html-pipeline used by GitHub which easily allows you to apply different filters or ... -
03:07 Defect #28946 (Closed): If assignee is locked subtasks don't get copied
- Committed. Thank you for the fix.