Activity
From 2018-06-28 to 2018-06-30
2018-06-30
-
09:32 Revision 17427 (svn): Simpler expression for Japanese label_in_the_next_days and label_in_the_past_days (#29115).
-
08:30 Defect #29038: Thumbnail macro causes attachment file not found and broken filename and link
- I have confirmed the issue. Here is a test to catch it.
-
08:13 Feature #17907: Give 'version' another meaning
- I also agree with this proposal. From my experience it's hard to sell the Roadmap feature to people which are not involved in any type of software development or dev-topics at all. I usually come around that issue by renaming the 'versio...
-
08:07 Patch #29160: Remove unused and broken method CustomField.visibility_condition
- I have confirmed the problem Holger reported. Setting target version to 4.0.0.
-
07:41 Patch #29115 (Closed): Change Japanese translation for date filter operators
- Committed.
-
07:40 Revision 17426 (svn): Change Japanese translation for date filter operators (#29115).
- Patch by Go MAEDA.
-
06:52 Patch #29045: Change Japanese translation for Tracker
- I don't agree this translation proposal.
"tracker" contains the meaning of tracking the issue's status changes.
"種別[shubetsu] aka type" does not contains.
Besides, the word "type" is very similar to the word "category".
It may ... -
02:25 Patch #26091 (Closed): Allow to filter by any visible version on the global issues view
- Committed. Thank you all for the contribution.
-
02:24 Revision 17425 (svn): Changed test name (#26091).
- Patch by Marius BALTEANU.
2018-06-29
-
17:32 Patch #29162: Only allow visible custom fields as aggregation criteria in time reports
- With just this patch, we can avoid the consequences of #29161 (at least I have not found any other place where this is an issue). Still, we should also apply #29161 to make the method save to use for ProjectCustomFields.
-
17:27 Patch #29162 (Closed): Only allow visible custom fields as aggregation criteria in time reports
- In time reports, the user can currently select any custom field defined in the Redmine system as an aggregation criteria. This can lead to confusion since the returned data might not reflect the custom field or might even lead to an info...
-
17:14 Patch #29161 (Closed): Avoid SQL errors when adding a project custom field as a time report criteria
- Custom fields can have different visibilities, depending on the custom field type and the current user:
* Custom fields are always visible to admins
* They are not visible for anonymous unless explicitly checked
* They are visible i... -
14:48 Patch #29160 (Closed): Remove unused and broken method CustomField.visibility_condition
- The class method was introduced in r12012 along with the instance method @CustomField#visibility_by_project_condition@. The method's body seems to follow the idea of the instance method but misses a lot of data required by it, including ...
-
14:03 Defect #26619: Workflow field permissions does not work with several different roles
- +1, we have same issue. We do have users with few Roles and Field Permissions just do not work if user/group has more than one permission.
Any workaround for this issue? -
09:32 Defect #29158 (New): API don't shows value label of a costum field
- h3. General informations
*Ruby version:* 2.1.5-p273
*Rails version:* 4.2.8
*Redmine version:* 3.4.4.stable.17183
h3. Informations about the specification of the custom field
*Format:* Key/value list
*Multiple values:* True
... -
09:23 Patch #26091: Allow to filter by any visible version on the global issues view
- Go MAEDA wrote:
> Marius BALTEANU wrote:
> ...
I think the new name of the test reflects better what is tested inside it. Also, we should remove the blank line from the end of the test (line 628).
Me sorry because I didn't pay enou... -
09:19 Patch #26091: Allow to filter by any visible version on the global issues view
- Marius BALTEANU wrote:
> Better test name.
Sorry, I have committed the previous patch. Do you think I should change the test name? -
09:10 Patch #26091: Allow to filter by any visible version on the global issues view
- Better test name.
-
07:39 Patch #26091: Allow to filter by any visible version on the global issues view
- Here is the updated test.
-
09:11 Revision 17424 (svn): Test for r17421 (#26091).
- Patch by Marius BALTEANU.
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
-
03:16 Revision 17423 (svn): Use active voice instead of passive voice in Japanese translation (#29129).
- Patch by Go MAEDA.
-
02:59 Revision 17422 (svn): Remove unnecessary trailing white-spaces.
-
02:49 Revision 17421 (svn): Allow to filter by all versions on the global issue list (#26091).
- Patch by Holger Just.
-
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.