Activity
From 2018-06-29 to 2018-07-01
2018-07-01
-
17:15 Feature #29164: Make the terms overwrite from the Redmine administration screen.
- Go MAEDA ,Thanks for your comment.
Go MAEDA wrote:
> What Yuuki Nara suggests is a feature to override default translation files by uploading customized YAML files on the administration page.
> ...
I do not consider replacing the en... -
15:12 Feature #29164: Make the terms overwrite from the Redmine administration screen.
- Currently, administrators can customize terms to fit their use case by modifying translation files (@config/locales/*.yml@). However, replacing YAML files is not so easy for Redmine admins because they usually don't have shell access to ...
-
12:57 Feature #29164 (New): Make the terms overwrite from the Redmine administration screen.
- The function of Redmine is flexible, and it can be used in various ways in a wide range.
However, because the names of each term are fixed, it is not suitable for individual use, and it may be difficult to use Redmine.
If you add a m... -
09:40 Patch #26501: Change English translation for setting_issue_list_default_columns
- I'm in favour of this change.
-
02:13 Patch #26501: Change English translation for setting_issue_list_default_columns
- Jean-Philippe, I would like to ask your decision about this change.
-
09:35 Feature #2665 (Closed): Filter on sub projects target version within the main project
- It seems to be fixed in the current trunk, but I'm not sure in which ticket, from my checks could be #24787.
I'm closing this because the subprojects target versions are now available in the target version filter of the main project.
... -
09:09 Defect #3869 (Closed): Filter using Target Version loses 'Target Version' part of the filter when applied across all tickets.
- Fixed for sure in #26091 that allows to filter by any visibile target version in the global page.
-
06:54 Patch #26728 (Closed): count > 0 vs exists?
- We have decided not to use @exists?@ there. Please see #24839#note-1 and #24839#note-3.
-
04:41 Defect #14443 (Closed): Property class in <code> inside <pre> does not accept a single quotes
- Fixed by #28469 (Redmine 3.3.8).
-
04:36 Defect #14575 (Closed): Validation message "Related issue can't be blank" should be hidden after "Add"
- I cannot reproduce the problem with the current trunk (Redmine 3.4.6.devel.17424). Closing.
-
04:20 Defect #17351 (Closed): 500 Internal Server Error when deploying in Tomcat 7
- Redmine 3.0 and later no longer support JRuby.
-
02:54 Defect #25282 (Closed): Explanation for attachment change in r16285
- I think the new preview feature introduced in Redmine 3.4 (#25988) has resolved this issue.
-
02:26 Defect #29069 (Needs feedback): API reports wrong date for time spent if issue start date is greater than spent_on date
-
01:45 Patch #29033: Move attachments to their own section in issue page
- LGTM. I think it improves understandability of information to visually separating description and attachments.
2018-06-30
-
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.
-
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.
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.