Activity
From 2020-07-23 to 2020-07-25
2020-07-25
-
21:42 Feature #30117: Conditional fixing keywords
- The current model of fixing keywords ignores current status. Yes, you can limit workflow state transition, but this wouldn't solve all cases.
For example, it can be permitted by the workflow to change "Resolved" to "In Progress" in case... -
18:58 Patch #33728: Remove an unused variable in Query#add_chained_custom_field_filters
- Go MAEDA wrote:
> Thank you for reporting the issue. I prefer the following fix because filter_id and filter_name are used as a pair at another line in query.rb (source:tags/4.1.1/app/models/query.rb#L1328).
OK, I think either soluti... -
10:47 Patch #33728: Remove an unused variable in Query#add_chained_custom_field_filters
- Thank you for reporting the issue. I prefer the following fix because filter_id and filter_name are used as a pair at another line in query.rb (source:tags/4.1.1/app/models/query.rb#L1328).
-
10:56 Patch #33763: Change Japanese translation for field_onthefly
- Setting the target version to 4.2.0.
-
10:55 Defect #33140 (Closed): Gantt bar is not displayed if the due date is the leftmost date or the start date is the rightmost date
-
10:18 Defect #33140 (Resolved): Gantt bar is not displayed if the due date is the leftmost date or the start date is the rightmost date
- Committed the patch.
-
10:55 Revision 19937 (svn): Merged r19935 from trunk to 4.0-stable (#33140).
-
10:54 Revision 19936 (svn): Merged r19935 from trunk to 4.1-stable (#33140).
-
10:17 Revision 19935 (svn): Gantt bar is not displayed if the due date is the leftmost date or the start date is the rightmost date (#33140).
- Patch by Yuichi HARADA.
-
08:39 Defect #28793: Redmine replaces tabs with spaces in code blocks
- The behavior of Textile formatter can be changed with the following patch, but I think it is not easy to change the behavior of Markdown formatter because is done in "Redcarpet gem":https://github.com/vmg/redcarpet.
-
07:57 Defect #31637: CSV and PDF export don't respect Time span format
- Go MAEDA wrote:
> Thank you for posting the patches but @issues_pdf_test.rb@ fails.
> ...
Sorry, I applied the older patch. The latest patch has no problem. The patches work fine now. -
07:45 Defect #31637: CSV and PDF export don't respect Time span format
- Thank you for posting the patches but @issues_pdf_test.rb@ fails.
2020-07-23
-
23:46 Feature #30117: Conditional fixing keywords
- I'm pretty sure that it already does this. It depends on the tracker workflow settings. If your tracker allows New to change to In Progress, but doesn't allow Resolved to change to In Progress, then you'll get what you want.
-
15:09 Defect #33766 (Closed): #31355 breaks project tree
- I think this defect has already been fixed for v4.2.0 in #32944.
Anyway, thank you for reporting the issue. -
11:53 Defect #33766 (Closed): #31355 breaks project tree
- Asume you jave a project tree (with sub projects like this
-top
+-sub1
+-sub2
+-sub3
This is displayes wellformed as a tree in projedct quickjump dropdown
Now klick on project "top"
The project "top" now appears under "... -
10:23 Defect #31637: CSV and PDF export don't respect Time span format
- Seiei Miyagi wrote:
> I also write a patch for PDF download timespan format.
> ...
I updated the patch, added a test for IssuesPdfHelper too. -
09:30 Defect #31637: CSV and PDF export don't respect Time span format
- I also write a patch for PDF download timespan format.
Should I create a new ticket for that? -
09:22 Defect #31637: CSV and PDF export don't respect Time span format
- Marius BALTEANU wrote:
> Seiei Miyagi wrote:
> ...
I added a test. -
08:57 Defect #31637: CSV and PDF export don't respect Time span format
- Seiei Miyagi wrote:
> I wrote a patch with Kusukawa and Mattani
Thanks for writing the patch. Can you add a new test or new assertions to existing tests? -
08:52 Defect #31637: CSV and PDF export don't respect Time span format
- I wrote a patch with Kusukawa and Mattani
-
07:53 Defect #31637: CSV and PDF export don't respect Time span format
- PDF export has same bug
-
10:10 Feature #7907: Display Issues in a hierarchy (tree)
- +1
-
06:32 Feature #7907: Display Issues in a hierarchy (tree)
- Klaus Adler wrote:
> +1
> ...
As far as the tree view is concerned you may have a look at this plugin here: https://www.redmine.org/plugins/redmine_issues_tree
-
09:53 Feature #33572: Show issue subject in the tooltip of "Prev" and "Next" button for issues
- Thanx!
LGTM! -
09:34 Feature #33572: Show issue subject in the tooltip of "Prev" and "Next" button for issues
- Goh Matsumoto wrote:
> It may be better to change the method name: 'retrieve_previous_and_next_issue_ids'.
> ...
Thank you for pointing it out.
I updated the patch. -
07:27 Feature #33572: Show issue subject in the tooltip of "Prev" and "Next" button for issues
- It may be better to change the method name: 'retrieve_previous_and_next_issue_ids'.
e.g. 'retrieve_previous_and_next_issue' -
08:31 Patch #33763: Change Japanese translation for field_onthefly
- Here is a screenshot with the patch applied.
!{width: 519px; border: 1px solid grey;}.screenshot-33763.png! -
08:25 Patch #33763 (Closed): Change Japanese translation for field_onthefly
- The current Japanese translation "あわせてユーザーを作成" (means "create a user at the same time") is vague. The feature automatically creates a user account when the authentication by the LDAP server is successful, however, it is not easy to under...