Activity
From 2018-09-27 to 2018-09-29
2018-09-29
-
23:53 Defect #26708 (Closed): Diff formatting results empty lines if they contains HTML tags
- Fixed by the migration to Rouge (#24681).
using CodeRay:
!before.png!
after migration to Rouge:
!after.png!
-
23:46 Feature #26791: Send individual notification mails per mail recipient
- I took the liberty to update the first patch to apply cleanly on the current trunk just in case of Holger Just or some else from Plan.io team do not have the time to do it until the new release. All tests pass and the rest of the patches...
-
09:55 Feature #26791: Send individual notification mails per mail recipient
- Because of r17269, the patch does not apply cleanly. Could you update it so we can commit this change? Thanks.
-
19:59 Feature #24681 (Reopened): Syntax highlighter: replace CodeRay with Rouge
- r17532 comments out the gem 'puma', please see source:trunk/Gemfile#L92 and I don't think that it is a desired change.
-
18:18 Feature #24681: Syntax highlighter: replace CodeRay with Rouge
- Thank you Go MAEDA for not giving up this feature and everyone else who contributed to the patch being merged.
-
08:57 Feature #24681 (Closed): Syntax highlighter: replace CodeRay with Rouge
- Thanks for fixing this issue, patch is committed.
-
12:47 Patch #29692: Bosnian localization update
- Additional typos fixed
-
12:33 Patch #29692 (Closed): Bosnian localization update
- Patch to update Bosnian translation is attached
* All untranslated text translated
* Typos fixed
* Standardize different namings of the values -
10:28 Patch #1651 (Closed): Hack to make redmine use pygmentize instead of CodeRay
- In the upcoming Redmine 4.0, such a hack is no longer necessary because the new syntax highlighter supports a large number of programming languages. Please see #24681 for details.
-
10:17 Feature #28094 (Closed): Kotlin code highlight support
- Implemented in #24681 for upcoming Redmine 4.0.0.
-
10:12 Feature #1313 (Closed): Optionally use ultraviolet for syntax highlighting
- The syntax highlighter has been replaced with Rouge in #24681 and it supports most popular languages.
https://github.com/jneen/rouge/wiki/List-of-supported-languages-and-lexers -
10:06 Feature #3032 (Closed): Use google Prettify for syntax highlighting instead of CodeRay
- The syntax highlighter has been replaced with Rouge in #24681 and it supports most popular languages.
https://github.com/jneen/rouge/wiki/List-of-supported-languages-and-lexers -
09:29 Feature #2623 (Closed): C# syntax highlighting
- Implemented in #24681 for upcoming Redmine 4.0.0.
-
04:16 Feature #29660: Add Referrer-Policy header to prevent browsers from sending private data to external sites
- Maybe adding Referrer-Policy header is preferable rather than adding a meta-tag for the following reasons.
* We can ensure that the header is always set
* Sysadmins can easily override the header by configuring web servers if necessary -
03:14 Feature #2529: Extend Issue Summary to include subprojects
- I have looked the patch attachment:feature_2529_v2.patch.
The patch passes an array of subprojects to @with_subprojects@ parameter in @Issue.count_and_group_by@, but the parameter is supposed to be true or false. I suggest updating th... -
01:45 Feature #23392: Link to remove a subtask from its parent task
- Here is a screenshot of the patch.
!{width: 797px; border: 1px solid #ccc;}.remove-subtask-button@2x.png! -
00:47 Feature #23392: Link to remove a subtask from its parent task
- The patch adds a button to remove subtask in the "Subtasks" section of an issue. Since the button looks consistent with existing buttons in "Related issues" section, I am in favor of merging the patch.
But I am not sure if it is OK wi...
2018-09-28
-
21:09 Feature #29690: Restrict Issues Access by status in workflow to respective roles.
- For example.
Profile: Help Desk Analyst
Tracker Type: Request
Permission: View/List - Any or specific statuses (Level 2, Level 3)
Edit, Any or specific statuses (Level 2, Level 3)
... -
20:52 Feature #29690 (New): Restrict Issues Access by status in workflow to respective roles.
- How could I restrict access to a group of issues by user-role, tracker and status in workflow?
For example;
Role 2 can only view or list issues for workflow statuses: "Level 2" or "Level 3".
Role 3 can only view or list issues for wor... -
20:37 Feature #285: Tracker role-based permissioning
- How could I restrict access to a group of issues by user-role, tracker and state in workflow?
For example;
Role 2 can only view issues for workflow statuses: "Level 2" or "Level 3".
Role 3 can only view issues for workflow status: "Le... -
20:20 Feature #7360: Issue custom query: default query per instance, project and user
- +1
-
15:00 Feature #29631: Add support to include repository file content in Wiki
- I am also very much interested in this functionality. It would avoid redundancy and add a great deal of flexibility when creating documentation.
-
12:36 Defect #25130: support of agglutinative languages like Hungarian/Magyar
- How can I help?
-
12:35 Patch #28509: hu.yml for Redmine 3.4
- How can I help?
-
09:39
Feature #10614: Email Notifications for Custom field with User type
- is this plugin working with Redmine 3.4?
-
09:31 Feature #29164: Make the terms overwrite from the Redmine administration screen.
- +1
-
08:52 Feature #23392: Link to remove a subtask from its parent task
- I wrote a patch to realize this feature.
When applying this patch, "Delete link to subtask button" will be added.
Pressing this button has the same effect as when emptying the "parent task field" on the child issue editing screen. -
05:08 Patch #29674: Missing validation for custom field formats based on RecordList
- +1
I also think that the validation that 'Alexander Achenbach' pointed out should be done.
Actually, by manipulating the form on the client side, it was possible to send arbitrary record ID.
I added a test code to the patch made by 'A... -
04:31 Defect #26023 (Needs feedback): Category filter only shows categories of current project
- I would like Felix to review the patch attachment:26023_test_added.patch.
-
03:56 Feature #2529: Extend Issue Summary to include subprojects
- Go MAEDA wrote:
> I had a look at the patch by Mizuki Ishikawa and found that it is better not to replace @Issue.by_*@ methods with @Issue.count_and_group_by@. Instead, @Issues.by_*@ methods should take @Setting.display_subprojects_issu... -
00:32 Patch #29673 (Closed): Update Russian translations
- Committed. Thank you for your contribution.
2018-09-27
-
23:42 Feature #29687 (Closed): Keep history for comment editions
- closing as a duplicate of #12388.
Thank you for suggesting a new feature. -
16:42 Feature #29687: Keep history for comment editions
- related to #2598
-
15:07 Feature #29687 (Closed): Keep history for comment editions
- Whenever I edit a comment it is updated but as far as I can see there is no history for that. We need history for all changes in the redmine. At least for comment edits.
Probably this was reported in #9441 but due to bad style, it was... -
16:43 Feature #2598: Edit of issue notes should be tracked
- related to #12416 and #29687
-
15:26 Feature #23307: Include auth_source field in User API response
- What is the status of this issue?
-
15:23 Defect #29607 (Closed): Allow project column to break into new line in time entry table
- Committed the patch. Thank you for providing the patch.
-
09:47 Defect #29607: Allow project column to break into new line in time entry table
- Felix Gliesche wrote:
> i did some tests. For the issue list, I didn't really find an improvement for the issue list:
Thank you for sparing time for testing it, I agree with you.
I am setting the target version to 4.1.0.
-
15:14 Patch #29669 (Closed): "no_notification" option is not listed in the description of email.rake
- Committed. Thank you for your contribution.
-
13:26 Defect #29686 (Closed): Date format in issues pages
- Hello
I recently updated to Redmine 3.4.6, I have configured the Starting day of week the mondays, but in the issues when I want to select the date the shown calendar has the sunday as first week day, can this be changed to be the monda... -
13:03 Feature #29685 (New): Check for modifications on an issue before letting somebody else edit it
- *Environment*
Redmine version: 3.4.2.stable
Ruby version: 2.3.0-p0
Rails version: 4.2.8
Database: pgsql 9.2
*Example*
Person A created an issue and has the page right after creation still opened. The issue has been assigned to ... -
12:33 Feature #24681: Syntax highlighter: replace CodeRay with Rouge
- Fixed the ampersand issue. Please test attachment:0001-Switch-syntax-highlighter-to-Rouge-from-CodeRay.patch.
The reason why ampersand is broken is that recloth3.rb replaces "&" with "x%x%" while processing Textile. ... -
05:43 Feature #24681: Syntax highlighter: replace CodeRay with Rouge
- Jean-Philippe Lang wrote:
> There's a serious problem with & caracters:
This problem occurs when the text formatting setting is Textile. redcloth3.rb replaces all "&" to "x%x%" before calling @highlight_by_language@... -
10:24 Defect #29684 (New): when using export issues to csv format, notes fields contain html flags, making text quite hard to read / use
- users need to make reporting based on notes fields in csv exported files.
html flags make the text unreadable. -
08:39 Feature #29683 (New): New filter TIME in report "Spen time"
- Hello,
I need to add time filter/column when the spent time was added/logged. Now is only date *2018-09-25* (in the snapshot), but I want *2018-09-25* and time *13:52* too. The time is in the database, but not showed. When I open atom... -
05:09 Defect #29681: "x%x%" is rendered as "&" in Textile formatter
- This is because RedCloth temporarily replaces "&" with "x % x %" (actually, there are no space characters) while converting Textile to HTML.
* source:tags/3.4.6/lib/redmine/wiki_formatting/textile/redcloth3.rb#L1010
* source:tags/3.4... -
03:17 Defect #29681 (New): "x%x%" is rendered as "&" in Textile formatter
- The character sequence described in the subject is always rendered as "&" in Textile formatter. You can easily reproduce this issue by entering the sequence in a description field of an issue.
You see '@=> "&"@' in the second line of ...