Activity
From 2018-06-26 to 2018-06-28
2018-06-28
-
14:55 Patch #26091 (Reopened): Allow to filter by any visible version on the global issues view
- I'm reopening and assigning this to me because I would like to add a test for this feature.
-
02:50 Patch #26091 (Closed): Allow to filter by any visible version on the global issues view
- Committed. Thank you for improving Redmine.
-
11:55 Defect #29036 (Closed): "Assigned to" filter on the issues page works only on second attempt
- Vladislav Yashin wrote:
> It was a problem in redmine_elasticsearch
Thank you for reporting it. -
11:49 Defect #29036 (Resolved): "Assigned to" filter on the issues page works only on second attempt
- It was a problem in redmine_elasticsearch
-
09:36 Defect #29128: API: Issue Relation create does not work
- Hi the URL is https://www.redmine.org/projects/redmine/wiki/Rest_IssueRelations
Looking at it again, the GET method actually returns arrays, while the POST one fits to the one you provided.
Would be good, if someone could add xml/j... -
03:57 Defect #29128: API: Issue Relation create does not work
- Thank you for your confirmation.
I read the code, but the current Issue Relation create API seems not to support to multiple structures.
Eser Esen wrote:
> Yes it worked, but does that mean, i cannot add multiple relations with one ... -
05:37 Patch #29151 (Closed): Add honorific suffixes ("san") in Japanese translation
- I suggest adding an honorific suffix "さん" ("san") to Japanese messages.
In Japanese, it is rare and sometimes impolite not to add honorific suffixes referring to others in a conversation. For example, people say "Maeda-san" when talki... -
03:21 Patch #29129 (Closed): Use active voice instead of passive voice in Japanese translation
- Committed.
-
02:52 Patch #29129: Use active voice instead of passive voice in Japanese translation
- +1
-
02:48 Patch #29115: Change Japanese translation for date filter operators
- +1
-
02:05 Feature #29145 (Closed): To embedded the Roadmap for a project into an iFrame?
- Please use forums for question after reading "How to request help":http://www.redmine.org/boards/2/topics/667.
-
01:28 Defect #29028 (Closed): Redmine generates notification emails that fail DMARC and will therefore often be rejected or quarantined
- Jonathan Kamens wrote:
> Reported at https://github.com/ruby/b.r-l.o/issues/91 .
Thank you.
2018-06-27
-
22:35 Defect #29028 (Resolved): Redmine generates notification emails that fail DMARC and will therefore often be rejected or quarantined
- Reported at https://github.com/ruby/b.r-l.o/issues/91 .
-
16:58 Feature #29145 (Closed): To embedded the Roadmap for a project into an iFrame?
- We used Google Site as our team site which contains information of all our projects. It is very nice for us to "embedded" information from Redmine about our planned work into our Google site especially with the roadmap
-
16:18 Patch #29142 (Closed): Japanese translation change for "lost password"
- The patch changes "再発行" (reissue) to "再設定" (reset). The word "再発行" vaguely suggests that a plain password will be informed.
-
15:20 Defect #29128: API: Issue Relation create does not work
- Yes it worked, but does that mean, i cannot add multiple relations with one shot? looking at the api doc it looks like it is handling arrays of relations.
Thanks -
08:38 Defect #29128 (Needs feedback): API: Issue Relation create does not work
-
08:26 Defect #29128: API: Issue Relation create does not work
- Could you please change it as follows and try it out.
With my environment this worked out. -
15:17 Feature #973: Assign different status sets and workflows for separate projects
- +1
-
14:49 Feature #16410: Bulk delete wiki attachments
- It works fine for me and the code and the behavior are consistent with #13072. Setting target version to 4.1.0.
-
14:23 Feature #29131: 'View all Issues' adds project custom fields Columns displayed on the issue list
- zhangzhi liao wrote:
> Feature #18006 yes ,I copy that issue,beacuse i found there years later,the issue still not solve!
Please don't create duplicate issues on purpose. It does not help to speed up the development at all. Instead,... -
12:20 Feature #29131: 'View all Issues' adds project custom fields Columns displayed on the issue list
- Feature #18006 yes ,I copy that issue,beacuse i found there years later,the issue still not solve!
-
11:52 Patch #29129: Use active voice instead of passive voice in Japanese translation
- Updated the patch. Removed garbages and reverted some changes.
-
07:14 Patch #29129: Use active voice instead of passive voice in Japanese translation
- +1
-
05:29 Patch #29129: Use active voice instead of passive voice in Japanese translation
- +1
-
10:04 Feature #28616 (Closed): Handle image orientation of attachments and thumbnails
- Committed. Thank you for sharing the patch.
-
08:40
Feature #2024: gantt chart editing
- I would still love to have this feature. Can someone organise to have some developers come together and create a kickstarter or similiar for a shared funding ?
I would certainly contribute in a meaningful way. -
07:57 Feature #28947: Show the existing attachments on the wiki editing page
- Thank you for all the work for this feature.
I think that if #16410 were implemented that feature could meet my needs. -
00:41 Patch #28934: Support migration context for plugins
- I attach a patch to add simple unit test.
I hope to fix this issue :) -
00:25 Feature #12763: Add filtering capability to time entries REST API
- I am trying to do something very simple like getting all time entries on a given date. I tried sending a request to @/time_entries.json?spent_on=2018-06-26&user_id=me@ but it doesn't work. Am I doing something wrong?
I am trying to bu...
2018-06-26
-
18:17 Patch #29107 (Closed): Traditional Chinese translation (to r17413)
- Committed. Thank you for your contribution.
-
18:03 Feature #19094 (Closed): 'View all Issues' adds project custom fields
-
18:01 Feature #19094: 'View all Issues' adds project custom fields
- Closing as a duplicate of #18006.
-
18:02 Feature #29131 (Closed): 'View all Issues' adds project custom fields Columns displayed on the issue list
- Thank you for suggesting this feature but I am closing this issue because I found a very similar issue #18006.
-
13:57 Feature #29131: 'View all Issues' adds project custom fields Columns displayed on the issue list
- Only project name can be shown.
What I asked, is the possibility to show also custom fields. As said, at the moment the custom fields can be used as query filter, but not as query output columns. -
13:46 Feature #29131 (Closed): 'View all Issues' adds project custom fields Columns displayed on the issue list
- 'View all Issues' adds project custom fields Columns displayed on the issue list is very helpful feature!
-
17:31 Patch #29045: Change Japanese translation for Tracker
- Masakazu IZUI wrote:
> It whould be like "型".
> ...
I think "型" is difficult to understand if the user is not a programmer. Maybe many people are not familiar with the concept of "型" (type, class).
/* ja
「型」はプログラミングの知識がある人以外には理解しにく... -
14:34 Patch #29045: Change Japanese translation for Tracker
- It whould be like "型".
"Category", as it is.
#-- いっそ「型」にしてしまうというのはどうでしょうか(トラッカー)。
#-- カテゴリはカテゴリのまま据え置きで。 -
14:42 Patch #29129: Use active voice instead of passive voice in Japanese translation
- +1
I'd like it. -
13:34 Patch #29129 (Closed): Use active voice instead of passive voice in Japanese translation
- The English sentence "X has been added/updated by Y" is translated as "X が Y によって追加/更新されました" in the current ja.yml. But it is a little bit unnatural because it is a passive voice ("追加/更新されました" means "be added/updated"). Passive voice is ...
-
11:55 Patch #29118 (Closed): Change Japanese translation for text_user_mail_option
- Committed.
-
02:43 Patch #29118 (Closed): Change Japanese translation for text_user_mail_option
- The word "事柄" (means "things") is no longer used in for Japanese @label_user_mail_option_only_*@ strings after r16110. It was replaced with "もの" (also means "things"). But @text_user_mail_option@ still uses "事柄".
The following patch c... -
11:00 Defect #29128 (Needs feedback): API: Issue Relation create does not work
- using postman */issues/15658/relations.json*
with headers
* Content-Type:application/json
* X-Redmine-API-Key:...
and payload -
10:30 Feature #8160: Extend watched_by_me-issue filter to include all project-members instead of only <<me>>-substitution
- LGTM, I'm in favour of delivering this feature in the next major version.
-
02:47 Feature #8160: Extend watched_by_me-issue filter to include all project-members instead of only <<me>>-substitution
- Go MAEDA wrote:
> Mizuki, thank you very much for posting the patch so quickly. I tried out the patch and I noticed the following points. To move this issue forward, could you update the patch?
> ...
Fixed points you pointed out.
Than... -
09:49 Patch #3195: issue's start date could be the latest due date of predecessors
- Lets leave it as it is for now. I've removed it from version:"Candidate for next major release" until we get more feedback from the community and we agree to a solution.
-
09:46 Feature #7360: Issue custom query: default query per instance, project and user
- +1
The patch of #7360#note-36 which was not working according to version upgrade was fixed to work on trunk.
I would like the continuation of work to realize this feature. -
09:34 Defect #27283: Failed to run "rake db:migrate" command against clean database on MySQL 5.7
- I made some checks and it seems that the changes between @rake db:migrate@ on Rails 4.2 and @rake db:migrate@ on Rails 5.2 are quite big.
First of all, it seems that the @:timestamp@ method from migrations generates different column t... -
08:05 Defect #26537: Column Project is not longer added by default to the list of default columns for time entries
- Sorry for the noise, now is the correct patch attached.
-
07:57 Defect #26537: Column Project is not longer added by default to the list of default columns for time entries
- Here is the updated patch.
Jean-Philippe, some mentions regarding my patch:
- I've removed the default columns defined in the @default_columns_names@ and @default_totalable_names@ methods because I found them confusing to have them ... -
06:40 Patch #29115: Change Japanese translation for date filter operators
- +1
I like this translation.
Simple is best!