{"issues": [{"id": 35721, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 123153, "name": "Pavel Rosick\u00fd"}, "category": {"id": 19, "name": "Attachments"}, "subject": "Unlink files after they're closed", "description": "Tests are trying to unlink the file inside the block while the file descriptor is still active.\r\n\r\nthey were introduced by https://redmine.org/issues/35539\r\n\r\nfixes _Errno::EACCES: Permission denied_\r\n\r\n\r\n\r\ndiff --git a/test/unit/attachment_test.rb b/test/unit/attachment_test.rb\r\nindex 2aee87964..a870e3697 100644\r\n--- a/test/unit/attachment_test.rb\r\n+++ b/test/unit/attachment_test.rb\r\n@@ -276,27 +276,31 @@ class AttachmentTest < ActiveSupport::TestCase\r\n end\r\n \r\n def test_create_diskfile\r\n+ path = nil\r\n Attachment.create_diskfile(\"test_file.txt\") do |f|\r\n path = f.path\r\n assert_match(/^\\d{12}_test_file.txt$/, File.basename(path))\r\n assert_equal 'test_file.txt', File.basename(path)[13..-1]\r\n- File.unlink f.path\r\n end\r\n+ File.unlink path\r\n \r\n Attachment.create_diskfile(\"test_accentu\u00e9.txt\") do |f|\r\n+ path = f.path\r\n assert_equal '770c509475505f37c2b8fb6030434d6b.txt', File.basename(f.path)[13..-1]\r\n- File.unlink f.path\r\n end\r\n+ File.unlink path\r\n \r\n Attachment.create_diskfile(\"test_accentu\u00e9\") do |f|\r\n+ path = f.path\r\n assert_equal 'f8139524ebb8f32e51976982cd20a85d', File.basename(f.path)[13..-1]\r\n- File.unlink f.path\r\n end\r\n+ File.unlink path\r\n \r\n Attachment.create_diskfile(\"test_accentu\u00e9.\u00e7a\") do |f|\r\n+ path = f.path\r\n assert_equal 'cbb5b0f30978ba03731d61f9f6d10011', File.basename(f.path)[13..-1]\r\n- File.unlink f.path\r\n end\r\n+ File.unlink path\r\n end\r\n \r\n def test_title\r\n\r\n ", "done_ratio": 0, "created_on": "2021-08-06T15:33:29Z", "updated_on": "2021-08-06T15:33:29Z"}, {"id": 35720, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 123153, "name": "Pavel Rosick\u00fd"}, "category": {"id": 19, "name": "Attachments"}, "subject": "Defect: Binmode specified twice", "description": "after https://redmine.org/issues/35539 I'm getting failures\r\n\r\n\r\nArgumentError: binmode specified twice\r\n app/models/attachment.rb:572:in `initialize'\r\n app/models/attachment.rb:572:in `open'\r\n app/models/attachment.rb:572:in `create_diskfile'\r\n app/models/attachment.rb:142:in `files_to_final_location'\r\n \r\n\r\n_File::BINARY_ flag should be enough to setup a binary mode\r\n\r\n\r\ndiff --git a/app/models/attachment.rb b/app/models/attachment.rb\r\nindex c65c56722..b0b0a02ba 100644\r\n--- a/app/models/attachment.rb\r\n+++ b/app/models/attachment.rb\r\n@@ -572,7 +572,6 @@ class Attachment < ActiveRecord::Base\r\n File.open(\r\n File.join(path, name),\r\n flags: File::CREAT | File::EXCL | File::BINARY | File::WRONLY,\r\n- binmode: true,\r\n &block\r\n )\r\n rescue Errno::EEXIST\r\n\r\nStarted POST \"/uploads.js?attachment_id=2&filename=placeholder.jpeg&content_type=image%2Fjpeg\" for X.X.X.X at 2021-08-05 17:48:28 +0200\r\nProcessing by AttachmentsController#upload as JS\r\n Parameters: {\"attachment_id\"=>\"2\", \"filename\"=>\"placeholder.jpeg\", \"content_type\"=>\"image/jpeg\"}\r\n Current user: cyprien (id=121)\r\nCompleted 500 Internal Server Error in 5ms (ActiveRecord: 0.9ms)\r\n \r\nNoMethodError (undefined method `size' for #):\r\n \r\napp/models/attachment.rb:123:in `file='\r\napp/controllers/attachments_controller.rb:108:in `upload'\r\nlib/redmine/sudo_mode.rb:61:in `sudo_mode'\r\n \r\n\r\nIt seems to come from this change introduced to 4.2.2\r\n\r\ndiff redmine-4.2.1/app/controllers/attachments_controller.rb redmine-4.2.2/app/controllers/attachments_controller.rb\r\n108c108\r\n< @attachment = Attachment.new(:file => request.raw_post)\r\n---\r\n> @attachment = Attachment.new(:file => request.body)\r\n \r\nIf I switch back from request.body to request.raw_post the error is fixed", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "168"}], "created_on": "2021-08-06T08:50:30Z", "updated_on": "2021-08-06T15:05:06Z"}, {"id": 35688, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 49905, "name": "Brice Beaumesnil"}, "category": {"id": 44, "name": "Rails support"}, "subject": "OpenIdAuthentication alias_method_chain", "description": "Hello,\r\n\r\nIn redmine\\lib\\plugins\\open_id_authentication\\lib\\open_id_authentication\\request.rb\r\n\r\nA alias_method_chain already exist.\r\n\r\nIt could be change change to :\r\n\r\n\r\n alias_method :request_method_without_openid, :request_method\r\n alias_method :request_method, :request_method_with_openid\r\n \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "168"}], "created_on": "2021-08-05T09:32:01Z", "updated_on": "2021-08-05T09:32:01Z"}, {"id": 35687, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 188597, "name": "Guillermo ML"}, "category": {"id": 12, "name": "Translations"}, "subject": " Galician translation update", "description": "Added translations for missing strings against current trunk.\r\n* gl.yml\r\n* jstoolbar-gl.js", "done_ratio": 0, "created_on": "2021-08-05T07:57:47Z", "updated_on": "2021-08-05T07:57:47Z"}, {"id": 35685, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 97902, "name": "Martin Jungowski"}, "category": {"id": 21, "name": "Database"}, "subject": "Support for MySQL > 5.7 or MariaDB", "description": "Given that I cannot see anything on the roadmap I'd like to ask what the state of MySQL support is. As stated on the Install page the latest officially supported release is MySQL 5.6, which has been EOL since February of 2021. MySQL 5.7 seems to work just fine but is not yet officially supported (it's on the roadmap for the next major release after 5.0!) and has an EOL date of October 2023 (aka slightly over 2 years from today). At the current speed of development I fear that MySQL will be EOL long before it is officially supported by Redmine. MariaDB is not supported at all.\r\n\r\nAny insight?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-04T20:23:06Z", "updated_on": "2021-08-04T20:23:06Z"}, {"id": 35683, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 40856, "name": "Jens Kr\u00e4mer"}, "category": {"id": 39, "name": "PDF export"}, "fixed_version": {"id": 33, "name": "Candidate for next minor release"}, "subject": "PDF rendering improvements", "description": "Two PDF generation improvements:\r\n\r\n1. Currently, when rendering an issue PDF, macros are only expanded in the description, but not when rendering custom fields with fulltext formatting enabled. The patch changes the behaviour so that formatted full-width custom fields are rendered in the same way the description is rendered, fully interpreting macros. The behaviour for rendering normal-width custom fields is unchanged, probably it is better to leave it as is due to space constraints.\r\n2. Thumbnail macro output was not rendered properly (in the issue description and elsewhere) because the thumbnail image file could not be retrieved - the second patch extends @get_image_filename@ to check for thumbnail URLs and retrieve the proper file path in that case.\r\n\r\nBoth patches were initially developed for \"Planio\":https://plan.io/redmine-hosting .", "done_ratio": 0, "created_on": "2021-08-04T11:01:57Z", "updated_on": "2021-08-06T21:30:36Z"}, {"id": 35680, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 365663, "name": "Markus Boremski"}, "category": {"id": 3, "name": "SCM"}, "subject": "Error while using local hashes gitlab-repository", "description": "In our company we have many small projects with files in a git-repo.\r\n\r\nWe wanted to get rid of this crontab-solution: \"HowTo: Easily integrate a (SSH secured) GIT repository into redmine\":https://www.redmine.org/projects/redmine/wiki/HowTo_Easily_integrate_a_(SSH_secured)_GIT_repository_into_redmine\r\nAlso we never even tried the plugin \"redmine_git_remote\":https://www.redmine.org/plugins/redmine_git_remote because it doessnt seems to be maintained anymore.\r\n\r\nSo we set up a single VM running gitlab and redmine side by side.\r\nThis setup was choosen to keep usage of git repositories in redmine easy.\r\nWe planned to use the local repo-storage of gitlab directly in redmine.\r\n\r\nNow, everything is set up, we see the following issue:\r\n* Set up a repository in redmine and use the local path of the gitlab-repo:\r\ne.g.: @/var/opt/gitlab/git-data/repositories/@hashed/7a/df/3ada92f28b4ceda38562ebf047c6ff0xxxxxxxxxxxxxxxxxxxxxxxx.git@\r\n* calling the repo leads to a @404-error@\r\n* production.log says:\r\n\r\nStarted GET \"/projects/our_project_id/repository/test_local\" for xx.xx.xx.xx at 2021-08-04 09:30:19 +0200\r\nProcessing by RepositoriesController#show as HTML\r\n Parameters: {\"id\"=>\"our_project_id\", \"repository_id\"=>\"test_local\"}\r\n Current user: boremski (id=xx)\r\n Rendering common/error.html.erb within layouts/base\r\n Rendered common/error.html.erb within layouts/base (1.0ms)\r\n Rendering inline template\r\n Rendered inline template (0.8ms)\r\n Rendered plugins/redmine_tags/app/views/tags/_header_assets.html.erb (0.4ms)\r\n Rendered plugins/additionals/app/views/additionals/_html_head.html.slim (0.6ms)\r\n Rendered plugins/additionals/app/views/additionals/_body_top.slim (0.2ms)\r\n Rendered plugins/redmine_local_avatars/app/views/hooks/redmine_local_avatars/_base_body_bottom.erb (0.3ms)\r\n Rendered plugins/time_logger/app/views/time_loggers/_embed_menu.html.erb (18.9ms)\r\n Rendered plugins/time_logger/app/views/time_loggers/_update_menu.html.erb (20.0ms) [cache hit]\r\n Rendered plugins/additionals/app/views/additionals/_body_bottom.html.slim (0.3ms)\r\nCompleted 404 Not Found in 156ms (Views: 134.0ms | ActiveRecord: 10.3ms)\r\n \r\n\r\nFurther information:\r\n* redmine runs as root on our system\r\nSo I dont think this might eb an issue with access-rights.\r\nTo verify I changed the ownder of the repo-folder recursively.\r\nNo change.\r\n* I also tried to use a soft-link to this folder.\r\nalso no change.\r\n\r\nMaybe there is an issue with the @ in the path?\r\n\r\nSystem-Informations:\r\n\r\nEnvironment:\r\n Redmine version 4.1.2.stable.20855\r\n Ruby version 2.5.5-p157 (2019-03-15) [x86_64-linux-gnu]\r\n Rails version 5.2.4.5\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\nSCM:\r\n Subversion 1.10.4\r\n Git 2.20.1\r\n Filesystem \r\nRedmine plugins:\r\n additionals 3.0.2-master\r\n msproject_import 0.6\r\n redmine_issue_evm 5.5.1\r\n redmine_local_avatars 1.0.5.2.0\r\n redmine_mail_from 2.0.0\r\n redmine_subtask_list_accordion 2.2.0\r\n redmine_tags 4.0.0\r\n redmine_workload 1.1.0\r\n time_logger 0.5.4\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-08-04T07:40:25Z", "updated_on": "2021-08-04T07:40:25Z"}, {"id": 35679, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Ignore text email parts only stating that the email should be viewed as HTML", "description": "As already discussed in #30838 some emails now contain \"Your email client does not support HTML messages.\" in the text part and the interesting bits in the HTML part. This can be solved with the \"prefer HTML\" setting introduced in #30838.\r\n\r\nWe would like to propose a patch to still ignore email text parts stating \"Your email client does not support HTML messages.\" or similar with a blacklist. This way users preferring text parts and/or not aware of the new option do not need to see those parts in Redmine.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-03T20:06:47Z", "updated_on": "2021-08-03T20:14:12Z"}, {"id": 35677, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 40856, "name": "Jens Kr\u00e4mer"}, "category": {"id": 26, "name": "Text formatting"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Preserve leading white space when quoting using the JS toolbar", "description": "the attached patch changes the quote/unquote toolbar.js regular expressions so they preserve leading spaces. This is helpful i.e. when quoting blocks of code.", "done_ratio": 0, "created_on": "2021-08-03T10:54:01Z", "updated_on": "2021-08-04T08:07:19Z"}, {"id": 35676, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 53, "name": "Performance"}, "subject": "Optimize performance of syntax highlighting implementation", "description": "* re-implement performance optimizations of #26055\r\n* don't send input through syntax highlighting if it:\r\n** does not need to be highlighted, or\r\n** can not be highlighted\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-03T10:11:22Z", "updated_on": "2021-08-03T10:11:22Z"}, {"id": 35674, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 10, "name": "UI"}, "subject": "Several improvements (with fixes of inconsistencies) for the issues show view", "description": "I'll leave an untested WIP-patch against current trunk.\r\n\r\nChange descriptions by file:\r\n\r\n* +_app/views/issues/show.html.erb_+\r\n** blank (unset) value rendering of issue core attributes (currently a dash [@-@] is rendered for several attributes, while nothing is rendered for other attributes):\r\n*** consistently render a dash for issue core attributes with a blank (unset) value\r\n** spent time rendering (currently the field is not rendered when there's no spent time on the issue):\r\n*** consistently show the field and render a dash when there's no spent time on the issue (if spent time module is disabled the field and dash won't be rendered)\r\n** blank description rendering (currently the field is not rendered when it has a blank [unset] value):\r\n*** consistently show the field and render a dash for blank description attribute (partly the same as #24015)\r\n** full-width custom field rendering (the field is rendered below the attachments section):\r\n*** render the field above the attachments section (and below the description core attribute)\r\n\r\n* +_app/helpers/issues_helper.rb_+\r\n** blank (unset) value rendering of issue core attributes for related issues and subtasks sections (currently nothing is rendered):\r\n*** consistently render a dash for issue core attributes with a blank (unset) value for related issues and subtasks sections\r\n** estimated time rendering (currently the field value always shows the 'Total:' label):\r\n*** consistently show the field and render a dash when there's no estimated time on the issue, and only show the 'Total:' label with value when it is appropriate\r\n** blank (unset) value rendering of half-width issue custom field attributes (currently nothing is rendered for custom field attributes):\r\n*** consistently render a dash for half-width issue custom field attributes with a blank (unset) value\r\n** full-width custom field rendering (currently the field is not rendered when it has a blank [unset] value):\r\n*** consistently render a dash for full-width issue custom field attributes with a blank (unset) value\r\n\r\nSome notes and warnings on the patch:\r\n* contains no tests, doesn't modify existing tests and might break existing tests\r\n* doesn't modify email templates and/or API views\r\n\r\nI'd like to get some feedback on the mentioned changes before I spend more time on this patch.", "done_ratio": 0, "created_on": "2021-08-03T02:33:54Z", "updated_on": "2021-08-03T02:33:54Z"}, {"id": 35671, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Move subtasks section on issues show view into a separate partial", "description": "Subject says it all.\r\n\r\nI'll attach a patch that does this.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-02T23:30:35Z", "updated_on": "2021-08-02T23:38:40Z"}, {"id": 35670, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 40, "name": "Issues planning"}, "subject": "Graphs in the Issues Report details are too large.", "description": "I think the subject says it all. They should be resized to a more subtle size.\r\n\r\nAdditionally, they should be made printable too as they currently don't size well when they are printed (they are cut-of when they exceed page sizes).", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2021-08-02T23:04:52Z", "updated_on": "2021-08-02T23:04:52Z"}, {"id": 35669, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 40, "name": "Issues planning"}, "subject": "Prints of Issues Report details are messed-up due to the size of the graphs", "description": "When printing the Issues Report details I get lots of unwanted pages due to the large graphs (graph sizes should additionally be decreased independent of this issue, though [see #35670]) that are beneath the table. And the graphs that are actually printed are messed-up due to their size too.\r\n\r\nI think the best solution currently is to hide the charts when printing, like so:\r\n\r\n\r\ndiff --git a/app/views/reports/_details.html.erb b/app/views/reports/_details.html.erb\r\nindex 9b8f3b5e5..701591c74 100644\r\n--- a/app/views/reports/_details.html.erb\r\n+++ b/app/views/reports/_details.html.erb\r\n@@ -25,10 +25,10 @@\r\n <% end %>\r\n \r\n \r\n-\r\n+
\r\n \"> \r\n
\r\n-
\r\n+
\r\n
\r\n <%= javascript_tag do %>\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2021-08-02T22:56:15Z", "updated_on": "2021-08-02T23:06:13Z"}, {"id": 35667, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 40, "name": "Issues planning"}, "subject": "Consider generalization of My page block mechanism for use on the Issues Reports view", "description": "Given the current implementation of the Issues Reports view it might be sensible to generalize the My page block mechanism and re-implement the Issues Reports view to use that generalization. This would provide:\r\n* addition of user personalization of the Issues Reports view\r\n* addition of plugin extensibility of the Issues Reports view", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-02T16:08:05Z", "updated_on": "2021-08-02T16:08:05Z"}, {"id": 35666, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 2, "name": "Issues"}, "subject": "Review incorrect usage of Setting.display_subprojects_issues", "description": "@Setting.display_subprojects_issues@ was originally intended to provide a default value that can be overridden by users. It's used in several other places now too where the user might not have the ability to override its value while it would still make sense to provide the user this ability. These usages should be reviewed and fixed if necessary.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-08-02T13:42:53Z", "updated_on": "2021-08-02T13:42:53Z"}, {"id": 35664, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 40, "name": "Issues planning"}, "subject": "Inconsistencies in rendering of subproject data on Issues Reports", "description": "There are several inconsistencies in rendering of subproject data on Issues Reports after the addition of subprojects-inclusion introduced in #2529 and its extension by #34185. I've put my findings in a table:\r\n\r\n|_<. Block: |_<. Shows subproject values: |_<. Shows subproject data: |\r\n|_<. _Tracker_ | yes, if with_subprojects=1 | yes, if with_subprojects=1 |\r\n|_<. _Priority_ | yes, always ** | yes, if with_subprojects=1 |\r\n|_<. _Assignee_ | no | yes, if with_subprojects=1 and only if subproject value is available in current project |\r\n|_<. _Author_ | no | yes, if with_subprojects=1 and only if subproject value is available in current project |\r\n|_<. _Version_ | yes, always | yes, if with_subprojects=1 |\r\n|_<. _Subproject_ * | yes, always * | yes, always * |\r\n|_<. _Category_ | no | no |\r\n\r\n|_\\3. Legend: |\r\n|
* | = | only shown when @@project.children.any? == true@ |\r\n|
** | = | these values are global |\r\n| with_subprojects=1 | = | @Setting.display_subprojects_issues == 1@ |", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "99"}], "created_on": "2021-08-02T13:26:16Z", "updated_on": "2021-08-02T13:26:16Z"}, {"id": 35663, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 434198, "name": "Simeon Trifonov"}, "category": {"id": 32, "name": "REST API"}, "subject": "Access custom fields in project specific activities via Redmine API", "description": "I created a custom field in the activities that should contain different code for each activity. Also the codes could be different in the different projects. This is supported from Redmine and works fine.\r\n\r\n!activities.png!\r\n\r\nI tried to access this data from outside (using Python-Redmin library) and it seems to be impossible. The developers of the library said that this is not supported from the Redmine API and they cannot solve this problem. I will appreciate extension of the Redmine API that will allow access to custom fields in the activities.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-02T11:26:44Z", "updated_on": "2021-08-02T13:26:55Z"}, {"id": 35658, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 531763, "name": "Sebastian Hunziker"}, "category": {"id": 17, "name": "Permissions and roles"}, "subject": "Administration -> Role -> Users Visibility", "description": "In the dropdown list menu, adding \"None users\" as an option. For some approaches, It would be really useful to be able to select this option to set up a role that can be part of a project but cannot see other members.\r\n\r\n!RoleUserVisibility.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-01T17:48:18Z", "updated_on": "2021-08-02T10:31:12Z"}, {"id": 35657, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 2, "name": "Issues"}, "subject": "Spent time ratio column and filter", "description": "I suggest adding a new column and a new filter to the issues list.\r\n\r\nThe name of the column and the filter is \"Spent time ratio\". \"Spent time ratio\" column displays the percentage of a spent time divided by an estimated time. The column is useful to see the sign of overspending of man-hours and find issues that took more time than estimated.\r\n\r\n\"Easy Redmine\":https://www.easyredmine.com/ already has the same column and filter.\r\n\r\n!{width: 1023px; border: 1px solid grey;}.spent-time-ratio.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-08-01T14:07:22Z", "updated_on": "2021-08-01T14:26:31Z"}, {"id": 35656, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 15, "name": "Importers"}, "fixed_version": {"id": 33, "name": "Candidate for next minor release"}, "subject": "When importing issue relations, the validation messages are not shown in the UI", "description": "If you import a CSV with invalid relations, the validations messages are not shown in the UI.\r\n\r\nThe attached CSV can be used to reproduce the problem and it should generate the following error in the logs:\r\n
\r\nActiveRecord::RecordInvalid (Validation failed: Related issue cannot be blank):\r\n \r\napp/models/issue_import.rb:289:in `block (2 levels) in build_relations'\r\napp/models/issue_import.rb:252:in `each'\r\napp/models/issue_import.rb:252:in `block in build_relations'\r\napp/models/issue_import.rb:248:in `each_key'\r\napp/models/issue_import.rb:248:in `build_relations'\r\napp/models/issue_import.rb:244:in `extend_object'\r\napp/models/import.rb:215:in `block in run'\r\napp/models/import.rb:142:in `block in read_items'\r\napp/models/import.rb:256:in `block in read_rows'\r\napp/models/import.rb:255:in `read_rows'\r\napp/models/import.rb:136:in `read_items'\r\napp/models/import.rb:194:in `run'\r\napp/controllers/imports_controller.rb:91:in `run'\r\nlib/redmine/sudo_mode.rb:61:in `sudo_mode'\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-08-01T14:06:13Z", "updated_on": "2021-08-01T14:06:13Z"}, {"id": 35655, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 2, "name": "Issues"}, "fixed_version": {"id": 170, "name": "4.2.3"}, "subject": "Create duplicated follows relations fails with 500 internal error", "description": "It seems that the relation validations are not covering all the cases and if you try to add two duplicated follows relations, the request fails with 500 internal error. The issue reproduces only on 4.2.* versions and it's caused by #33418.\r\n\r\n
\r\nI, [2021-08-01T16:29:31.426087 #19530] INFO -- : Completed 500 Internal Server Error in 117ms (ActiveRecord: 70.3ms | Allocations: 8146)\r\n\r\n\r\nF, [2021-08-01T16:29:31.427135 #19530] FATAL -- : \r\nActiveRecord::RecordNotUnique (Mysql2::Error: Duplicate entry '1-2' for key 'issue_relations.index_issue_relations_on_issue_from_id_and_issue_to_id'):\r\n \r\napp/controllers/issue_relations_controller.rb:67:in `block in create'\r\napp/controllers/issue_relations_controller.rb:51:in `each'\r\napp/controllers/issue_relations_controller.rb:51:in `create'\r\n\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-08-01T13:41:29Z", "updated_on": "2021-08-05T23:52:23Z"}, {"id": 35648, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "subject": "Changelog generator should allow merging two or more versions", "description": "The script used to generate the changelog for releases should allow merging two or more versions.\r\n\r\nFor example, for the latest releases, we generated the changelog for two versions:\r\n* 4.1.4\r\n* 4.2.2 \r\n\r\nThe changelog for 4.2.2 should contain also the changes for 4.1.4, but the script doesn't do this and we need to manually merge the changelogs which is very error-prone.\r\n\r\nAlso, the script should allow authorised requests in order to pull the security issues which are private at the time of the releases. The authorization should use environment variables.", "done_ratio": 0, "created_on": "2021-08-01T08:15:59Z", "updated_on": "2021-08-01T08:15:59Z"}, {"id": 35647, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 40, "name": "Issues planning"}, "subject": "Allow the user to properly override Setting.display_subprojects_issues on Issue Reports if a project has subprojects", "description": "I'd like to know if there is interest in a feature like this:\r\n\r\n!{width:95%;}.2021-07-31_10-49-52.gif!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-31T13:04:38Z", "updated_on": "2021-08-03T00:31:59Z"}, {"id": 35645, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 10, "name": "UI"}, "subject": "Request for reconsideration of removal of 'View all issues' link", "description": "Yesterday I started doing some development work on Redmine again. The first thing that I stumbled upon was that the 'View all issues' link in the issues sidebar was removed in r18304. Although I see the merit of its removal with #30294, it really annoys me not having that link available (to such an extend that I quickly created a \"small plugin\":/plugins/redmine_add_all_issues_link_in_issues_sidebar to restore it on the issues show view).\r\nThe reason for this annoyance is that it was the only way to clear the current, not-saved query straight from the issues show view without first going back to the issues index view and then subsequently clicking on the clear button. With the link on issues show it is possible to go back to the default issues list without the need of an additional click on the clear button to clear the in-memory query. All the other (currently available) links that go back to the issues index view (project menu and query links on the index show view) retain the current query.\r\n\r\nSo, to make a long story short, I'd like to request a reconsideration of the decision for the removal of this link. This is also rooted in the fact that I think more (power) users will be/have been bitten by this change.\r\n\r\nFTR:\r\n* I have no problems with the move of the other links ('Summary' and 'Import') to the drop-down menu. This request is just about the 'View all issues' link.\r\n* I haven't looked into the changes of the 'Spent time' sidebar yet, but the points of the 'Issues sidebar' might also apply to those views.\r\n* If the removal decision is indeed reverted then it would be viable to subsequently also revert the addition of the clear query buttons added in #31640, as they would become obsolete if the 'View all issues' link is added back in.\r\n* I am also ok if my request will be declined. I'll then just keep using my plugin to restore the old situation...\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-30T17:14:42Z", "updated_on": "2021-07-31T13:20:05Z"}, {"id": 35642, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 2, "name": "Issues"}, "fixed_version": {"id": 169, "name": "4.1.5"}, "subject": "Long text custom field values are not aligned with their labels", "description": "See the screenshot below. You will see an unnecessary gap above the value of a custom field if all of the following conditions are met:\r\n\r\n* The format of the custom field is \"Long text\"\r\n* Text formatting is enabled for the custom field\r\n\r\nThe attached patch fixes the UI issue.\r\n\r\n!{width: 346px; border: 1px solid grey;}.custom-value-is-not-aligned-with-label.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Fixed"}, {"id": 4, "name": "Affected version", "value": "164"}], "created_on": "2021-07-30T02:36:45Z", "updated_on": "2021-08-05T21:51:36Z"}, {"id": 35640, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 361957, "name": "Eugenia B."}, "category": {"id": 2, "name": "Issues"}, "subject": "select / deselect watchers with one click when I copy a single issue", "description": "I have issues with more than 10 watchers and I want to copy the issues without watchers .\r\nIt would be better not to deselect the watchers one by one.\r\n\r\nI want to select / deselect watchers with one click when I copy a single issue\r\n\r\nAlso, I would like to have the option to add a new checkbox to copy watchers when I copy a single issue\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-29T19:49:13Z", "updated_on": "2021-07-30T00:32:03Z"}, {"id": 35627, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 445357, "name": "token ring"}, "subject": "Database schema", "description": "Please publish latest database schema", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-28T14:04:16Z", "updated_on": "2021-07-28T14:04:16Z"}, {"id": 35626, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 445357, "name": "token ring"}, "category": {"id": 11, "name": "Projects"}, "subject": "Prevent close project", "description": "Please add feature to prevent closing project with opened tasks\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-28T14:03:31Z", "updated_on": "2021-07-28T14:03:31Z"}, {"id": 35616, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 10, "name": "UI"}, "subject": "Remove \"Delete\" from the context menu for related issues", "description": "A related issue has a context menu that is invoked by right-clicking the issue.\r\n\r\nIt contributes to improving usability, but it also causes certain misoperation. This is the accidental deletion of an issue. Sometimes users misunderstand \"Delete\" in the context menu as a menu item to delete the issue relation, and accidentally delete the issue. I have seen such users many times.\r\n\r\nI don't think there are many cases where you want to delete issues in the \"Related issues\" section. In my opinion, It is rather harmful to have \"Delete\" in the menu.\r\n\r\nI suggest removing the \"Delete\" from the context menu in order to avoid such accidents.\r\n\r\n!{width: 393px; border: 1px solid grey;}.delete-in-context-menu.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-27T13:19:13Z", "updated_on": "2021-07-27T19:00:41Z"}, {"id": 35613, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 12, "name": "Translations"}, "subject": "German translation update of wiki_syntax_markdown.html", "description": "Related to #35375, I have updated untranslated de/wiki_syntax_markdown.html based on de/wiki_syntax_textile.html.\r\n\r\nSince I don't understand German, I didn't add any new translations. All translations are from de/wiki_syntax_textile.html.", "done_ratio": 0, "created_on": "2021-07-27T07:45:57Z", "updated_on": "2021-08-06T21:28:51Z"}, {"id": 35608, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 530723, "name": "anderson henrique de oliveira"}, "subject": "ActionView::Template::Error", "description": "
\r\nActionView::Template::Error (Tried to load unspecified class: ActiveSupport::HashWithIndifferentAccess):\r\n 6: \r\n 7: <%= label_tag available_tag_id, l(:description_available_columns) %>\r\n 8: <%= select_tag 'available_columns',\r\n 9: options_for_select(query_available_inline_columns_options(query)),\r\n 10: :id => available_tag_id,\r\n 11: :multiple => true, :size => 10,\r\n 12: :ondblclick => \"moveOptions(this.form.#{available_tag_id}, this.form.#{selected_tag_id});\" %>\r\n\r\napp/models/custom_field.rb:194:in `full_width_layout?'\r\napp/models/query.rb:129:in `initialize'\r\napp/models/issue_query.rb:227:in `new'\r\napp/models/issue_query.rb:227:in `block in available_columns'\r\napp/models/issue_query.rb:227:in `collect'\r\napp/models/issue_query.rb:227:in `available_columns'\r\napp/models/query.rb:751:in `available_inline_columns'\r\napp/helpers/queries_helper.rb:111:in `query_available_inline_columns_options'\r\napp/views/queries/_columns.html.erb:9:in `_app_views_queries__columns_html_erb__180106743509758731_39790100'\r\napp/helpers/queries_helper.rb:120:in `render_query_columns_selection'\r\napp/views/settings/_issues.html.erb:42:in `block in _app_views_settings__issues_html_erb___3907273758105470640_70343526728380'\r\napp/views/settings/_issues.html.erb:1:in `_app_views_settings__issues_html_erb___3907273758105470640_70343526728380'\r\napp/views/common/_tabs.html.erb:21:in `block in _app_views_common__tabs_html_erb___2021973252971248650_66522480'\r\napp/views/common/_tabs.html.erb:20:in `each'\r\napp/views/common/_tabs.html.erb:20:in `_app_views_common__tabs_html_erb___2021973252971248650_66522480'\r\napp/helpers/application_helper.rb:439:in `render_tabs'\r\napp/views/settings/edit.html.erb:5:in `_app_views_settings_edit_html_erb___2628854012480261892_66449720'\r\napp/controllers/settings_controller.rb:33:in `index'\r\nlib/redmine/sudo_mode.rb:65:in `sudo_mode'\r\n \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-07-26T13:18:50Z", "updated_on": "2021-07-27T12:01:26Z"}, {"id": 35582, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 529660, "name": "Robinson Torres"}, "category": {"id": 8, "name": "Administration"}, "subject": "Error: Template::Error (Tried to load unspecified class: ActiveSupport::HashWithIndifferentAccess)", "description": "Started GET \"/redmine/roles/3/edit\" for 192.168.1.1 at 2021-07-19 11:31:51 -0500\r\nProcessing by RolesController#edit as HTML\r\n Parameters: {\"id\"=>\"3\"}\r\n Current user: admin (id=1)\r\n Rendered roles/_form.html.erb (35.5ms)\r\n Rendered roles/edit.html.erb within layouts/admin (37.1ms)\r\nCompleted 500 Internal Server Error in 51ms (ActiveRecord: 6.7ms)\r\n\r\nActionView::Template::Error (Tried to load unspecified class: ActiveSupport::HashWithIndifferentAccess):\r\n 84: <%= hidden_field_tag \"role[permissions_all_trackers][#{permission}]\", '0', :id => nil %>\r\n 85: <%= check_box_tag \"role[permissions_all_trackers][#{permission}]\",\r\n 86: '1',\r\n 87: @role.permissions_all_trackers?(permission),\r\n 88: :class => \"#{permission}_shown\",\r\n 89: :data => {:disables => \".#{permission}_tracker\"} %>\r\n 90: \r\n app/models/role.rb:229:in `permissions_all_trackers'\r\n app/models/role.rb:238:in `permissions_all_trackers?'\r\n app/views/roles/_form.html.erb:87:in `block in _app_views_roles__form_html_erb___376610786332119881_69944433040580'\r\n app/views/roles/_form.html.erb:82:in `each'\r\n app/views/roles/_form.html.erb:82:in `_app_views_roles__form_html_erb___376610786332119881_69944433040580'\r\n app/views/roles/edit.html.erb:4:in `block in _app_views_roles_edit_html_erb___4451376381137512519_69944418235820'\r\n app/helpers/application_helper.rb:1190:in `labelled_form_for'\r\n app/views/roles/edit.html.erb:3:in `_app_views_roles_edit_html_erb___4451376381137512519_69944418235820'\r\n lib/redmine/sudo_mode.rb:63:in `sudo_mode'\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "134"}], "created_on": "2021-07-19T16:32:57Z", "updated_on": "2021-07-30T04:51:52Z"}, {"id": 35570, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 434111, "name": "C S"}, "category": {"id": 38, "name": "Themes"}, "subject": "Dynamically adjustable template options", "description": "\r\nAt the moment I use the template Purplemine (https://github.com/mrliptontea/PurpleMine2), because at least in the CSS file it offers the possibility to provide the trackers with different colored labels. This is particularly helpful in the Gant diagram to keep track of things. The colors are also used to highlight the respective IDs in the issue overview.\r\nIt would be even better if I could specify the colors directly in the definition of the tracker (Administration-> Tracker) myself", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-16T07:42:20Z", "updated_on": "2021-07-16T07:42:20Z"}, {"id": 35566, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 140010, "name": "shawn freeman"}, "category": {"id": 19, "name": "Attachments"}, "subject": "option to display thumbnails above file list in Documents", "description": "It would be nice to display the thumbnail of files/images, that are attached to an document, before the list of files (in some cases). I have a document enum to act as a catalog of images, and when the document has more than a few images, the users have to scroll down far to see the images. Here's a small example of the \"as is\", with the files listed BEFORE thumbnails (feature request is for AFTER).\r\n\r\n!Screenshot_20210714_203258.png!\r\n\r\nThank you!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-15T00:51:19Z", "updated_on": "2021-07-15T00:51:19Z"}, {"id": 35559, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 2, "name": "Issues"}, "subject": "Query links for related issues on issue page", "description": "Redmine 4.2.0 and later have query links for subtasks on an issue page (#28471). I think the \"Related issues\" section should also have similar links.\r\n\r\nAlthough there is no filter that can extract all types of related issues as mentioned in #28471, I think the new links can be implemented by using the issue ids filter (#4806).\r\n\r\n!{width: 769px; border: 1px solid grey;}.query-links-for-related-issues.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-13T02:02:47Z", "updated_on": "2021-07-29T13:21:50Z"}, {"id": 35558, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 400484, "name": "David Dole\u017eal"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Add button \"Send notification again\"", "description": "It happened today. I wrote issue's note wrong and saved it. Users got notification email with wrong information. So I edited my note, corrected all wrong parts (like url for pics, text, ...) and saved it. No notification was send. I think it's ok, because usually nobody change own note after save. But for admins can be usefull to send it again, for example when something crashed on SMTP, etc.\r\n\r\nSo can you add button *Send notification again* for issue journal and protect it with permission.\r\n\r\nHow I think about:\r\nOn issue head will be new button. When I click on it - it send notification about issue like I save it like a new.\r\nOn issue's notes will be new button. When I click on it - it send notication about issue's note like I save it like a new.\r\n\r\nFeel free for question. Maybe I didn't to describe it perfectly.... ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-07-12T11:56:10Z", "updated_on": "2021-07-12T17:15:31Z"}, {"id": 35557, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 361769, "name": "Liane Hampe"}, "category": {"id": 14, "name": "Custom fields"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Fix position when rendering custom field enumerations", "description": "The position of each custom field enumeration is integrated as hidden\r\nfield in the corresponding index.html.erb file.\r\n \r\nWhen iterating over all enumerations for a certain field, the iteration\r\nis done with an index information of the array, what contains all enumerations.\r\n \r\nThis index information again is used as the value for the position. \r\n\r\nThis is wrong, since the (array) index starts counting from zero whereas the position\r\nnumbers start counting from 1.\r\n \r\nThis is fixed now by increasing the position by 1 as stated below.\r\n\r\n
\r\ndiff --git a/app/views/custom_field_enumerations/index.html.erb b/app/views/custom_field_enumerations/index.html.erb\r\nindex 83e9d59c9..45398728f 100755\r\n--- a/app/views/custom_field_enumerations/index.html.erb\r\n+++ b/app/views/custom_field_enumerations/index.html.erb\r\n@@ -7,7 +7,7 @@\r\n <% @custom_field.enumerations.each_with_index do |value, position| %>\r\n \r\n \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-07-12T10:42:37Z", "updated_on": "2021-07-13T08:09:48Z"}, {"id": 35545, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 361769, "name": "Liane Hampe"}, "category": {"id": 2, "name": "Issues"}, "subject": "Fix css class assignment in issue custom field rendering in show view", "description": "Rendering the issue custom fields in the show view is done by the\r\nclass IssueFieldsRow, which can be found in issues_helper.rb.\r\n \r\nThe method IssueFieldRow#to_html has an error because the\r\nclass 'splitcontentright' will never be assigned.\r\n \r\nThis patch fixes this error by modifying the class in the respective\r\ncontent_tag of the helper method. Thus, it is a one liner.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-07-08T15:24:39Z", "updated_on": "2021-07-14T08:31:14Z"}, {"id": 35539, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 8, "name": "Reopened"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 40856, "name": "Jens Kr\u00e4mer"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 19, "name": "Attachments"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Race condition (possible filename collision) in Attachment.disk_filename", "description": "When two (or more) files with the same name are uploaded at the same time, it may happen that two or more of the resulting attachment records end up using the same disk file, resulting in data loss if the files actually differ in content. This was already previously mentioned in #34479-2 (but was unrelated to that issue and hence got \"lost\")\r\n\r\nThe problem is that @Attachment.disk_filename@ finds a non-existant filename, but fails to \"claim\" this name in the file system while doing so. So nothing stops a parallel process to end up using the same name if it tries to do so before the first process actually creates the file.\r\n\r\nThis patch, extracted from \"Planio\":https://plan.io/redmine-hosting , instead tries to create a file directly, with the @File::EXCL@ flag set, catches the error which means 'filename taken already' and retries until the file is created. This way, filenames are guaranteed to be unique by the underlying file system.\r\n", "done_ratio": 0, "created_on": "2021-07-07T05:25:26Z", "updated_on": "2021-08-08T01:52:53Z", "closed_on": "2021-07-19T13:28:21Z"}, {"id": 35536, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 486714, "name": "Takashi Kato"}, "subject": "Use webpack to improve javascripts and stylesheets management", "description": "I propose the use of webpack as a library management tool for javascript. I also suggest the use of \"simpacker\":https://github.com/hokaccha/simpacker as a tool for linking rails and webpack.\r\n\r\nThe docker environment can be found here.\r\n\r\nhttps://github.com/tohosaku/redmine-docker-wsl2\r\n\r\nh2. Motivation\r\n\r\n* To deal with the problem that #6662 \"js files are not compressed\"\r\n* To be a foundation for future npm package usage. ", "done_ratio": 0, "created_on": "2021-07-06T10:00:04Z", "updated_on": "2021-07-06T10:06:11Z"}, {"id": 35531, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 517334, "name": "anju dhiman"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "redmine unexpected undefined local variable or method `project'\" for mail handler , did you mean project_url", "description": "Hi,\r\n\r\nI am getting an error on Redmine while reading a particular email, error is :\r\nRedmine unexpected undefined local variable or method `project'\" for mail handler, did you mean project_url?\r\n\r\nEmail is getting read but it's not creating tickets in Redmine.\r\n\r\nCould you guys please help us?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-07-05T12:22:52Z", "updated_on": "2021-07-13T08:31:46Z"}, {"id": 35471, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 78650, "name": "Sergey Lobanov"}, "category": {"id": 12, "name": "Translations"}, "subject": "Split field_is_private to two labels for correct Russian translation", "description": "Currently, field_is_private is used for comments(notes) and issues\r\n\r\nFor English and many other languages it is OK to use the same word (\"Private\") for a comment(note) and an issue, but in Russian language the form of the adjective depends on the next word. (private comment in Russian is *\u0427\u0430\u0441\u0442\u043d\u044b\u0439* \u043a\u043e\u043c\u043c\u0435\u043d\u0442\u0430\u0440\u0438\u0439 or *\u041f\u0440\u0438\u0432\u0430\u0442\u043d\u044b\u0439* \u043a\u043e\u043c\u043c\u0435\u043d\u0442\u0430\u0440\u0438\u0439, but private issue in Russian is *\u0427\u0430\u0441\u0442\u043d\u0430\u044f* \u0437\u0430\u0434\u0430\u0447\u0430 or *\u041f\u0440\u0438\u0432\u0430\u0442\u043d\u0430\u044f* \u0437\u0430\u0434\u0430\u0447\u0430)\r\n\r\nSo it is required to have two labels, e.g. field_issue_is_private and field_note_is_private to make a correct translation to Russian.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-27T23:55:33Z", "updated_on": "2021-07-01T12:24:18Z"}, {"id": 35470, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 482687, "name": "Mark Tomm"}, "category": {"id": 27, "name": "Groups"}, "subject": "Create \"New Group\" results in HTTP code 500", "description": "h1. Redmine logs output\r\n\r\n\r\nApp 174 output: I, [2021-06-27T08:09:33.046085 #174] INFO -- : Started POST \"/redmine/groups\" for 172.30.23.1 at 2021-06-27 08:09:33 +0300\r\nApp 174 output: I, [2021-06-27T08:09:33.047230 #174] INFO -- : Processing by GroupsController#create as HTML\r\nApp 174 output: I, [2021-06-27T08:09:33.047325 #174] INFO -- : Parameters: {\"utf8\"=>\"\u2713\", \"authenticity_token\"=>\"XXXX\", \"group\"=>{\"name\"=>\"test\"}, \"commit\"=>\"Create\"}\r\nApp 174 output: I, [2021-06-27T08:09:33.115818 #174] INFO -- : Current user: XXXX (id=XXXX)\r\nApp 174 output: I, [2021-06-27T08:09:33.123919 #174] INFO -- : Completed 500 Internal Server Error in 76ms (ActiveRecord: 66.7ms)\r\nApp 174 output: F, [2021-06-27T08:09:33.125716 #174] FATAL -- : \r\nApp 174 output: F, [2021-06-27T08:09:33.125742 #174] FATAL -- : ActiveRecord::NotNullViolation (Mysql2::Error: Field 'mail_notification' doesn't have a default value: INSERT INTO `users` (`login`, `hashed_password`, `firstname`, `lastname`, `created_on`, `updated_on`, `type`) VALUES ('', '', '', 'test', '2021-06-27 08:09:33', '2021-06-27 08:09:33', 'Group')):\r\nApp 174 output: F, [2021-06-27T08:09:33.125773 #174] FATAL -- : \r\nApp 174 output: F, [2021-06-27T08:09:33.125792 #174] FATAL -- : app/controllers/groups_controller.rb:68:in `block in create'\r\nApp 174 output: app/controllers/groups_controller.rb:67:in `create'\r\nApp 174 output: lib/redmine/sudo_mode.rb:61:in `sudo_mode'\r\n \r\n\r\nh1. Redmine info\r\n\r\nRunning official Docker image without modifications (https://hub.docker.com/_/redmine/).\r\nWe have 3 plugins, info listed below.\r\n\r\n\r\nEnvironment:\r\n Redmine version 4.2.1.stable\r\n Ruby version 2.7.3-p183 (2021-04-05) [x86_64-linux]\r\n Rails version 5.2.5\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\nSCM:\r\n Subversion 1.10.4\r\n Mercurial 4.8.2\r\n Bazaar 2.8.0\r\n Git 2.20.1\r\n Filesystem \r\nRedmine plugins:\r\n redmine_checklists 3.1.18\r\n redmine_contacts 4.3.2\r\n redmineup_tags 2.0.8\r\n \r\n\r\nOur Redmine DB exists from 2011 (from 1.x to 4.x).\r\n\r\n*Setting.default_notification_option* check:\r\n\r\n\r\nroot@redmine:/usr/src/redmine# rails c p\r\nLoading production environment (Rails 5.2.5)\r\nirb(main):001:0> Setting.default_notification_option\r\n=> \"only_my_events\" \r\n \r\n\r\nh1. Notes\r\n\r\nThe same issue occurred in Redmine 3.x prior to migration to 4.2.1\r\n\r\nRelated issues: #34255\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-06-27T10:55:15Z", "updated_on": "2021-07-13T12:46:44Z"}, {"id": 35462, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 19, "name": "Attachments"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Download all attachments in a journal", "description": "Bulk attachments download for issues has been implemented in Redmine 4.2.0 (#7056). However, sometimes I want to download all attachments of a journal, not an issue.\r\n\r\nFor example, suppose that an issue already has dozens of files. In the most recent update, your colleague has attached 5 more files. In this case, it is not uncommon to want to download only the latest 5 files.\r\n\r\nI believe that bulk downloading of files for each journal is a very useful feature.\r\n\r\n!{width: 766px; border: 1px solid grey;}.bulk-download-journal-attachments.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-25T01:51:12Z", "updated_on": "2021-08-03T07:00:31Z"}, {"id": 35456, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 94920, "name": "James H"}, "category": {"id": 2, "name": "Issues"}, "subject": "Group of Users as Assignable Users per tracker", "description": "Sometimes we need trackers assignable to a group of individuals regardless of their membership/role on any projects.\r\nInstead of adding users or groups to every single project (defeating the use of members/roles), would like this feature:\r\n\r\nHave as an option per tracker, to allow selecting a Group as the list of assignable users instead of the current project members.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-24T20:17:18Z", "updated_on": "2021-06-24T20:17:18Z"}, {"id": 35454, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 365663, "name": "Markus Boremski"}, "category": {"id": 34, "name": "Gantt"}, "subject": "Gantt - Projectbars / (nearly) all Start on 2019-Oct-01", "description": "Could anyone tell me what exaclty causes the start-date of a project-bar in gantt?\r\nWe have about 800 projects and many of them seem to start on 01-oct-2019.\r\n!https://www.redmine.org/attachments/download/27621/2021-06-24%2012_57_33-Gantt-Diagramm.png!\r\n\r\nThis mostly happens for sub-projects, but not in general.\r\nIf I take a closer look on such a project and display all one can see that this project did not start on 01-oct-2019:\r\n!{width:600px;}https://www.redmine.org/attachments/download/27622/2021-06-24%2013_05_01-Gantt-Diagramm.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "162"}], "created_on": "2021-06-24T12:22:23Z", "updated_on": "2021-07-21T14:58:55Z"}, {"id": 35450, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 362529, "name": "Yuichi HARADA"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "subject": "Fixed an error message when registering an email address for a disallowed email domain", "description": "When registering an email address with a disallowed email domain with \"My account > Email\", the error message \"Email is invalid\" is displayed.\r\n\r\n!{width:400px;border:1px solid grey;}current-error-message.png!\r\n\r\nI don't understand what the error message wants to convey, so fixed the error message.\r\n\r\n!{width:400px;border:1px solid grey;}fixed-error-message.png!", "done_ratio": 0, "created_on": "2021-06-24T02:00:04Z", "updated_on": "2021-06-24T02:00:04Z"}, {"id": 35439, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 7, "name": "Accounts / authentication"}, "subject": "Option to require 2FA only for users with administration rights", "description": "#31920 adds the option to enable 2FA only for certain groups when the 2FA setting is set to optional. This is very useful, but it doesn't cover the case when you want to enable 2FA only for administrators. As a best security practice, if you cannot enforce for all users, the administrators should be top priority to secure using 2FA. \r\n\r\nMy proposal is to add a new setting to allow enforcing 2FA only for administrators:\r\n\r\n!{width:60%;}2fa_optional.png!\r\n\r\nWhat do you think?\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-22T21:23:00Z", "updated_on": "2021-06-23T08:34:24Z"}, {"id": 35435, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 123153, "name": "Pavel Rosick\u00fd"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 45, "name": "Gems support"}, "fixed_version": {"id": 170, "name": "4.2.3"}, "subject": "Psych 4: aliases in database.yml cause Psych::BadAlias exception", "description": "see for details\r\nhttps://github.com/ruby/psych/pull/487\r\nhttps://github.com/rails/rails/commit/1e56b1d1152e8ab74203db30625116844614cc78\r\n\r\npatch\r\n\r\ndiff --git a/Gemfile b/Gemfile\r\nindex b83cd2215..8f6bbe946 100644\r\n--- a/Gemfile\r\n+++ b/Gemfile\r\n@@ -52,7 +52,8 @@ require 'erb'\r\n require 'yaml'\r\n database_file = File.join(File.dirname(__FILE__), \"config/database.yml\")\r\n if File.exist?(database_file)\r\n- database_config = YAML::load(ERB.new(IO.read(database_file)).result)\r\n+ yaml_config = ERB.new(IO.read(database_file)).result\r\n+ database_config = YAML.respond_to?(:unsafe_load) ? YAML.unsafe_load(yaml_config) : YAML.load(yaml_config)\r\n adapters = database_config.values.map {|c| c['adapter']}.compact.uniq\r\n if adapters.any?\r\n adapters.each do |adapter|\r\n\r\nproduction: &alias\r\n adapter: mysql2\r\n database: xxx\r\n\r\ndevelopment: *alias\r\n \r\n\r\nerror\r\n\r\nCannot load database configuration: (Psych::BadAlias)\r\nUnknown alias: alias\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Fixed"}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-06-22T12:33:28Z", "updated_on": "2021-07-27T01:27:16Z"}, {"id": 35432, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 3, "name": "SCM"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "View annotate prior to the change", "description": "The \"Blame\" view of GitHub and Gitlab has a feature called \"View blame prior to this change\". With the feature, you can easily jump to an older change of the line.\r\n\r\nI think it would be useful if Redmine also has the feature. Currently, it requires some manual steps to see older changes in the \"Annotate\" view of Redmine.\r\n\r\n!{width: 634px; border: 1px solid grey;}.gitlab-view-blame-prior-to-this-change.png!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-22T08:01:18Z", "updated_on": "2021-07-24T07:58:36Z"}, {"id": 35431, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 140059, "name": "Mohamed Attya"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "send notifications to user selected from costum field (user type)", "description": "Hello all\r\ni need an immediate help please, i have an issue that i need to send the issue to more than one assignee and i cant add them in groups because the combination is changable, i add new costum field with type (user) but the selected user(s) from this menu doesnt receive any notifications and doesnt have permission to access this issue.\r\ni tried a plugin with name (custom_users_as_assignees) but after i install the plugin my redmine fails and i have to remove the plugin from the directory to work.\r\nplease help me fixing this problem as i need it immediatly", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "99"}], "created_on": "2021-06-22T07:43:36Z", "updated_on": "2021-06-22T07:43:36Z"}, {"id": 35430, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 147409, "name": "salman mp"}, "category": {"id": 3, "name": "SCM"}, "subject": "Internal error when viewing revisions diff", "description": "When I want to view revisions diff in the one project repository tab, in the first try it is OK, but after refresh or try another revisions diff it throw internal server error 500.\r\nI found that is because of using any deface on 'layout/base'. ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "162"}], "created_on": "2021-06-21T10:39:50Z", "updated_on": "2021-07-01T15:23:33Z"}, {"id": 35429, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 310708, "name": "Martina A."}, "category": {"id": 2, "name": "Issues"}, "subject": "Ticket assignement only to groups not to single users", "description": "https://www.redmine.org/boards/2/topics/65690\r\n\r\nWould be really great, if you can consider this for next update.\r\nMany thanks.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-21T10:27:37Z", "updated_on": "2021-06-22T01:33:33Z"}, {"id": 35422, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 443869, "name": "Martin Hierholzer"}, "category": {"id": 34, "name": "Gantt"}, "subject": "Make timeline in Gantt chart sticky", "description": "When having a bit Gantt chart with many tickets, the timeline is no longer visible after scrolling down. This makes it hard to understand the chart. Also the horizontal scroll bar is always at the very bottom of the chart, so scrolling horizontally is not easy (unless using Shift + scroll wheel in Firefox).\r\n\r\nI think it would be ideal to have the vertical scroll bar similar as the horizontal via css overflow:scroll, such that only the body of the chart scrolls and the header of the chart and the rest of the page stays in position.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-17T09:22:59Z", "updated_on": "2021-06-17T09:22:59Z"}, {"id": 35415, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 523899, "name": "Ludwig Meysel"}, "category": {"id": 20, "name": "Plugin API"}, "subject": "Unified plugin api esp. regarding patches", "description": "Many plugins use different ways to include own lib-code. A common topic I came across is applying patches and consuming hooks. Sometimes the files are @require@'d having something like\r\n\r\n\r\nunless FoobarController.included_modules.include? MyPlugin::Patches::FooControllerPatch\r\n FooController.send(:include, MyPlugin::Patches::FooControllerPatch)\r\nend\r\n \r\n\r\nin the bottom.\r\n\r\nSometimes the @require@ is wrapped in Reloader's @to_prepare@-callback (which seems quite useless to me), other plugins have some kind of @apply_patch@-method implemented, which does the same as the code above in a more generic manner (IMO the most elegant way to go).\r\n\r\nWhile all these techniques basically work, it often invites to mess up with the auto reloader. When doing some tweaks in the codebase (or even develop my own plugin), I either have to disable foreign plugins or painfully restart the dev-server with every change, when autoloading is not properly implemented. Otherwise I face the often reported problem of \"Cannot autoload Constant ...\"-Error.\r\n\r\nMy suggestion is to provide a more unified API for applying patches and consuming hooks.\r\n\r\nI could imagine a simple approach e.g. of an @appyl_patch@ function, which forwards the params to an array, which then is processed internally by the @ActiveSupport::Reloader.to_prepare@ callback.\r\n\r\nAnother (more opinionated) approach is to grab all patches from plugins/.../lib/patches/*.rb, after a plugin was registered, which also was applicable to the hooks.\r\n\r\nAnyways, I think there should be some mechanism to provide plugins safely, which do not mess up with the autoloader. This could also catch compatibility-stuff I have also often seen like @Rails.version < '5.1' ? ActionDispatch::Callbacks : ActiveSupport::Reloader@.to_prepare.\r\n\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-14T06:41:41Z", "updated_on": "2021-06-14T06:41:41Z"}, {"id": 35388, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 94920, "name": "James H"}, "category": {"id": 16, "name": "Search engine"}, "subject": "Search filters in top bar", "description": "Searching takes a very long time when there are lots of text fields included in the search.\r\n\r\nWould like a way to filter the search (projects, issues, etc.) from the top bar without going to the search page first.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-09T18:43:00Z", "updated_on": "2021-06-24T00:31:48Z"}, {"id": 35382, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 523420, "name": "Oz Ak"}, "subject": "Copy Project Tracker and Tasks and relations ", "description": "In order to manage our Implementation Project better, I created a Project X. In order to better organize our task I also created a tracker for Project. \r\n\r\nThe trackers I have are:\r\n* Project\r\n* Programming Request\r\n* Support\r\n* Bug\r\n* Training\r\n\r\nThe hierarchy of the project is as follow :\r\n\r\n* Project X\r\n** Project (Tracker) = Project Implementation\r\n*** Programming request 1 - Precedes (Support 2)\r\n*** Support 2 Precedes (Support 3)\r\n*** Support 3\r\n\r\nWhen I make a copy of the Project Implementation, the subtasks Programming request 1, Support 2, Support 3 do copy however the Precedes values does not copy over. \r\n\r\nAnyone else has this issue? \r\n\r\nIdeally what I would love to do is copy the Project Implementation as a template and push the dates based on the Project Implementation for other projects moving forward\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-06-09T13:39:24Z", "updated_on": "2021-06-09T13:39:24Z"}, {"id": 35373, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Improve project deletion warning text", "description": "This is related to #34417\r\n\r\nThe information text when deleting the user clearly states that deleting the user cannot be undone and that locking the user would be an alternative. This patch adds similar text stating the finality of deleting a project and the alternative of archiving the project to the project deletion information text.", "done_ratio": 0, "created_on": "2021-06-08T12:53:10Z", "updated_on": "2021-06-26T10:05:21Z"}, {"id": 35362, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 53326, "name": "\u0412\u0438\u043a\u0442\u043e\u0440 \u0412\u043e\u0435\u0432\u043e\u0434\u0441\u043a\u0438\u0439"}, "category": {"id": 58, "name": "Issues list"}, "subject": "Issues list", "description": "Is it possible the user to see the problem only members of the group? A user \"developer\" has seen the problem of all groups.\r\nAs part of the project are connected by different organizations. There is a need that they are not seen by the task each other. Since each organization is a separate group, it is necessary that users see only the tasks of their group. \u0422ow there is only:\r\nissues_visibility_all\r\nissues_visibility_own\r\nissues_visibility_public\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-06T13:13:36Z", "updated_on": "2021-06-06T13:13:36Z"}, {"id": 35359, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 522962, "name": "Sangram Jadhav"}, "category": {"id": 59, "name": "Filters"}, "subject": "assignee dropdown list ascending order", "description": "How to filter assignee dropdown list by ascending order", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "145"}], "created_on": "2021-06-05T11:02:47Z", "updated_on": "2021-06-05T11:02:47Z"}, {"id": 35356, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 459447, "name": "Angelica Diaz"}, "category": {"id": 59, "name": "Filters"}, "subject": "subtasks field", "description": "Hello, is there the possibility to add \"subtasks\" field to build a query?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-04T14:28:31Z", "updated_on": "2021-06-04T14:28:31Z"}, {"id": 35355, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 522881, "name": "Roman K"}, "category": {"id": 7, "name": "Accounts / authentication"}, "subject": "Unable to create or edit users with Cyrillic logins", "description": "Used version: 4.2.1.stable (Bitnami Redmine Stack)\r\nTested on fresh new install.\r\nTested on upgraded from 4.0.3 install.\r\n\r\nI'm unable to create new or modify existing users with Cyrillic login. Error is: \u201cLogin is invalid\u201d.\r\n\r\nExisting user accounts works fine. Also, I can create user manually via direct DB queries without any problems.\r\n\r\nThere was no such problem on 4.0.3.\r\n\r\nAlready reported on Bitmani Forums, but this error occurs even on fresh new install, so I'm also report it here.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-06-04T11:20:49Z", "updated_on": "2021-06-06T19:42:11Z"}, {"id": 35349, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 522782, "name": "Ilya Belyaev"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Email notification when Issue description is updated", "description": "Hello! I have a question. How to send notifications when the Description field is updated. \r\nFor a number of reasons, I cannot mark check-box \"Issue updated\". Perhaps you can advise some plugin for advanced configuration of email notifications.\r\nI have tried adding fiel_description to journal.rb and notifiable.rb But I did not understand how to make to understand the change in value \"description\"\r\n\r\nMy setting for email notification is:\r\n\r\n!setting.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-06-03T08:57:54Z", "updated_on": "2021-06-03T08:57:54Z"}, {"id": 35345, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 74968, "name": "Massimo Rossello"}, "category": {"id": 20, "name": "Plugin API"}, "subject": "Redmine::Plugin::compare_versions fails with stable and devel branches", "description": "A plugin using Redine::Plugin::require_redmine always fails against stable and development branches. In fact, a version like e.g. 4.0.9.stable (from the latest 4.0.9 tag) can't be matched either against 4.0.9 or 4.0.9.0.\r\n\r\nAttached a workaround based on trunk, which is not satisfactory as it isn't using collect(&:to_i) in compare_versions. But it works.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-06-02T12:16:08Z", "updated_on": "2021-07-22T07:27:47Z"}, {"id": 35320, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 31416, "name": "Jim McAleer"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "When viewing spent time report the Activity, Issue Id and Subject are combined into a single column Issue yet there is no option for filtering on subject.", "description": "Please add the issue's subject as a column to filter by in the spent time reporting. Trying to filter the issue for anything in the subject does not work does not work!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "148"}], "created_on": "2021-05-27T16:02:16Z", "updated_on": "2021-05-27T16:02:16Z"}, {"id": 35309, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 484942, "name": "Immanuel Wilhelmy"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Hyperlinks ending in \"$\" will be truncated (the trailing \"$\" sign will not be part of the URL to be pointed to)", "description": "Hyperlinks ending in \"$\" will be truncated (the trailing \"$\" sign will not be part of the URL to be loaded).\r\n\r\ne.g.: \r\n\r\nhttps://this.is.a.example/withtrailing$ (hover over the URL and look what is shown in the browser status line, resp. you see the \"$\" is not contained in redmine's URL).\r\n\r\nOur Mail-URL-Scanner replaces incoming URLs with redirects to the scanner. The generated new URL contains a trailing \"$\", so the URLs are no more recognized by the scanner and do not work.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2021-05-25T12:33:01Z", "updated_on": "2021-05-26T08:29:57Z"}, {"id": 35298, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 397854, "name": "Wolf Gang"}, "category": {"id": 7, "name": "Accounts / authentication"}, "subject": "LDAP /auth_sources/autocomplete_for_new_user not working when multiple LDAP Servers", "description": "Hello!\r\n\r\nIn my setup I have several different LDAP Servers (~20) I try to query. When I add a new user the progress icon appears and stops after a while appearingly without success. After this for a while, the server returns \"Internal Error\" for a a while (< 1 minute). The following appears in the log files:\r\n\r\n\r\nI, [2021-05-23T20:34:25.442329 #1] INFO -- : Started GET \"/auth_sources/autocomplete_for_new_user?term=ex\" for 92.248.33.178 at 2021-05-23 20:34:25 +0000\r\nI, [2021-05-23T20:34:25.443289 #1] INFO -- : Processing by AuthSourcesController#autocomplete_for_new_user as JSON\r\nI, [2021-05-23T20:34:25.443327 #1] INFO -- : Parameters: {\"term\"=>\"ex\"}\r\nI, [2021-05-23T20:34:25.456248 #1] INFO -- : Current user: admin (id=1)\r\nI, [2021-05-23T20:34:34.971175 #1] INFO -- : Started GET \"/auth_sources/autocomplete_for_new_user?term=exs\" for 92.248.33.178 at 2021-05-23 20:34:34 +0000\r\nI, [2021-05-23T20:34:34.972246 #1] INFO -- : Processing by AuthSourcesController#autocomplete_for_new_user as JSON\r\nI, [2021-05-23T20:34:34.972279 #1] INFO -- : Parameters: {\"term\"=>\"exs\"}\r\nI, [2021-05-23T20:34:34.985667 #1] INFO -- : Current user: admin (id=1)\r\nI, [2021-05-23T20:34:35.275884 #1] INFO -- : Started GET \"/auth_sources/autocomplete_for_new_user?term=exsc\" for 92.248.33.178 at 2021-05-23 20:34:35 +0000\r\nI, [2021-05-23T20:34:35.276661 #1] INFO -- : Processing by AuthSourcesController#autocomplete_for_new_user as JSON\r\nI, [2021-05-23T20:34:35.276697 #1] INFO -- : Parameters: {\"term\"=>\"exsc\"}\r\nI, [2021-05-23T20:34:35.303692 #1] INFO -- : Current user: admin (id=1)\r\nI, [2021-05-23T20:34:35.701371 #1] INFO -- : Started GET \"/auth_sources/autocomplete_for_new_user?term=exsch\" for 92.248.33.178 at 2021-05-23 20:34:35 +0000\r\nI, [2021-05-23T20:34:35.702086 #1] INFO -- : Processing by AuthSourcesController#autocomplete_for_new_user as JSON\r\nI, [2021-05-23T20:34:35.702117 #1] INFO -- : Parameters: {\"term\"=>\"exsch\"}\r\nI, [2021-05-23T20:34:35.707769 #1] INFO -- : Current user: admin (id=1)\r\nI, [2021-05-23T20:34:38.076215 #1] INFO -- : Started GET \"/auth_sources/autocomplete_for_new_user?term=exsch\" for 92.248.33.178 at 2021-05-23 20:34:38 +0000\r\nI, [2021-05-23T20:34:38.076974 #1] INFO -- : Processing by AuthSourcesController#autocomplete_for_new_user as JSON\r\nI, [2021-05-23T20:34:38.077003 #1] INFO -- : Parameters: {\"term\"=>\"exsch\"}\r\nnot verifying SSL hostname of LDAPS server 'lh.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'lh.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'lh.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'lh.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\n172.18.0.7 - - [23/May/2021:20:34:39 UTC] \"GET /auth_sources/autocomplete_for_new_user?term=exscha HTTP/1.0\" 500 46\r\nhttps://noekis-test.lknoe.at/users/new -> /auth_sources/autocomplete_for_new_user?term=exscha\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'lh.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'am.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sp.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sp.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'lf.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'lf.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'tu.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sp.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wy.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'tu.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ks.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ks.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'kl.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'kl.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'zt.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sb.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ma.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'me.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sp.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'sp.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'zt.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wt.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'wt.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'gd.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'gd.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ho.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'ho.nk.lokal:636'\r\nnot verifying SSL hostname of LDAPS server 'mi.nk.lokal:636'\r\n172.18.0.7 - - [23/May/2021:20:34:56 UTC] \"GET /auth_sources/autocomplete_for_new_user?term=exscha HTTP/1.0\" 500 46\r\nhttps://noekis-test.lknoe.at/users/new -> /auth_sources/autocomplete_for_new_user?term=exscha\r\n \r\n\r\nI dont know how to further debug that so any support is highly appreciated.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-05-23T20:45:02Z", "updated_on": "2021-05-28T09:20:29Z"}, {"id": 35282, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 521309, "name": "hagay go"}, "category": {"id": 2, "name": "Issues"}, "subject": "Assign to former/previous assignee short cut", "description": "Hi,\r\n\r\nThe \"Assign to me\" (#29285) feature is very nice and i believe another shortcut would be beneficial.\r\n\r\nOn our team , issues are being assigned form person A to person B and sometimes there is a lot of \"ping pong\" between person A and person B.\r\n\r\nPerson A assigns the issue to person B with comments.\r\nPerson B adds his comments and assigns to issue to Person A.\r\nPerson A sees the comments and adds is own and assigns the issue to Person B.\r\n\r\nIf we'll have a \"Assign to Previous Assignee\" shortcut , it would saves us few clicks and manual user lookup from the drop down (we got 25+ users/groups on the list).\r\n\r\nThnaks in advance.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-23T06:44:54Z", "updated_on": "2021-05-23T06:44:54Z"}, {"id": 35281, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "[Meta] (Issues) Custom (and Standard) Fields Grouping and Positioning", "description": "This is a meta-issue to track all related issues concerning the subject and which acts as a singular entity for scheduling (instead of scheduling individual implementation proposals, like #30919).", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-23T04:28:33Z", "updated_on": "2021-05-23T04:28:33Z"}, {"id": 35270, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 94920, "name": "James H"}, "category": {"id": 2, "name": "Issues"}, "subject": "Grouping & Positioning of custom fields", "description": "For individual Issue view page format.\r\n\r\nWould like a more customizable way to group/position the custom fields.\r\nCurrently, trackers with many fields can be a blur of info and needs some grouping/spacers to make finding information faster/easier.\r\n\r\nRequest:\r\nThe most important part would be having a way to add grouping headers, spacers, or notes between custom fields per tracker that looks clean and assists in readability.\r\n\r\nIdeal:\r\nI think a custom positioning checkbox per tracker, and then allow custom indexing/ordering of custom fields and allow creating spacers and grouping headers with alignment and/or grid choices would be amazing.\r\n\r\nThis also could extend to project custom fields and other custom fields, but not really as useful as it would be for issues.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-20T20:50:46Z", "updated_on": "2021-05-21T05:22:13Z"}, {"id": 35268, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 291, "name": "Thomas L\u00f6ber"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "subject": "Issue.acts_as_searchable columns option cleanup", "description": "Hi,\r\n\r\nJust for the sake of completeness, in @Issue.acts_as_searchable@ the @columns@ option should specify the table name for both columns.\r\n\r\nA patch is attached.\r\n\r\nBest regards,\r\nThomas\r\n", "done_ratio": 0, "created_on": "2021-05-20T14:29:36Z", "updated_on": "2021-05-20T14:29:36Z"}, {"id": 35265, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 520824, "name": "Rajarshi Das"}, "subject": "Readmine: Create IssuePriority Enumeration give error", "description": "h2. I am using readmin 4.2\r\n\r\nwhile create a Issue Priority It give me error.\r\n\r\n [46, 55] in aa/enumerations_controller.rb\r\n 46: def new\r\n 47: end\r\n 48:\r\n 49: def create\r\n 50: byebug\r\n => 51: if request.post? && @enumeration.save\r\n 52: flash[:notice] = l(:notice_successful_create)\r\n 53: redirect_to enumerations_path\r\n 54: else\r\n 55: render :action => 'new'\r\n (byebug) @enumeration #\r\n\r\n\r\nand then I saw the below error\r\n\r\n\r\n (byebug) exception #\r\n\r\n\r\nI am not able to create any enuumeration in redmine\r\n\r\nany help", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-05-20T09:51:03Z", "updated_on": "2021-05-21T12:01:48Z"}, {"id": 35248, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 351215, "name": "Kam Nazir"}, "category": {"id": 37, "name": "I18n"}, "subject": "Hard-coded error messages in IssueStatus", "description": "Untranslated hard-coded string exists in source:trunk/app/models/issue_status.rb@20897#L113\r\n\r\ndef check_integrity\r\n if Issue.where(:status_id => id).any?\r\n raise \"This status is used by some issues\"\r\n elsif Tracker.where(:default_status_id => id).any?\r\n raise \"This status is used as the default status by some trackers\"\r\n end\r\nend\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-05-16T03:05:44Z", "updated_on": "2021-05-18T06:58:07Z"}, {"id": 35237, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 354376, "name": "Darko Palic"}, "category": {"id": 2, "name": "Issues"}, "subject": "Configure default ordering for new Users via global Settingsb", "description": "in #589 there was the fix implemented to allow users to decide.\r\nSo here a user can decide on his own to change the behavior on ordering/sorting the notes in issues.\r\n\r\nThis is good, but new users often do not know what this configuration means. So as a admin I would like to define the defaults for it. So a setting entry in /redmine/settings?tab=display would be great", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-14T06:30:14Z", "updated_on": "2021-05-14T06:30:14Z"}, {"id": 35225, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 116788, "name": "Sergio Serrano"}, "category": {"id": 2, "name": "Issues"}, "subject": "Edit issue shows date in MM/DD/YYYY while the rest of the application shows YYYY/MM/DD", "description": "Dear redmine community\r\n\r\nIssue list DD-MM-YYYY\r\n\r\nIssue detail DD-MM-YYYY\r\n\r\nIssue edit MM-DD-YYYY\r\n\r\nIssue list and Issue details follows redmine date configuration but issue edit always use the MM-DD-YYYY format.\r\n\r\nPlease, any advice what I'm doing wrong?\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "162"}], "created_on": "2021-05-11T06:39:45Z", "updated_on": "2021-05-12T10:50:04Z"}, {"id": 35224, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 518481, "name": "Marc Cramer"}, "category": {"id": 11, "name": "Projects"}, "subject": "Adding new project impossible with mandatory custom field of type users", "description": "Redmine: 4.1.2\r\nRails: 5.2.4.4\r\nPostgreSQL: 12.5\r\nNo Plugins\r\n\r\nI was just hit by this issue, kind of a logical bug:\r\n\r\nI cannot add a new project if there is a mandatory custom field with a user\r\ndrop-down list, since there are no users initially--but I cannot add users\r\nunless the project has been created...\r\n\r\nTo reproduce:\r\n\r\n- Add a custom field to projects\r\n- Field type: Users\r\n- Make the field mandatory\r\n- Try to add a new project\r\n\r\nExpected behaviour:\r\n\r\n- Find a prefilled list of users in the drop down\r\n- Able to submit (create new project)\r\n\r\nCurrent behaviour:\r\n\r\n- User list is empty (possibly because the project has no users?)\r\n- Toggling inheritage of users does not help\r\n- Cannot submit project because the custom field is still empty but mandatory\r\n\r\nWorkaround:\r\n\r\n- Make custom field optional\r\n- Add project (with empty user selection)\r\n- Add users to the project\r\n- Edit project again and select user from drop down list\r\n\r\n\r\nAm I missing something trivial?\r\n\r\nThanks\r\n\r\n\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "162"}], "created_on": "2021-05-10T19:35:59Z", "updated_on": "2021-05-14T12:05:54Z"}, {"id": 35221, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 259873, "name": "Mizuki ISHIKAWA"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Show public badge on project's overview page when the project is public", "description": "This is a feature related to #35044.\r\nAdding a badge in addition to #35044 's features will make it easier to notice that your project is public.\r\n!{width: 500px; border: 1px solid #ccc}screenshot.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-10T00:28:21Z", "updated_on": "2021-05-24T01:53:04Z"}, {"id": 35219, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 519732, "name": "Michaela Pawlowski"}, "category": {"id": 2, "name": "Issues"}, "subject": "Unable to add watchers to existing project in Redmine", "description": "We use Redmine within our organization for project management. Recently, we have noticed an issue where the \u201cadd\u201d button for watchers does not function for pre-existing projects. The \u201cadd\u201d button doesn\u2019t do anything when clicked; however, when adding watchers to a new project, the button works as expected. See below.\r\n\r\n!b19ea10232456ae82a5f7138696ea648.png!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-05-07T15:47:39Z", "updated_on": "2021-05-19T15:06:01Z"}, {"id": 35217, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 40856, "name": "Jens Kr\u00e4mer"}, "subject": "Replace use of Digest::MD5 / Digest::SHA1 with ActiveSupport::Digest", "description": "Rails introduced @ActiveSupport::Digest@ to allow central configuration of the actual digest implementation that is used throughout Rails. This is helpful in environments where certain digest implementations (most notably, MD5) are not available, i.e. to be \"FIPS\":https://www.nist.gov/itl/fips-general-information compliant.\r\n\r\nThe attached patch replaces all uses of @Digest::SHA1@ and @Digest::MD5@ with @ActiveSupport::Digest@. Without further configuration, this will result in @Digest::SHA1@ being used in all these instances since that's the current Rails default. This can be changed by users via the \"config.active_support.hash_digest_class setting\":https://github.com/rails/rails/pull/40213 , i.e.:\r\n\r\n\r\nRails.application.config.active_support.hash_digest_class = OpenSSL::Digest::SHA256\r\n \r\n", "done_ratio": 0, "created_on": "2021-05-07T03:02:16Z", "updated_on": "2021-05-07T13:14:53Z"}, {"id": 35215, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 470755, "name": "der gl0wn"}, "subject": "tribute.js third party library localization", "description": "Hello there,\r\n\r\nit would be very helpful if we would be able to change the \"No Match Found!\" message that is included via the third party library tribute.js. I could hardcode it into the file itself, but that just seems odd.\r\n\r\nBest regards", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-06T09:02:47Z", "updated_on": "2021-05-10T14:49:25Z"}, {"id": 35212, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3959, "name": "Shaun Gilroy"}, "category": {"id": 2, "name": "Issues"}, "subject": "Issues controller_issues_edit_* hooks not firing on bulk edit actions", "description": "I'm not sure if this was the intended functionality or not, but it seems like a bug to me. We discovered in our installation of redmine 4.2.0.stable that when issues are edited through bulk update actions (right clicking from the issue list) that the following hooks do not trigger:\r\n\r\n* controller_issues_edit_before_save\r\n* controller_issues_edit_after_save\r\n\r\nUpon closer examination of the system, I discovered that the IssueController.bulk_update method does not call the before and after issue.save\r\n\r\nThis seems like an unintentional oversight, so I'm reporting it here. We fixe the issue by simply editing the method in our copy of the application. But this only fixes the issue for us.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-05-05T16:20:23Z", "updated_on": "2021-05-05T16:20:23Z"}, {"id": 35199, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 12098, "name": "Martin Cizek"}, "category": {"id": 20, "name": "Plugin API"}, "subject": "HookTest resets all listeners - core tests run inconsistently with plugins", "description": "When a test runner is invoked and the tests include either @test/integration/lib/redmine/hook_test.rb@ or @test/unit/lib/redmine/hook_test.rb@, there is a side effect that all hooks classes / listeners are cleared. It is probably related to hook listeners being stored in class variables.\r\n\r\nThis may affect other tests, but most importantly, it makes it difficult to verify redmine core integrity with plugins in place. While plugins' patches are still applied, the listeners are not guaranteed and the results differ between e.g. @rake test@ and @rake test:functionals@.\r\n\r\nMore info about the context below.\r\n\r\n---\r\n\r\nAlthough this might not be necessarily a defect - maybe core tests are not supposed to run with plugins - the consequences of plugin developers not running the core tests are terrible and affect the reputation of whole Redmine ecosystem.\r\n\r\nWhat we've observed:\r\n* We have run Redmine core tests with plugins we use.\r\n* It's even difficult to find a plugin that doesn't break anything in the core.\r\n* A logical objection would be \"plugins modify core functionality, so it's normal that core tests are not passing\". But this turned out NOT to be the case. In fact:\r\n* Around 50% of the errors and failures are that the implementation is not robust enough to withstand testing.\r\n* And the other 50% are user-reproducible bugs, which would have been discovered if core tests had been run.\r\n* In the end, we have not observed any error or failure caused by intentional plugin behavior.\r\n\r\nBased on your feedback, I can provide specific examples and will be happy to update [[plugin_tutorial]] to encourage core testing.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-05-02T22:57:12Z", "updated_on": "2021-05-10T19:26:57Z"}, {"id": 35196, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 519176, "name": "Philippe Cloutier"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Version tracking (allow filtering out tickets which don't affect given version)", "description": "I am new to Redmine, but one basic feature which appears to be missing is version tracking. There are 2 angles in which version tracking helps:\r\n# It clarifies which versions a given issue affects (mostly relevant to developers).\r\n# It allows to filter out issues which do not affect the version relevant (mostly relevant to users).\r\n\r\nFor me, #2 is the most important benefit. For example, Redmine currently has over 10 thousand issues reported. But it may be that fewer than 5 thousand of these affect the current version (4.2.1). It is therefore critical to properly evaluating a product to have the ability to limit displayed tickets. It is also seriously inefficient to search and report issues in mature software without such a feature.\r\n\r\nA basic scenario is that if a certain issue x is solved in version 2.0, then that issue does not affect version 2.0. However, there are more complex cases. For example, that same issue does not affect version 2.1, as version 2.1 is ulterior to 2.0.\r\n\r\nUnfortunately, this can get tricky. There are cases where a solution is reverted. For example, if issue A is reintroduced in version 2.2, then version 2.3 may be affected, even if it is ulterior to 2.0.\r\n\r\nEven for simpler cases when an issue is solved once for good, branches complicate things. For example, if issue B affects version 1.0.0 but is fixed in version 1.0.3, is version 1.1 affected? Without more information, that cannot be answered.\r\n\r\n\r\nThe ITS engine which properly implements this that I know is Debbugs: https://lwn.net/Articles/144106/\r\nA demonstration of aspect #1 can be seen on \"this libkate issue's graphic\":https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;collapse=1;fixed=libkate%2F0.4.1-5;format=png;found=libkate%2F0.4.1-4;height=;info=1;package=liboggkate-dev;width=;ignore_boring=0\r\nRed versions are affected, green versions are not. Grey versions are those about which the ITS cannot decide.\r\n\r\nDebbugs's approach is to scan changelogs to compute a version ancestry tree. This is very efficient, but based on Debian's mandatory and uniform changelogs. This approach won't readily be usable with Redmine. An alternative would be to enhance versions management allowing administrators to manually build their product's version ancestry tree, or to start with basic semantic inference (if an issue is solved in version 2.0.0, it does not affect versions 2.1.0 and ulterior).\r\n\r\n\r\nThere are several types of version indications possible.\r\n# The best indications are certain, based on code analysis. For example, if a commit which clearly introduces a defect is made between versions 2.0.1 and 2.0.2, then we can indicate in the ticket that version 2.0.2 introduces the issue.\r\n# Very often, indications are unfortunately not so certain, and based on behavior. For example, if a test reveals a defect in version 2.0.1 and the same test does not reveal the same defect in version 2.0.0, we have an indication that version 2.0.1 may have introduced that defect, whose certitude depends on how reproducible the bug is.\r\n\r\nIdeally, tickets could take precise indications about issue introductions and solutions, and Redmine would be able to tell, for any given issue and product version, the risks that it is affected. For example, a given version may:\r\n* *Not be affected* by issue _x_\r\n* *Be affected* by issue _y_\r\n* *Have a 1 in 5 chance of being affected* by issue _z_\r\n\r\nIn practice, that would be quite an achievement. It would already be vastly superior to match Debbugs and simply manage to tell *whether an issue affects, doesn't affect, or may affect* a version, and I will consider this issue solved once that level has been reached.\r\n\r\n\r\nBuilding blocks necessary to achieve this include the aforementioned version indications (possibility to mark certain versions as affected and/or introducing issues, as well as the converse possibility to mark as unaffected and/or solving). This building blocks are treated in ticket #685 (found in version) and ticket #219 (fixed in multiple versions). Defining a version inheritance tree is related to ticket #18126.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-05-02T21:25:03Z", "updated_on": "2021-05-02T21:25:03Z"}, {"id": 35192, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 519068, "name": "Jean-Ren\u00e9 ROUET"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 2, "name": "Issues"}, "subject": "Watchers pop up window appears after a long time", "description": "Hi\r\n\r\npatch #33329 introduces a performance issue\r\n\r\nWhen you want to add a watcher to an issue in a project with many collaborators, the pop-up window take between 10 sec and 20 sec (according to the number of collaborators) to appear.\r\nIt's very disturbing because user has no graphical indication about that.\r\n\r\nregards", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "165"}], "created_on": "2021-04-30T15:42:00Z", "updated_on": "2021-05-04T06:56:24Z"}, {"id": 35189, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 343718, "name": "Yoann AMICHAUD"}, "category": {"id": 9, "name": "Email notifications"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "New email notification option - events of my bookmarked projects", "description": "For now, if you want to be informed about all events of a huge projects portfolio, I have to update the list behind \"For any events of the selected projects only...\" quite often. \r\nIt would be really great if we can receive all notifications of the bookmarked projects adding a new option in the notification option list : \"For any events of my bookmarked projects only...\"\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-30T09:11:54Z", "updated_on": "2021-06-17T04:59:28Z"}, {"id": 35178, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "subject": "Make adding project settings tabs easier", "description": "Currently it is quite cumbersome to add a tab to the projects settings. It is necessary to patch the @ProjectsHelper@ and override the @project_settings_tabs@, which can be dangerous if the behaviour of the checks in the method change and patching helpers can lead to problems due to load orders.\r\n\r\nI would suggest to at least extract the list of tags from the method to a constant like for the @CustomFieldsHelper::CUSTOM_FIELDS_TABS@ list. This would have the added benefit that it would not be necessary to duplicate any logic from the @project_settings_tabs@ to a plugin if needed.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-28T15:19:20Z", "updated_on": "2021-04-28T15:22:09Z"}, {"id": 35176, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 461592, "name": "Barty Kacz"}, "category": {"id": 19, "name": "Attachments"}, "subject": "Multiple files for issues custom filed", "description": "I can create multiple file custom fields and add it to issue tracker but for each of this field I can add only one attachment.\r\nFor the generic Files field I can add multiple files.\r\nIs it something that I can change in admin panel?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-28T08:13:22Z", "updated_on": "2021-04-28T08:13:22Z"}, {"id": 35168, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 427018, "name": "David L"}, "category": {"id": 50, "name": "Activity view"}, "subject": "Activity tab not showing recent data", "description": "Even though I committed a change, it does not show up in Activity.\r\n\r\nIssues, Changesets and News were enabled in the Activity view filters.\r\n\r\nI have noticed this problem with regular issues in the past. I linked Redmine to revisions and now see it with that.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-04-27T06:02:20Z", "updated_on": "2021-04-27T06:02:20Z"}, {"id": 35153, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 31332, "name": "Kota Shiratsuka"}, "category": {"id": 10, "name": "UI"}, "subject": "Add a touch icon", "description": "The image was edited using [[Logo]]", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-04-25T10:56:26Z", "updated_on": "2021-04-27T11:08:56Z"}, {"id": 35141, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 517598, "name": "Yuriy Millen"}, "category": {"id": 23, "name": "Issues permissions"}, "subject": "Irrelevant groups in \"Add watchers\" list", "description": "Redmine 4.2 introduced an ability to add groups to watchers list.\r\n\r\nThe logic prior was that in the \"Add watchers\" list appeared only users, who have access to a particular tracker. However, this logic is ignored for groups - it is possible to add any group regardless of a whether this group was access to the tracker or not.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-04-21T14:01:30Z", "updated_on": "2021-04-21T14:01:30Z"}, {"id": 35138, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 8, "name": "Reopened"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 517543, "name": "Jan Kokert"}, "category": {"id": 16, "name": "Search engine"}, "subject": "Allow Version custom fields to be searchable", "description": "Currently, the global search does not take the values of the custom fields into account.\r\nCan you please add this? Many thanks in advance!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-21T09:36:34Z", "updated_on": "2021-05-13T08:45:52Z", "closed_on": "2021-04-22T12:00:36Z"}, {"id": 35132, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 365663, "name": "Markus Boremski"}, "category": {"id": 14, "name": "Custom fields"}, "subject": "Custum field default value has no effect if field is inaccessible", "description": "Unfortunately with 4.1.2 we now have an issue regarding #33550.\r\nIf we set a default value and the reporting person is not able to edit the field, the default value has no effect.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "162"}], "created_on": "2021-04-20T05:45:10Z", "updated_on": "2021-05-03T20:22:34Z"}, {"id": 35104, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 12098, "name": "Martin Cizek"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Code blocks - consistent rendering and retaining user-supplied language name in rendered HTML", "description": "This patch:\r\n\r\n* Makes code block rendering consistent across formats, which is important for plugins, client-side scripts and styling.\r\n* Makes sure rendered language name is escaped.\r\n* Exposes user-supplied language name in an HTML attribute, so that client-side scripts and Redmine plugins can always access it.\r\n\r\nThe patch applies to the current Textile and Markdown formatters. The very same change to the planned CommonMark formatter will be attached to #32424.\r\n\r\nPlease see below for design decisions rationale.\r\n\r\nh3. Code block rendering\r\n\r\n**@<pre><code>@ vs. -just @<pre>@-**:\r\nTextile supports blocks without code (@<pre>...</pre>@), while code can be part of such blocks. Typically, there is just one and only code block per @<pre>@ block, but it's possible to have more than one code block in a @<pre>@ block. So in general, we cannot avoid the @code@ tag in the HTML rendered from Textile.\r\n\r\nWhile it is possible to render only the @pre@ tag for Markdown code blocks and rendering libraries do have option for that, we should use the @code@ tag too to be consistent. Fortunatelly, this is already the case and it is even what CommonMark spec suggests.\r\n\r\n-**No-code blocks in Markdown**-\r\nMarkdown does not have preformatted blocks except for code blocks. Code blocks are either idented or fenced, but both are meant to represent code (\"spec\":https://spec.commonmark.org/0.29/#indented-code-blocks).\r\nThe fenced code blocks can also carry an info string, which is used to determine the languge of the code.\r\n\r\n**Comparison of different renderers:**\r\n\r\n|_<. Formatter |_. No-code block \u2192 HTML |_. Code block w/o lang \u2192 HTML |_. Code block with supported lang \u2192 HTML |_. Code block with unsupported lang \u2192 HTML |\r\n|_<. Redmine Textile | @<pre>...</pre>@ | @<pre><code>...</code></pre>@ | @<pre><code class=\"ruby syntaxhl\">...</code></pre>@ | @<pre><code>...</code></pre>@ |\r\n|_<. CommonMark reference renderer | N/A | @<pre><code>...</code></pre>@ | @<pre><code class=\"language-ruby\">...</code></pre>@ | @<pre><code class=\"language-foo\">...</code></pre>@ |\r\n|_<. Redmine Markdown | N/A | @<pre>...</pre>@ | @<pre><code class=\"ruby syntaxhl\">...</code></pre>@ | @<pre>...</pre>@ |\r\n|_<. Redmine CommonMark #32424 | N/A | @<pre><code>...</code></pre>@ | @<pre><code class=\"ruby syntaxhl\">...</code></pre>@ | @<pre>...</pre>@ |\r\n\r\nIt's quite obvious that we should follow the Textile behavior to be consistent.\r\n\r\nh3. Original data language\r\n\r\nThe user-supplied language information is currently dropped if the particular language does not have any lexer for syntax highlighting. However, there are several use cases when this information is valuable:\r\n* Plugins like \"redmine_wysiwyg_editor\":https://redmine.org/plugins/redmine_wysiwyg_editor\r\n* Data format converters like \"redmine_reformat\":https://redmine.org/plugins/redmine_reformat\r\n* Client-side scripts that could render or decorate specific languages in their own way, e.g. \"mermaid\":https://mermaid-js.github.io/mermaid/#/\r\n\r\nFor the reasons above, the information has to be carried on the @code@ tag. I've examined a few projects and libraries related to the topic to find an appropriate name for such attribute. The conclusion is to use @<code data-language=\"foo\" ...>@.\r\n\r\n**Resulting code block rendering:**\r\n|_<. Formatter |_. No-code block \u2192 HTML |_. Code block w/o lang \u2192 HTML |_. Code block with supported lang \u2192 HTML |_. Code block with unsupported lang \u2192 HTML |\r\n|_<. All Redmine formatters | @<pre>...</pre>@ | @<pre><code>...</code></pre>@ |\r\n@<pre><code class=\"ruby syntaxhl\" data-language=\"ruby\">...</code></pre>@ | @<pre><code data-language=\"foo\">...</code></pre>@ |\r\n\r\nh3. Quality Assurance, Security & Compatibility\r\n\r\n* +QA+: Added new unit tests and updated the existing ones.\r\n* +Security+: Previously, Textile formatter did not escape language name and relied on validating it against syntax highlighter, while expecting language names to be safe. Language names are now always subject to escaping.\r\n* +Compatibility+:\r\n** The rendered HTML is now the same as the HTML from Textile.\r\n** The added @data-language@ attribute should be indeed ignored by unconcerned components.\r\n** I don't really expect that anybody to rely on getting @<pre>@ and not @<pre><code>@, especially when it is the current behavior of Textile. I've verified this on redmine_wysiwyg_editor as a rare example of a potentially concerned plugin.\r\n\r\nSo I'm convinced it is safe to include this in any minor release.", "done_ratio": 0, "created_on": "2021-04-15T19:29:21Z", "updated_on": "2021-06-03T12:46:34Z"}, {"id": 35103, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 94920, "name": "James H"}, "category": {"id": 8, "name": "Administration"}, "subject": "Administration Groups & Users Lags with Many Projects", "description": "This applies to the Groups page, Users page, and possibly others.\r\n\r\nWhen you navigate into the Groups page, it tries to load a few tabs of information. \r\nI have many projects and some users or groups are members of many of them and it takes a very long time to load these pages to even do simple changes. Sometimes unusable.\r\nI suspect the problem is due to the other tabs trying to load all of the related information e.g. all of the projects they are members of.\r\n\r\nCan the projects page be paginated with a sort that makes sense? \r\nIdeally something like the issues viewing list would be most powerful, but most time consuming. \r\nA simple searchable/paginated list of some kind would be great, or just not loading the projects until you go into that tab or similar.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-15T18:09:58Z", "updated_on": "2021-04-15T18:37:37Z"}, {"id": 35102, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 98872, "name": "Pan Tau"}, "subject": "Issue Tracking Details are showning issue statuses even if they are not used within the project", "description": "The Issue Tracking Details show all issue statuses of all trackers used in the project, \r\neven if no project-role uses them in their workflow.\r\n\r\nThat becomes an problem if have many projects using for example the tracker \"Defect\"\r\nand some of the projects have additional issue statuses.\r\nBecause you get an really long table und header and most of the statuses are not used within the project.\r\n\r\nIt would be helpful to filter the shown statuses by project-trackers and their project-role-workflows.\r\n\r\n!many_not_used_issue_statuses.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-04-15T09:02:37Z", "updated_on": "2021-04-15T09:02:37Z"}, {"id": 35090, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "category": {"id": 10, "name": "UI"}, "subject": "Permission check mismatches button semantics", "description": "In source:/tags/4.2.0/app/views/issues/index.html.erb#L16 the link goes to the @issues@ tab of the project settings. The button is only shown if the user has the @manage_categories@ permission but the permission required for this tab is @edit_project@ source:/tags/4.2.0/app/helpers/projects_helper.rb#L28\r\n\r\nNote that this is only a UI issue, the button might be shown to users that cannot see the tab that it links to or the button might not be shown to users that would be able to see the tab that it links too, but upon following the link the correct permission is checked. There also is no information disclosure associated with this issue.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-04-14T10:23:28Z", "updated_on": "2021-04-14T10:26:20Z"}, {"id": 35081, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 44, "name": "Rails support"}, "subject": "Update config/environments/*.rb for Rails 6.1", "description": "The attached patch updates Rails environment files (development.rb, production.rb, and test.rb in config/environments directory) for Rails 6.1.\r\n\r\nBy updating the files, several useful new features in Rails 6.1 will be available (e.g. request_id in production.log, verbose_query_logs in development.log). Also, by looking at the commented out settings, the user can easily know what settings are available (e.g. config.force_ssl in config/environments/production.rb).", "done_ratio": 0, "created_on": "2021-04-13T02:21:30Z", "updated_on": "2021-07-04T16:42:44Z"}, {"id": 35077, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 516036, "name": "Dcn Spyridon Papa"}, "category": {"id": 14, "name": "Custom fields"}, "subject": "Custom Strings as Unique Identifiers for issues", "description": "Hello everybody,\r\nI am completely new to Redmine so please forgive me if i am asking nonsensical, obsolete or stupid questions. I need your help and would be very grateful to anyone who can provide us with assistance!\r\nWe are running a large project, which involves the digitisation of cultural heritage. We have an interdisciplinary mix of teams from various institutions, with multiple levels and types of expertise in different areas. Therefore this is not solely a software development project but also involves the management of digitisation procedures, methodology development, webpage development, UI development, reporting, publications etc...\r\nWe have chosen Redmine after a lot of research following recommendations from our partners and now we have set up Redmine on a server and will commence enrichment. We have an existing system for numbering and codifying our tasks and issues. However, looking at Redmine i can see it automatically assigns numbers to issues. Is it feasible to assign our own numbering and codification scheme on existing tasks, features and projects? It will be confusing for us to be seeing a task numbered #34 when we already have the code 3.1.2 for it. We have dozens of tasks and subtasks and relative issues are anticipated to amount to thousands. Any suggestions how we might be able to have the header of the particular issue to be presented as \"3.1.2 ISSUE TITLE\" rather than \"#34 ISSUE TITLE\"?\r\nI will be very grateful for any help.\r\nAll the best to all,\r\nDS", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-12T10:38:18Z", "updated_on": "2021-04-12T10:38:18Z"}, {"id": 35073, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 40856, "name": "Jens Kr\u00e4mer"}, "category": {"id": 21, "name": "Database"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "escape values in LIKE statements to prevent injection of placeholders (_ or %)", "description": "While not technically a security risk, LIKE queries with lots of placeholders can result in high database load, very slow query execution and therefore are a possible vector for denial of service attacks. Further, escaping the wildcard characters in actual query values now allows to actually search for values containing these characters.\r\n\r\nThe attached patches, which have been extracted from \"Planio\":https://plan.io/redmine-hosting are:\r\n\r\n* The first patch removes '%' signs from query strings used in the search test case. These did not matter until now since they just resulted in queries like @field LIKE '%%value%%'@, but now would be looking for a value with literal percent signs. Tests pass before and after that change.\r\n* Patches 2-4 add @sanitize_sql_like@ calls to the various places where we currrently generate sql LIKE statements. Corresponding tests are included.\r\n* The last patch is just a cosmetic change that replaces a @.send@ with a direct call since the called method is now public.\r\n", "done_ratio": 0, "created_on": "2021-04-12T06:50:57Z", "updated_on": "2021-07-29T04:59:56Z"}, {"id": 35066, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 36999, "name": "J\u00e9r\u00f4me BATAILLE"}, "category": {"id": 13, "name": "Time tracking"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Create time entry and add another on project, initialize project_id", "description": "While using *create and add another* button with \"a plugin I have developed\":https://www.redmine.org/plugins/redmine_queries_for_time_report I have an issue with an empty drop-down in a custom field :\r\n# first step :\r\n!Project_Enumerations_create_and_add_another.png!\r\n# second step :\r\n!Project_Enumerations_create_and_add_another2.png!\r\n\r\nThe issue is caused by a missing intialisation of the TimeEntry.\r\nHere is a patch to fix this.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-09T22:09:01Z", "updated_on": "2021-05-25T11:18:42Z"}, {"id": 35062, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "subject": "Back URLs with \r\n# Title\r\n\r\n## Heading 2\r\n\r\n- item\r\none\r\n-\r\nnot a heading\r\n\r\n## Heading 2\r\nNulla nunc nisi, egestas in ornare vel, posuere ac libero.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-05T14:00:34Z", "updated_on": "2021-04-05T14:00:34Z"}, {"id": 35035, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 12098, "name": "Martin Cizek"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Refactor text formatting to HTML::Pipeline", "description": "After merging the CommonMark patch #32424, Redmine will contain an @HTML::Pipeline@ implementation limited to this new format. It makes then perfect sense to extend the new concept to text formatting generally.\r\n\r\nThe current implementation looks like:\r\n!Text_Formatting-Redmine-4.2.png!\r\n\r\nWhile the new Markdown (CommonMark) implementation is designed like:\r\n!CommonMark-HTML_Pipeline.png!\r\n\r\nMigrating text rendering to @HTML::Pipeline@ should provide several benefits:\r\n* Better separation of concerns.\r\n* Cleaner, safer and DRY code.\r\n* Individual formatters can be freed from excessive restrictions that were introduced as XSS prevention. Especially the absolute prohibition of HTML tags can be pain in specific cases.\r\n* More consistent behavior among formatters (e.g. HTML is currently escaped in Textile, but dropped in Markdown),\r\n* **Controlled level of security** without the need to rely on individual formatter implementations that often use poorly maintained libraries.\r\n* More flexibility for Redmine developers and Redmine plugin developers. Adding some hooks would be nice and would allow e.g. implementing @mermaid@ charts as a custom syntax highlighter - in the same way as GitLab.\r\n\r\nSome inspiration \"can be found in GitLab sources\":https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/banzai/pipeline, but our pipelines would probably won't need to go that complex.\r\n\r\nIf there were no other timing considerations, it would make sense to implement this together with Redcarpet removal.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-05T13:28:42Z", "updated_on": "2021-04-12T02:31:44Z"}, {"id": 35028, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 21060, "name": "Ivan Cenov"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 45, "name": "Gems support"}, "subject": "Deprecation message when executing 'bundle install'", "description": "Here is a part of the console output when upgrading Redmine to version 4.2.0:\r\n\r\nE:\\data\\redmine>bundle install --without test development\r\n[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions.\r\nInstead please use `bundle config set without 'test development'`, and stop using this flag\r\n[DEPRECATED] Your Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems.\r\nTo resolve this warning, use a block to indicate which gems should come from the secondary source.\r\nTo upgrade this warning to an error, run `bundle config set disable_multisource true`.\r\nYour Gemfile lists the gem rake (>= 0) more than once.\r\nYou should probably keep only one of them.\r\nRemove any duplicate entries and specify the gem only once.\r\nWhile it's not a problem now, it could cause errors if you change the version of one of them later.\r\n \r\n\r\nEspecially this part:\r\n\r\n[DEPRECATED] Your Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems.\r\nTo resolve this warning, use a block to indicate which gems should come from the secondary source.\r\n Is it something dangerous? I am not a ruby on rails programmer and cannot tell...", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "152"}], "created_on": "2021-04-04T09:52:45Z", "updated_on": "2021-04-04T18:44:49Z"}, {"id": 35027, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 34, "name": "Gantt"}, "fixed_version": {"id": 33, "name": "Candidate for next minor release"}, "subject": "Gantt PNG export ignores imagemagick_convert_command", "description": "Gantt PNG export uses ImageMagick's convert command, but it ignores imagemagick_convert_command in configration.yml.\r\n\r\nSteps to reproduce:\r\n\r\n1. Set incorrect command name (e.g. @/usr/bin/_convert@) to imagemagick_convert_command in configration.yml\r\n2. Restart Redmine\r\n3. Export gantt to PNG. It should not work because imagemagick_convert_command is wrong, but it works fine.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2021-04-04T06:54:48Z", "updated_on": "2021-06-19T08:47:39Z"}, {"id": 35014, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 21, "name": "Database"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Review and update supported database engines and versions ", "description": "Supported database engines and versions were not been updated for a while and we should do it in Redmine version:\"5.0.0\". ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-03T06:37:11Z", "updated_on": "2021-04-04T08:29:53Z"}, {"id": 35001, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 7, "name": "Accounts / authentication"}, "subject": "Disable API authentication with username and password when two-factor authentication is enabled for the user", "description": "In Redmine 4.2, two-factor authentication has been introduced.\r\n\r\nWhen two-factor authentication is enabled, it becomes difficult for an attacker to log in to Redmine even if he knows the username and password.\r\n\r\nHowever, API authentication is not covered by two-factor authentication. Currently, there are three methods of API authentication:\r\n\r\n1. send the user's API key via X-Redmine-API-Key header\r\n2. basic authentication with the user's API key ( username is the API key and password is a random string)\r\n3. basic authentication with user name and password\r\n\r\nIf you have two-factor authentication enabled, I think the third method will be problematic. This is because even though the web UI can prevent an attacker from logging in with an illegally obtained username and password, they can still use that username and password to access the data via the API.\r\n\r\nTo address this risk, I suggest disabling basic authentication with username and password for users who have two-factor authentication enabled.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-04-02T03:18:53Z", "updated_on": "2021-04-02T03:26:27Z"}, {"id": 34995, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 514581, "name": "rafaelteb rafaelteb"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Running redmine in docker getting ssl error, any ideas what might be the issue?", "description": "Im having an issue with SSL. Im getting pretty crazy currently. Got the feeling that I miss something really simple :D\r\n\r\nWould be very thankful for any help.\r\nMaybe I should add rufus to a Dockerfile like its done here: https://github.com/docker-library/redmine/issues/64?\r\n\r\nCurrently wanted to setup with cron. But Im constantly getting this error:\r\n\r\n**`rake aborted!\r\nOpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (unable to get local issuer certificate)`**\r\n\r\nMentioned error occurers when I use this command:\r\n`bundle exec rake -f /usr/src/redmine/Rakefile redmine:email:receive_imap RAILS_ENV=\"production\" host=xxx port=993 username=xxx password=xxx ssl=true project=testproject folder=INBOX move_on_success=processed move_on_failure=failed no_permission_check=1 unknown_user=accept`\r\n\r\nFunny thing: When I dirtily switch off ssl-checking by ruby **with some sort of hack, all is working**. I added a file here in /usr/src/redmine/config/initializers/bypass_ssl_verification_for_open_uri.rb with this:\r\n\r\n```\r\nrequire 'openssl'\r\nOpenSSL::SSL::VERIFY_PEER = OpenSSL::SSL::VERIFY_NONE\r\n```\r\n\r\nAlso, I did setup ssl. I use redmine passenger with cert files in /usr/local/ca-certifications.\r\nMy Dockerfile looks like this:\r\n\r\n````FROM redmine:4.1.0-passenger\r\n\r\n#install packages\r\nRUN apt update && apt -y install build-essential ca-certificates ruby-xapian\r\n\r\n#import certificates for https\r\nCOPY certificates/redmine.pem /usr/local/share/ca-certificates/\r\nCOPY certificates/redmine.key /usr/local/share/ca-certificates/\r\n#not sure why permissions need to be relaxed...\r\nRUN chmod -R 777 /usr/local/share/ca-certificates/\r\n\r\n\r\nCMD [\"passenger\", \"start\", \"--ssl\", \"--ssl-certificate\", \"/usr/local/share/ca-certificates/redmine.pem\", \"--ssl-certificate-key\", \"/usr/local/share/ca-certificates/redmine.key\", \"--ssl-port\", \"443\"]\r\n````\r\n\r\nAnd my docker-compose.yml looks like this:\r\n````\r\nversion: '3.1'\r\n\r\nservices:\r\n web:\r\n build: .\r\n restart: always\r\n ports:\r\n - 8080:3000\r\n - 443:3443\r\n environment:\r\n REDMINE_DB_MYSQL: db\r\n REDMINE_DB_PASSWORD: example\r\n volumes:\r\n - /data/redmine/redmine-files:/usr/src/redmine/files\r\n - /data/redmine/redmine-plugins:/usr/src/redmine/plugins\r\n - /data/redmine/redmine-themes:/usr/src/redmine/public/themes\r\n db:\r\n image: mysql:5.7\r\n restart: always\r\n environment:\r\n MYSQL_ROOT_PASSWORD: example\r\n MYSQL_DATABASE: redmine\r\n volumes:\r\n - /data/redmine/mysql:/var/lib/mysql\r\n ````\r\n\r\nAny ideas? Very thankfull for tips and help ;)\r\nBest", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "159"}], "created_on": "2021-03-31T13:18:57Z", "updated_on": "2021-03-31T13:18:57Z"}, {"id": 34992, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 33, "name": "Ruby support"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Ruby 3.0 support", "description": "Ruby 3.0.0 has been released on 25 Dec 2020.\r\nhttps://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released/\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Fixed"}], "created_on": "2021-03-31T06:40:02Z", "updated_on": "2021-04-03T09:12:02Z"}, {"id": 34988, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 308290, "name": "Bernhard Rohloff"}, "category": {"id": 24, "name": "Documentation"}, "subject": "Add new notification settings for priority based notification to the user guide", "description": "", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-30T12:04:05Z", "updated_on": "2021-03-30T14:18:21Z"}, {"id": 34987, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 123153, "name": "Pavel Rosick\u00fd"}, "category": {"id": 44, "name": "Rails support"}, "subject": "Rails 6.1 destroy async", "description": "Rails 6.1 has a new feature that allows associations to be destroyed asynchronously.\r\n\r\nhttps://bigbinary.com/blog/rails-6-1-allows-associations-to-support-destroy_async-option-with-dependent-key", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-30T11:06:00Z", "updated_on": "2021-03-30T11:06:00Z"}, {"id": 34981, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 43, "name": "Project settings"}, "subject": "Allow to change a project identifier", "description": "Currently, it is not possible to change the identifier of a project. However, you may want to change the project identifier if, for example, you come up with a better identifier later, or if the purpose of the project changes.\r\n\r\nThe problem with changing the project identifier is that the identifier is used as part of URLs, so links from outside Redmine will be invalid.\r\n\r\nHowever, if a person who manages the project (means a member who has \"Edit project\" permission) understands and accepts the disadvantages of changing a project identifier, I think there is no problem to allow changing it. In fact, I am sometimes asked by customers how to change a project identifier.\r\n\r\nMy suggestions:\r\n* Allow to change a project identifier in /projects//settings page\r\n* For Display a warning below the Identifier field on the form (eg: \"Changing the identifier will change the URL of this project and may break links using the URL\")", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-30T02:42:09Z", "updated_on": "2021-07-27T09:55:17Z"}, {"id": 34978, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Drop support for IE 11", "description": "Beginning August 17, 2021, the remaining Microsoft 365 apps and services will no longer support IE 11. Microsoft Teams already ended support. More details \"here\":https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666#:~:text=Today%2C%20we're%20announcing%20that,no%20longer%20support%20IE%2011.\r\n\r\nIt's time to drop support for IE11 and supports only Microsoft Edge (Chromium version)", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-28T17:48:43Z", "updated_on": "2021-04-04T01:53:11Z"}, {"id": 34974, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Change the default value for \"Preferred part of multipart (HTML) emails\" from \"Text\" to \"HTML\"", "description": "The attached patch changes the default value for \"Preferred part of multipart (HTML) emails\" to \"HTML\".\r\n\r\nThe option to decide whether the text part or the HTML part should be used first when receiving an HTML email was introduced in Redmine 4.1.0 (#30838). At that time, the option to use the HTML part was treated as an experimental feature, and the default was to use the text part as in previous versions.\r\n\r\nOur company has been using the HTML-first option for almost two years, and we have had no problems.\r\n\r\nI think it is time to change the default value for new installations to HTML because the feature is mature enough and more and more emails are sent in HTML format now.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-28T06:50:58Z", "updated_on": "2021-07-25T05:40:26Z"}, {"id": 34965, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 514068, "name": "Joel Sager"}, "category": {"id": 10, "name": "UI"}, "subject": "UnWatch ticket does not work thows 403 Forbidden when clicked", "description": "When trying to UnWatch a ticket that have watched. It does not work and I get a 403 Forbidden\r\n\r\n\r\nFirebug log: \r\n\r\nXHRDELETEhttps://my.domain.com/watchers/watch?object_id=21079&object_type=issue\r\n[HTTP/1.1 403 Forbidden 227ms]\r\n\r\n\t\r\nDELETE\r\n\thttps://my.domain.com/watchers/watch?object_id=21079&object_type=issue\r\nStatus403\r\nForbidden\r\nVersionHTTP/1.1\r\nTransferred627 B (216 B size)\r\n\r\n\r\nApache Log\r\n\r\nActionController::RoutingError (No route matches [GET] \"/watchers/watch\"):\r\n\r\n\r\n\r\n\r\nEnvironment:\r\n Redmine version 4.1.2.stable\r\n Ruby version 2.6.5-p114 (2019-10-01) [x86_64-linux]\r\n Rails version 5.2.4.5\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\nSCM:\r\n Filesystem \r\nRedmine plugins:\r\n easy_gantt 1.12\r\n easy_gantt_pro 1.10\r\n redmine_agile 1.5.3\r\n redmine_checklists 3.1.16\r\n redmine_contacts 4.3.0\r\n redmine_contacts_helpdesk 4.1.8\r\n redmine_contacts_invoices 4.2.3\r\n redmine_crm_mailchimp 1.0.4\r\n redmine_favorite_projects 2.1.0\r\n redmine_finance 2.1.7\r\n redmine_people 1.5.1\r\n redmine_products 2.1.2\r\n redmine_questions 1.0.2\r\n redmine_reporter 1.0.3\r\n redmine_resources 1.0.2\r\n redmine_work_time 0.4.0\r\n redmine_zenedit 1.0.3\r\n sidebar_hide 0.0.8", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "162"}], "created_on": "2021-03-26T18:06:13Z", "updated_on": "2021-03-26T18:06:13Z"}, {"id": 34957, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 312060, "name": "Alejandro Grijalba"}, "category": {"id": 53, "name": "Performance"}, "subject": "Search issues by custom fields is slow", "description": "We have more than 30k issues, some of them use custom fields.\r\nWe found that searching by custom fields is slow, takes about 20 seconds the search.\r\nIt is slow both searching using API, or searching using GUI.\r\nThe custom field in this case is of type integer.\r\n\r\nThe problem seems to be related to the SQL query that is being done during search.\r\n\r\nThe query looks like this:\r\n\r\nSelect * from issues, ...\r\n AND issues.id IN (SELECT issues.id FROM issues LEFT OUTER JOIN custom_values\r\n ...\r\n )\r\n \r\n\r\nThe code for the subquery is at models/issue_custom_field.rb\r\n\r\nThere seem to be performance problems with \"IN\" subqueries in MySQL (https://stackoverflow.com/a/9627668/366209).\r\nIt looks like the subquery cannot be cached in MySQL, only the whole query can. (And that doesn't even help, because SQL cache is flushed when a ticket is created anyway)\r\nIronically the suquery alone runs in less than a second, and the external query alone is fast too.\r\n\r\nSo maybe the suquery could be reworked to use JOIN instead of IN, that's what they suggest in Stack Overflow. That worked in my tests, when I ran modified SQL queries manually.\r\nI wish I could change the code, but it seems a little complicated for me right now.\r\n\r\nOur Redmine was installed from a Bitnami's virtual machine template.\r\n\r\nEnvironment:\r\n Redmine version 3.3.2.stable\r\n Ruby version 2.1.10-p492 (2016-04-01) [x86_64-linux]\r\n Rails version 4.2.7.1\r\n Environment production\r\n Database adapter Mysql2\r\n\r\nMySQL Version: 5.6.35\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-03-25T17:58:08Z", "updated_on": "2021-03-28T06:12:51Z"}, {"id": 34924, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 44989, "name": "Dhanasingh Krishnapandian"}, "category": {"id": 12, "name": "Translations"}, "subject": "Tamil India language files", "description": "Tamil India language files", "done_ratio": 0, "created_on": "2021-03-18T10:46:12Z", "updated_on": "2021-03-18T10:46:12Z"}, {"id": 34922, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "category": {"id": 10, "name": "UI"}, "subject": "Reload whole time entries form on project change", "description": "Currently parts of the time entries form is reloaded when changing the project/project id, see source:/trunk/app/views/timelog/_form.html.erb@20821#L41\r\n\r\nThis however does not change and restore custom fields for example for time entries.\r\n\r\nWe think this should be changed to reload the whole time entries form similar to what is done for issue forms, see source:/trunk/app/views/issues/_form.html.erb@20821#L15\r\n\r\nDo you think this would be a good addition to Redmine or should this be done another way?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-03-18T09:42:50Z", "updated_on": "2021-03-18T09:42:50Z"}, {"id": 34917, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 259873, "name": "Mizuki ISHIKAWA"}, "category": {"id": 10, "name": "UI"}, "subject": "Change the label of Remove user action from \"Delete\" to \"Remove\"", "description": "The link that deletes the member record associated with the group appears to delete the user data itself due to the influence of the current label and icon.\r\nHow about adding a button_remove label and using it instead of button_delete?\r\nIn that case, I would like to change the icon as well.\r\n\r\n!{width: 50%; border: 1px solid #ccc}screenshot_2021-03-18_14.15.25.png!\r\n\r\nWhen deleting a watcher record, I think it's a \"delete user\" from the user's point of view. I want to change \"Delete\" to \"Remove\" as well.\r\n!{width: 30%; border: 1px solid #ccc}screenshot_2021-03-18_14.19.31.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-18T05:49:25Z", "updated_on": "2021-03-18T05:49:25Z"}, {"id": 34896, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 259873, "name": "Mizuki ISHIKAWA"}, "category": {"id": 8, "name": "Administration"}, "subject": "PDF thumbnails are not displayed even though \"ImageMagick PDF support available (optional)\" is checked", "description": "This is a issue related to #34397.\r\nDue to recent changes in ImageMagick, PDF cannot be converted to PNG without rewriting the policy.xml file.\r\nhttps://stackoverflow.com/questions/52861946/imagemagick-not-authorized-to-convert-pdf-to-an-image\r\n\r\nI think you should check if ImageMagick has permission to convert PDF to PNG and then check \"ImageMagick PDF support available (optional)\" in Infomation.\r\n!information.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-03-16T07:21:46Z", "updated_on": "2021-05-05T23:42:47Z"}, {"id": 34870, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 141795, "name": "Adriano Baptistella"}, "category": {"id": 59, "name": "Filters"}, "subject": "Differences in searches for accented words", "description": "Hi, team! \r\nI'm having problem in filter words with accents, see the print down. Have differences \"conv\u00eanio\" and \"convenio\" I would what the filter not had differences accents.\r\nBest regards!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-03-09T20:11:23Z", "updated_on": "2021-03-09T20:11:23Z"}, {"id": 34863, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 26, "name": "Text formatting"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Change default text formatter for new installations from textile to markdown", "description": "Nowadays, markdown is much more used and known compared with textile. Also, in Redmine, Markdown has better support.\r\n\r\nMy proposal is to change the default setting from textile to markdown.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-09T07:32:49Z", "updated_on": "2021-03-28T06:22:24Z"}, {"id": 34862, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 362529, "name": "Yuichi HARADA"}, "category": {"id": 19, "name": "Attachments"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Bulk delete forum attachments", "description": "I want to bulk delete attachments on the forum edit page, like a #16410.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-09T05:13:12Z", "updated_on": "2021-03-28T06:22:43Z"}, {"id": 34861, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 362529, "name": "Yuichi HARADA"}, "category": {"id": 19, "name": "Attachments"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Bulk delete news attachments", "description": "I want to bulk delete attachments on the news edit page, like a #16410.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-09T05:12:27Z", "updated_on": "2021-03-28T06:22:52Z"}, {"id": 34860, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 511216, "name": "Bj\u00f6rn Dieding"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Extended watcher and notification features", "description": "Hi,\r\n\r\nI would like to have more control on how people your me as a watcher and if I shall get notifications or now.\r\n\r\nSo new watcher User Stories can include:\r\n\r\nAs a Redmine User I want to control wheather I can be used as a watcher or not.\r\nAs a Redmine User I want to stop all mail from watches that had been added by others but not me.\r\nAs a Redmine User I want to deny certain users to use me as a watcher.\r\nAs a Redmine Admin I want to warcher permissions so that I can define a group of watchers a group can select.\r\n\r\nI beleive any of those can help my current spam problem.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-08T22:19:40Z", "updated_on": "2021-03-08T22:19:40Z"}, {"id": 34858, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 153583, "name": "Martin von Wittich"}, "category": {"id": 2, "name": "Issues"}, "subject": "Project list when creating/editing issue should be searchable", "description": "We currently have almost 400 projects in our Redmine instance. This makes it very painful to move an issue from one project to the other, because the project list when editing an issue is a simple `` without any searching/filtering capability. The fact that most of our projects are actually subprojects of a few projects like \"Team A\" and \"Team B\" makes it even worse, because you can't type the first letter of the project to jump to it in the list - this works only for first-level projects, because all other projects are indented in the list. If you don't know to which team the project you're looking for belongs to, you're in for a lot of scrolling through the list.\r\n\r\nThe \"jump to project\" box in the upper right corner features a search. Could the same implementation be used for the project list when creating/editing an issue?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-08T16:18:09Z", "updated_on": "2021-03-08T16:18:09Z"}, {"id": 34845, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 118633, "name": "Marco Shima"}, "category": {"id": 10, "name": "UI"}, "subject": "Configuration of display of subtickets", "description": "We use grouping of tickets a lot for semantic organization. That means that we have kind of group tickets that contain subtickets (e.g. a bug is a subticket of the feature group ticket it affects). The list of subtickets displayed may be quite large, scrolling is needed. Because of that we would like to get the possibility to configure the columns of the subticket listing.\r\n\r\nEasy:\r\n- Same columns as configured as default for ticket searches\r\n\r\nLuxury:\r\n- Configuration per project or even per ticket.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-05T08:22:43Z", "updated_on": "2021-03-05T12:45:28Z"}, {"id": 34841, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 442476, "name": "Benoit Petit"}, "subject": "URL encoding to pass arguments is broken with Edge and IE", "description": "Hello,\r\nI've got a tracker and I'm providing to my user an URL to validate or not some boolean fields defined in custom fields.\r\nE.g. : http://myredmine/projects/tracker/issues/new?issue%5Bcustom_field_values%5D%5B4%5D=1\r\n\r\nyou should read : http://myredmine/projects/tracker/issues/new?issue[custom_field_values][4]=1\r\n\r\nAs you can see, square brackets are coded. Chrome and firefox are reading them without issue, Edge and IE are not reading them and just open the page without changing the fields.\r\n\r\nAny idea how to solve that ? \r\nRunning 4.0.3.stable\r\n\r\nthanks a lot\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Cant reproduce"}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-03-04T17:21:28Z", "updated_on": "2021-04-09T09:27:21Z"}, {"id": 34834, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 10, "name": "UI"}, "subject": "Line breaks in the description field of custom fields are ignored", "description": "The text in the description field of a custom field is displayed as a tooltip. In Redmine 4.1, all line breaks in the descriptions are ignored when showing a tooltip.\r\n\r\n!{width: 543px; border: 1px solid #ccc;}.cf-description.png!\r\n\r\n*Redmine 4.1:*\r\n!{width: 390px; border: 1px solid #ccc;}.tooltip-4_1.png!\r\n\r\n*Redmine 4.0:*\r\n!{width: 390px; border: 1px solid #ccc;}.tooltip-4_0.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2021-03-04T07:01:15Z", "updated_on": "2021-03-21T06:05:12Z"}, {"id": 34831, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 342253, "name": "Albrecht Dre\u00df"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Unnecessary encoded CR characters in mails", "description": "I noticed that Redmine adds unnecessary CR (0x0d) characters to mail texts which may confuse some MUA's, e.g. (note the qp encoded \u201c@=0D@\u201d, not to be confused with the regular CRLF line endings required by RFC 5322, indicated by \u201c@\\r@\u201d):\r\n\r\n\r\n----==_mimepart_603f956964fe8_7c03fdcbf1d3464612fe\\r\r\nContent-Type: text/plain;\\r\r\n charset=UTF-8\\r\r\nContent-Transfer-Encoding: quoted-printable\\r\r\n\\r\r\nTicket #3814 wurde erstellt von Albrecht Dre=C3=9F.=0D\\r\r\n=0D\\r\r\n----------------------------------------=0D\\r\r\nFeature #3814: Diskussion=0D\\r\r\nhttps://web.my.org/redmine/issues/3814=0D\\r\r\n=0D\\r\r\n* Autor: Albrecht Dre=C3=9F=0D\\r \r\n\r\nIs it possible to get rid of them? Where should I look in the sources? I run Redmine 4.0.7 on a Debian Buster system, installed from Debian Backports.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "159"}], "created_on": "2021-03-03T15:44:24Z", "updated_on": "2021-03-03T17:13:46Z"}, {"id": 34830, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 145727, "name": "Takenori TAKAKI"}, "category": {"id": 2, "name": "Issues"}, "subject": "Issues burn down chart in the version detail", "description": "I propose a feature to visualize the changes of Open / Close issues in the version details using 'Burndown chart'.\r\nAfter applying the patch, a chart like the one in the screenshot below will be added to the version details.\r\n\r\n!{width:800px}issues-burndown-in-version-detail.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-03T07:42:12Z", "updated_on": "2021-03-03T07:42:12Z"}, {"id": 34829, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 510300, "name": "Iskatel -"}, "category": {"id": 10, "name": "UI"}, "subject": "How can I change default homepage in Redmine v4.1.1 ?", "description": "How can I change default homepage in Redmine v4.1.1 ?\r\nI need to change it to page \"Issues\" of project \"notes\".", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-03-02T19:00:54Z", "updated_on": "2021-03-02T19:00:54Z"}, {"id": 34824, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 308290, "name": "Bernhard Rohloff"}, "category": {"id": 24, "name": "Documentation"}, "subject": "Outdated description of notification settings in user settings", "description": "The description of the notification settings in [[RedmineAccounts]] is fairly outdated and does not describe the actual functionality anymore.\r\nIt should be replaced by a more recent description.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-03-02T05:11:24Z", "updated_on": "2021-03-02T10:50:29Z"}, {"id": 34820, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 50, "name": "Activity view"}, "subject": "Associated Revisions not shown up on Activity Page", "description": "If I create a project and connect it to a Git repository and this project has one or more subprojects and I reference an issue of the subproject in the commit, then the \"Associated revisions\" are displayed under the issue, but not on the activity page of the Subproject displayed. \r\n\r\nSomeone know how to fix that ?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-03-01T12:38:05Z", "updated_on": "2021-03-01T12:38:05Z"}, {"id": 34810, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 8, "name": "Reopened"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 34607, "name": "Florent H."}, "category": {"id": 1, "name": "Wiki"}, "subject": "SQL Error with UTF8 character greater or equals", "description": "I am currently getting a fatal error using this character (greater or equals) editing a wiki page\r\n\r\n\u2265\r\n\r\nhttps://fr.wiktionary.org/wiki/%E2%89%A5\r\n\r\nError\r\n\r\napp/models/wiki_page.rb:249:in `block in save_with_content'\r\napp/models/wiki_page.rb:245:in `save_with_content'\r\napp/controllers/wiki_controller.rb:180:in `update'\r\nlib/redmine/sudo_mode.rb:65:in `sudo_mode'\r\nStarted PUT \"/projects/site-web/wiki/Breakpoints\" for 92.167.55.166 at 2021-02-26 17:46:08 +0000\r\nProcessing by WikiController#update as HTML\r\n Parameters: {\"utf8\"=>\"<9C><93>\", \"authenticity_token\"=>\"XXX\", \"content\"=>{\"version\"=>\"1\", \"text\"=>\"h1. Breakpoints\\r\\n\\r\\nNous utilisons bootstrap 5 avec ses breakpoints officiels\\r\\n\\r\\nhttps://getbootstrap.com/docs/5.0/layout/breakpoints/\\r\\n\\r\\n|_.Breakpoint|_.Class infix|_.Dimensions|_.Appareil|\\r\\n|X-Small|None|<576px|Mobile|\\r\\n|Small|sm|<89>576px|Mobile|\\r\\n|Medium|md|<89>768px|Mobile|\\r\\n|Large|lg|<89>992px|Ordinateur|\\r\\n|Extra large|xl|<89>1200px|Ordinateur|\\r\\n|Extra extra large|xxl|<89>1400px|Ordinateur|\\r\\n\", \"comments\"=>\"\"}, \"wiki_page\"=>{\"parent_id\"=>\"25\"}, \"commit\"=>\"Sauvegarder\", \"project_id\"=>\"site-web\", \"id\"=>\"Breakpoints\"}\r\n Current user: Me (id=1)\r\nCompleted 500 Internal Server Error in 257ms (ActiveRecord: 249.6ms)\r\n\r\nActiveRecord::StatementInvalid (Mysql2::Error: Incorrect string value: '\\xE2\\x89\\xA5576...' for column `redmine`.`wiki_contents`.`text` at row 1: INSERT INTO `wiki_contents` (`page_id`, `author_id`, `text`, `updated_on`, `version`) VALUES (27, 1, 'h1. Breakpoints\\r\\n\\r\\nNous utilisons bootstrap 5 avec ses breakpoints officiels\\r\\n\\r\\nhttps://getbootstrap.com/docs/5.0/layout/breakpoints/\\r\\n\\r\\n|_.Breakpoint|_.Class infix|_.Dimensions|_.Appareil|\\r\\n|X-Small|None|<576px|Mobile|\\r\\n|Small|sm|<89>576px|Mobile|\\r\\n|Medium|md|<89>768px|Mobile|\\r\\n|Large|lg|<89>992px|Ordinateur|\\r\\n|Extra large|xl|<89>1200px|Ordinateur|\\r\\n|Extra extra large|xxl|<89>1400px|Ordinateur|\\r\\n', '2021-02-26 17:46:08', 1)):\r\n \r\n\r\n\r\nHere is my redmine's environment\r\n\r\nEnvironment:\r\n Redmine version 4.1.1.stable\r\n Ruby version 2.6.3-p62 (2019-04-16) [x86_64-linux]\r\n Rails version 5.2.4.2\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\nSCM:\r\n Git 2.25.1\r\n Filesystem \r\nRedmine plugins:\r\n no plugin installed\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Invalid"}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-02-26T17:56:40Z", "updated_on": "2021-04-20T06:08:03Z", "closed_on": "2021-04-19T22:43:47Z"}, {"id": 34790, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 507187, "name": "Moritz Poldrack"}, "category": {"id": 3, "name": "SCM"}, "subject": "Track tickets by branch-name", "description": "Hello,\r\n\r\nI'd like to propose to include the functionality of \"this\":https://github.com/mikoto20000/redmine_git_branch_hook seemingly unmaintained Plugin into mainline. Since nowadays git-flow and similar approaches are common and this would be an easy way to prevent the issue of forgotten @refs \u2026@ in commit-messages.\r\nThis is in no way limited to git. Same applies for other SCMs\r\n\r\nSo to summarize I'd like to propose:\r\n* getting related ticket by branch-name\r\n** additional tickets can still be referenced by adding them to the message\r\n** additional actions can still be performed using the message\r\n* closing issues on merge", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-02-23T08:27:52Z", "updated_on": "2021-02-23T08:27:52Z"}, {"id": 34778, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 127719, "name": "Frederico Camara"}, "category": {"id": 41, "name": "Issues workflow"}, "subject": "Inconsistencies working with workflow permissions", "description": "Found two problems working with setting workflow permissions to read_only:\r\n\r\nOn Admin > Workflows > Permissions:\r\n when you set tracker_id to \"read_only\" for the first tracker/status, on a project that has this tracker as the first tracker, you can't chose another tracker when creating a new issue,\r\n when you set subject to \"read-only\" for the first tracker/status, you can't create a new issue with this tracker, as it it required and has no default.\r\n\r\nEditing an issue\r\n after you change from a status that have tracker_id set to \"read-only\", to another status that doesn't\r\n before you save\r\n when you try to change the tracker to another tracker\r\n the page refreshes and doesn't change the tracker_id\r\n\r\nPatches attached:", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2021-02-20T18:59:17Z", "updated_on": "2021-02-21T05:02:30Z"}, {"id": 34774, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 235161, "name": "Ruben Kelevra"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Add a filter for 'Start-Date is not in the future'", "description": "I try to setup 'My Page' in Redmine, to show me the tasks which are in one status and are basically 'doable'. I don't want to see tasks which have a start-date in the future, like tomorrow or in 120 days.\r\n\r\nI just want to see what's available to be done right now.\r\n\r\nI don't think there's a way to do this right now.\r\n\r\nThe closest is 'start date' - 'more than days ago' '0'. But this doesn't show any tasks which have no start date at all.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-02-19T22:15:29Z", "updated_on": "2021-02-19T22:15:29Z"}, {"id": 34773, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 235161, "name": "Ruben Kelevra"}, "category": {"id": 2, "name": "Issues"}, "subject": "Redmine should be able to understand \":30\" or \":5\" in the Estimated time field of issues", "description": "I think the current validation is too strict, and redmine should only look for a number and \":\" to be contained in the field.\r\n\r\nA value of \":30\" should be interpreted as 30 minutes and a value of \":5\" as five minutes.\r\n\r\nThere's really no need to ask the users to enter a leading zero for validation purposes.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-02-19T20:57:04Z", "updated_on": "2021-02-19T20:57:04Z"}, {"id": 34766, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 3866, "name": "Felix Sch\u00e4fer"}, "category": {"id": 32, "name": "REST API"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Better error message when no API format is recognised", "description": "At Planio sometimes see users trying to make API requests using the HTTP @Accept: application/json@ header but forgetting to add @.json@ at the end of the path. This currently leads to a @raise@ with a @500 Internal Server Error@.\r\n\r\nWe propose the following patch to correctly return a @406 Not Acceptable@ (this is the same HTTP status Rails uses when the passed @Accept@ HTTP header can not be served), log the error instead of @raise@-ing, and returning a helpful message in the HTTP response.\r\n\r\n\r\n\r\ndiff --git a/lib/redmine/views/builders.rb b/lib/redmine/views/builders.rb\r\nindex 653c1bd6b..3c977df67 100644\r\n--- a/lib/redmine/views/builders.rb\r\n+++ b/lib/redmine/views/builders.rb\r\n@@ -30,7 +30,9 @@ module Redmine\r\n when 'xml', :xml then Builders::Xml.new(request, response)\r\n when 'json', :json then Builders::Json.new(request, response)\r\n else\r\n- raise \"No builder for format #{format}\"\r\n+ Rails.logger.error \"No builder for format #{format.inspect}\"\r\n+ response.status = 406\r\n+ return \"We couldn't handle your request, sorry. If you were trying to access the API, make sure to append .json or .xml to your request URL.\\n\"\r\n end\r\n if block_given?\r\n yield(builder)\r\n\r\nRouge::Formatters::HTMLLineHighlighter.new(formatter, highlight_lines: [3, 5]) will split your code into lines and wrap the lines specified by the highlight_lines option in a span with a class name specified by the highlight_line_class option (default: hll).\r\n \r\n\r\nCan the redmine be extended to support these parameters?\r\nBest regards", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-02-18T11:21:44Z", "updated_on": "2021-02-18T11:21:44Z"}, {"id": 34718, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 15, "name": "Importers"}, "subject": "Auto guess file encoding when importing CSV file", "description": "When importing a CSV file, file encoding is pre-selected according to general_csv_encoding in config/locales/*.yml. For example, \"CP932\" is selected by default when your language setting is Japanese.\r\n\r\nI often use CSV files with UTF-8 encoding, but it's a bother to re-select UTF-8 in the encoding drop-down every time.\r\n\r\nIt would be nice if Redmine auto guesses the file encoding when importing a CSV file. Redmine already auto guess file encoding when displaying attached files or repository contents using @Setting.repositories_encodings@.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-02-13T08:33:52Z", "updated_on": "2021-02-13T08:33:52Z"}, {"id": 34709, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 502426, "name": "Gregor Hiltmann"}, "category": {"id": 39, "name": "PDF export"}, "subject": "No Images in PDF export of issue list (with option show description)", "description": "This error is shown in current release 4.1.1 and the version used by redmine.org.\r\n\r\nSteps to reproduce:\r\n# Create a new issue, upload an attachment - e.g. \"example.png\" (like in this issue)\r\n# Link the attachment in the description like this:\r\n!example.png!\r\n# Create the issue, show the issue list\r\n# Click on options, check show description and apply\r\n# Now the issue list images are shown\r\n# Click on (also available in) PDF below the list\r\n\r\nResult:\r\nThe PDF doesn't contain the image. Instead the filename ist shown. In production log we see an error (something like filename is missing) -> filename object is NIL.\r\n\r\nHow to repair - simply do this:\r\n# open the file lib/redmine/export/pdf/issues_pdf_helper.rb\r\n# search for: \r\npdf.RDMwriteHTMLCell(0, 5, '', '', text, [], \"LRB\")\r\n \r\n# replace with:\r\npdf.RDMwriteHTMLCell(0, 5, '', '', text, issue.attachments, \"LRB\")\r\n \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-02-11T18:22:30Z", "updated_on": "2021-03-01T07:30:48Z"}, {"id": 34695, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 135455, "name": "Solt\u00e9sz Andr\u00e1s"}, "category": {"id": 2, "name": "Issues"}, "subject": "Allow editing the issue description immediately (issue editing form)", "description": "Currently, the issue editing form will not display the description of the task as it first appears and requires the user to click on a link to display the description and start editing it.\r\n\r\nThis is a big usability problem and no other, modern, notable task/issue manager implements it this way. \r\n\r\nI have been working with Redmine for many years in multiple settings (at different companies) and I can safely say that it unnecessarily slows down issue editing in a very big percentage of cases. \r\n\r\nRequest: Display the description editor field immediately when the editing of the issue starts, together with all of the other editing fields.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-02-07T11:30:18Z", "updated_on": "2021-02-16T13:51:48Z"}, {"id": 34681, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 29628, "name": "Alexander Meindl"}, "category": {"id": 28, "name": "LDAP"}, "subject": "LDAP test not running on redmine build server", "description": "All LDAP tests are skipped on Redmine build server.\r\n\r\nSee e.g. https://www.redmine.org/builds/logs/build_trunk_mysql_ruby-2.6_1384.html\r\n\r\nYou will find \"(Test LDAP server not configured)\" in all test results. This means, that no ldap tests was running because of ldap server was not configured or wrong configured. \"ldap_configured?\":/projects/redmine/repository/entry/trunk/test/test_helper.rb#L123 checks it and failed.\r\n\r\nThis means at the moment no ldap test is running on redmine.org testing infrastructure.\r\n\r\nSolution: Ldap server should be configured on test server.\r\n\r\nPS: LDAP tests are skipped on https://gitlab.com/redmine-org/redmine/, too.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-02-03T19:34:58Z", "updated_on": "2021-02-03T19:43:05Z"}, {"id": 34654, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 496301, "name": "Stan Efremov"}, "category": {"id": 40, "name": "Issues planning"}, "subject": "Accounting for the closing date of the issue when calculating the overdue", "description": "When calculating the overdue for issues, the closing date of the issues is not taken into account, despite the availability of relevant information. An overdue issue remains overdue even after it is closed.\r\n\r\nEnvironment:\r\n Redmine version 4.0.4.stable\r\n Ruby version 2.6.5-p114 (2019-10-01) [x86_64-linux]\r\n Rails version 5.2.3\r\n Environment test\r\n Database adapter PostgreSQL\r\n Mailer queue ActiveJob::QueueAdapters::InlineAdapter\r\n Mailer delivery test\\nSCM:\r\n Subversion 1.9.7\r\n Git 2.17.1\r\n Filesystem \r\nRedmine plugins: no plugin installed", "done_ratio": 0, "created_on": "2021-01-29T08:14:40Z", "updated_on": "2021-02-01T04:41:14Z"}, {"id": 34641, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 362529, "name": "Yuichi HARADA"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 2, "name": "Issues"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "When editing an issue, the Log time and/or Add notes does not show or hide dynamically", "description": "I changed the project when editing an issue, but the Log time does not show or hide dynamically. There is a mixture of projects with the Time tracking module enabled or disabled.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-01-27T01:32:40Z", "updated_on": "2021-02-25T03:07:18Z"}, {"id": 34635, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 494910, "name": "Tymofii Smyrnov"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Separated email template for \"Closed\" status.", "description": "Hi Team,\r\n\r\nI need to a few strings in the email notifications for tickets which status changed to \"Closed\".\r\nIs there any possibility to make a separated template specifically for this scenario?\r\n\r\nI've looked through the forum but haven't found any information on this case.\r\n\r\nThanks in advance.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-01-25T15:25:37Z", "updated_on": "2021-01-25T15:26:07Z"}, {"id": 34634, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 21060, "name": "Ivan Cenov"}, "assigned_to": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 1, "name": "Wiki"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Can't add deleted wiki Tab (404)", "description": "This issue is inspired by a thread in the forum (message#61955)\r\n\r\nAn user delete all wiki pages including the root page. Then he could not see the root page and could not create wiki pages any more.\r\n\r\nThe solution was to disable Wiki module and then enable it again. Then the root wiki page appeared again (may be it has been recreated on enabling wiki module).\r\n\r\nSo I think that it should be harder to delete the root wiki page or make it not erasable.\r\nHowever, if it remains erasable, Wiki module should be made inactive when this page is deleted.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2021-01-25T08:34:53Z", "updated_on": "2021-07-27T03:19:32Z"}, {"id": 34609, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 369008, "name": "Holger M\u00f6\u00dfinger"}, "category": {"id": 2, "name": "Issues"}, "subject": "Setting for partially independent start-date, end-date in parent tickets", "description": "In issue #5490 the global settings option for an independent subtask priority/start date/due date/done ratio was implemented (closed in #5490-91). There were some fixes to this or related functionality in #21449, #20994 and #27533.\r\n\r\nIn note #5490-91 Jean-Philippe Lang mentioned a third \"restricted children\" option as to vaguely specified.\r\n\r\nI would like to propose a specification for this third option allowing a hybrid approach, where it is still possible to set a separate start- and end-date for the parent ticket and calculate the overall date according to the following ruleset.\r\n\r\nFor the start date:\r\n* If the start date of the parent ticket is \"older/lower\" than the the oldest date of the subtickets, the parent tickets own start date is used (just like in the independent setting now).\r\n* If the start date of any of the subtickets is older than the parent ticket, then the oldest subticket date is used (just like in the dependent setting now).\r\n\r\nFor the end date:\r\n* If the end date of the parent ticket is \"newer\" than the the newest date of the subtickets, the parent tickets own end date is used (just like in the independent setting now).\r\n* If the end date of any of the subtickets is newer than the parent ticket then newest subticket date is used (just like in the dependent setting now).\r\n\r\nAs an example: \r\nLet have a parent-ticket with a start-date as 01. March 2021. \r\nAdding a subticket with a start-date of 10. March 2021, the parent-ticket keeps the start-date 01. March 2021.\r\nAdding another subticket with a start-date of 15. February 2021, the parent start-date gets updated to 15. February too.\r\nNow setting the parent-ticket start-date to 05. February is allowed.\r\nSetting the parent-ticket start-date to 05. March, raises an error stating a subticket restricts the start-date to 15. February.\r\n(The user could even be asked if he wants to update the subticket date(s) accordingly, but I would consider that optional at first.)\r\n\r\nUI-wise I would suggest leaving the start and end Dates in the parent tickets visible and editable but check for the above conditions when submitting changes. \r\n\r\nAdding this feature would allow to have parent tickets keep track of their scheduled dates while automatically moving them if subtask requires it. This would make working with project schedules e.g. Gantt-Chart more useful.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-01-20T11:22:03Z", "updated_on": "2021-01-20T11:22:03Z"}, {"id": 34593, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 141725, "name": "Fabrizio Sebastiani"}, "subject": "privacy problem on users info", "description": "If a logged-is user start to access cyclically to urls likes this:\r\n\r\n\r\n https://example.com/redmine/users/5\r\n https://example.com/redmine/users/6\r\n https://example.com/redmine/users/7\r\n ...\r\n \r\n\r\nhe/she will see get the full organization's useers, members, informations, accounts, email etc... This is a particular sensible information if organization needs to hide and protect membership information to all users.\r\n\r\nThis looks violation of privacy information. Also the organization cannot hide to any member this wide information. Looks a design lack. \r\n\r\n\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-01-14T16:23:30Z", "updated_on": "2021-01-24T21:45:18Z"}, {"id": 34583, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 491005, "name": "Mary Cox"}, "assigned_to": {"id": 491005, "name": "Mary Cox"}, "category": {"id": 59, "name": "Filters"}, "subject": "Group by parent project", "description": "How do I export a list which includes the parent project name, or group by the parent project?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-01-11T10:42:46Z", "updated_on": "2021-01-24T21:54:45Z"}, {"id": 34570, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 470637, "name": "James Brady"}, "category": {"id": 17, "name": "Permissions and roles"}, "subject": "Misleading workflow/permission issue", "description": "I'm using the latest version of Turnkey Linux Redmine: \r\nhttps://www.turnkeylinux.org/redmine\r\n\r\n\r\nEnvironment:\r\n Redmine version 4.1.1.stable\r\n Ruby version 2.6.6-p146 (2020-03-31) [x86_64-linux]\r\n Rails version 5.2.4.2\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery sendmail\r\nSCM:\r\n Subversion 1.10.4\r\n Git 2.20.1\r\n Filesystem \r\nRedmine plugins:\r\n no plugin installed\r\n \r\n\r\nIf a user is assigned multiple roles, any workflow defined on any role will affect that user, even if one of those roles has no editing issue edit permission. \r\n\r\nExample: \r\n* Role 1\r\n** I don't remove *Close* status from all statuses in that role's Workflow.\r\n** I remove all edit permissions from Issue Tracking permissions. \r\n* Role 2\r\n** I remove *Close* status from all statuses from that role's Workflow. \r\n** I allow *Edit Issues* permission in Issue Tracking permissions. \r\n\r\nIf I assign a user both Role 1 and Role 2, he will be able to Close issues. \r\n\r\nNot sure if you'd consider this a defect per se, but I just spent a chunk of time configuring a new redmine server at work, and it took me a bit to figure out why my users had the ability to close issues, even when the workflows I painstakingly defined for them appeared to prevent it. \r\nIt was because I was using multiple roles to control their access, and I hadn't edited the workflow of the other role to match, or at least not conflict. \r\nThe confusion is bolstered by the fact that you can't see the role in the dropdown on the Workflow edit page, to correct such a mistake, until you restore the edit permissions on that Role's edit page, in the Permission's section. \r\n\r\nSince issue status workflows only really come into play for someone who has edit permission for Issues, I suggest that worfklows become effectively disabled for any role whenever that role loses edit permission for Issues. ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2021-01-08T00:15:03Z", "updated_on": "2021-02-02T10:47:10Z"}, {"id": 34556, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 2, "name": "Issues"}, "subject": "Setting to change the max. no. of members to propose as watcher on the new issue form", "description": "Currently, the \"Watchers\" section in the new issue form shows up to 20 members of the project. I think it would be better if the fixed number is configurable on the Administration page.\r\n\r\nUse cases:\r\n* Suppose a team with 21 persons (slightly over the maximum number of watchers, 20). When you creating a new issue, you can never see the checkboxes even if you wanted to. The problem can be addressed if an admin can increase the maximum number of watchers to 21 or more\r\n* I sometimes get requests from my customers that they don't want to see a checkbox to add a watcher. In such a case, they can set the setting to 0 to hide the checkboxes and always use the \"Search for watchers to add\" feature to add watchers\r\n\r\n!{width: 586px; border: 1px solid grey;}.wachers-checkboxes.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2021-01-05T09:09:54Z", "updated_on": "2021-02-02T10:52:50Z"}, {"id": 34497, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 488734, "name": "Abeesh M P"}, "category": {"id": 53, "name": "Performance"}, "subject": "High memory usage in Redmine 4.0.5.stable", "description": "Hi Team, \r\n\r\nWe are getting high memory usage in Redmine, we have been using redmine (same version ) for last 1 year or more.But we didn't face this issue untill 2 weeks before, For the last two weeks , we are seeing high memory usage in Redmine.\r\n\r\nEnvironment:\r\n Redmine version 4.0.5.stable\r\n Ruby version 2.5.1-p57 (2018-03-29) [x86_64-linux-gnu]\r\n Rails version 5.2.3\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\n\r\n\r\nIt would be nice if you can provide some information to debug this issue.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "153"}], "created_on": "2020-12-23T12:07:23Z", "updated_on": "2021-01-11T18:38:49Z"}, {"id": 34496, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 434111, "name": "C S"}, "category": {"id": 2, "name": "Issues"}, "subject": "Assign Tickets only to groups", "description": "At the moment we can assign Tickets to a group or to a single user.\r\nSo if there are many Groups with many Users, the DropDown is longer as the screen ;)\r\nAlso there are moments there are no backup for sick people and no other got the task...\r\nIt would be very helpful, if there is a possibility to restrict the Assign only to groups...\r\nWhat do you think about that ?\r\n\r\nStay healthy!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-12-23T11:20:28Z", "updated_on": "2020-12-24T02:16:19Z"}, {"id": 34494, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 259873, "name": "Mizuki ISHIKAWA"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Rename the save, edit and delete buttons on the query form", "description": "It's hard to tell that the subject of the Save, Edit and Delete buttons on the Query form is a custom query.\r\nHow about changing it as follows?\r\n\r\n* Save => Save custom query\r\n* Edit => Edit custom query\r\n* Delete => Delete custom query\r\n\r\n!{width: 70%; border: 1px solid #ccc}save_after_change.png!\r\n!{width: 70%; border: 1px solid #ccc}edit_and_delete_after_change.png!", "done_ratio": 0, "created_on": "2020-12-23T07:01:42Z", "updated_on": "2021-03-25T07:34:01Z"}, {"id": 34490, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 15, "name": "Importers"}, "subject": "CSV import does not accept drag and drop of a CSV file", "description": "\"Select the file to import\" area on the \"Import issues\", \"Import time entries\", and \"Import users\" pages don't support drag and drop of a file.\r\n\r\n!{width: 643px; border: 1px solid grey;}.import-issues.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2020-12-23T00:25:42Z", "updated_on": "2021-05-07T07:08:15Z"}, {"id": 34489, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 488656, "name": "Nicolas ESTIENNE"}, "category": {"id": 59, "name": "Filters"}, "subject": "The project jump box does not work", "description": "Hi, I'm using this version of redmine:\r\n\r\nEnvironment:\r\n Redmine version 4.1.1.stable\r\n Ruby version 2.6.6-p146 (2020-03-31) [x86_64-linux]\r\n Rails version 5.2.4.2\r\n Environment production\r\n Database adapter Mysql2\r\n \r\n\r\nAnd I cannot switch to another project using the \"Jump to project\" filter: it does not work. I have the same issue with Filter on Issue list.\r\nIt seems that all filters are \"frozen\". I tested with Google Chrome, Safari on Mac, FireFox and Chrome.\r\nThanks for your help\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2020-12-22T17:22:15Z", "updated_on": "2021-01-11T19:01:24Z"}, {"id": 34484, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 460226, "name": "Adriano Bellia"}, "category": {"id": 2, "name": "Issues"}, "subject": "Error on issue validation", "description": "When I open a new issue, the data validation (type and required data) works perfectly. If for example I write a character in a numeric field or don't fill a required field I receive the normal red box with the error.\r\nAfter status changes, if the helpdesk or another assigner writes something wrong or doesn't fill a required field I receive the following error:\r\n\r\n> Internal error\r\n> An error occurred on the page you were trying to access.\r\n> If you continue to experience problems please contact your Redmine administrator for assistance.\r\n> \r\n> If you are the Redmine administrator, check your log files for details about the error.\r\n\r\nBelow the production.log generated part:\r\n\r\n\r\nStarted PATCH \"/issues/1884\" for 172.24.112.4 at 2020-12-21 18:20:35 +0100\r\nProcessing by IssuesController#update as HTML\r\n Parameters: {\"utf8\"=>\"\u2713\", \"authenticity_token\"=>\"WrsdDIM7eYhFTkjqMBQW2swULoE38w4FOd3Rwmso0DelQJivomeJW8u1yMJ7Mg78MOKkCxxRy39qjqGYKIgF6w==\", \"form_update_triggered_by\"=>\"\", \"issue\"=>{\"is_private\"=>\"0\", \"project_id\"=>\"15\", \"author_id\"=>\"5\", \"tracker_id\"=>\"11\", \"subject\"=>\"cvbn\", \"description\"=>\"dxcvbnmvcxzvhgjfx\", \"status_id\"=>\"1\", \"priority_id\"=>\"2\", \"assigned_to_id\"=>\"\", \"custom_field_values\"=>{\"13\"=>\"Redmine Interno\", \"17\"=>\"dcvbn\", \"18\"=>\"\", \"19\"=>\"\", \"20\"=>\"15 giorni - Richiesta ordinaria\", \"21\"=>\"\", \"22\"=>\"Estratto conto ex art. 50\", \"23\"=>\"\", \"24\"=>\"2019-11-16\", \"25\"=>\"2019-11-16\", \"26\"=>\"\", \"27\"=>\"2019-11-16\", \"28\"=>\"2019-11-16\", \"30\"=>\"Tasso Legale\", \"29\"=>\"\", \"31\"=>\"12345\", \"32\"=>{\"blank\"=>\"\"}}, \"notes\"=>\"\", \"private_notes\"=>\"0\", \"lock_version\"=>\"1\"}, \"was_default_status\"=>\"1\", \"last_journal_id\"=>\"\", \"commit\"=>\"Invia\", \"next_issue_id\"=>\"557\", \"issue_position\"=>\"1\", \"issue_count\"=>\"3\", \"id\"=>\"1884\"}\r\n Current user: Administrator (id=1)\r\n Rendering issues/edit.html.erb within layouts/base\r\n Rendered attachments/_form.html.erb (2.6ms)\r\n Rendered issues/_form_custom_fields.html.erb (15.3ms)\r\n Rendered issues/_attributes.html.erb (41.6ms)\r\n Rendered issues/_form.html.erb (58.2ms)\r\n Rendered issues/_edit.html.erb (66.3ms)\r\n Rendered issues/edit.html.erb within layouts/base (68.7ms)\r\nCompleted 500 Internal Server Error in 168ms (ActiveRecord: 9.6ms)\r\n\r\nActionView::Template::Error (undefined method `any?' for nil:NilClass):\r\n 40: \r\n 41:\r\n 42: \"><%= l(:label_attachment_plural) %> \r\n 43: <% if @attachments.any? && @issue.safe_attribute?('deleted_attachment_ids') %>\r\n 44: <%= link_to l(:label_edit_attachments), '#', :onclick => \"$('#existing-attachments').toggle(); return false;\" %>
\r\n 45: \">\r\n 46: <% @attachments.each do |attachment| %>\r\n\r\napp/views/issues/_edit.html.erb:43:in `block in _app_views_issues__edit_html_erb__169474526129585408_70197454896560'\r\napp/helpers/application_helper.rb:1242:in `labelled_form_for'\r\napp/views/issues/_edit.html.erb:1:in `_app_views_issues__edit_html_erb__169474526129585408_70197454896560'\r\napp/views/issues/edit.html.erb:3:in `_app_views_issues_edit_html_erb__3897739985162189416_70197464417020'\r\napp/controllers/issues_controller.rb:194:in `block (2 levels) in update'\r\napp/controllers/issues_controller.rb:193:in `update'\r\nlib/redmine/sudo_mode.rb:63:in `sudo_mode'\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "148"}], "created_on": "2020-12-21T17:29:15Z", "updated_on": "2021-01-24T21:51:39Z"}, {"id": 34476, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 263566, "name": "ciel ciel"}, "category": {"id": 13, "name": "Time tracking"}, "subject": "Link_to_Timelog_query", "description": "I have been working with Redmine 3.4.6.6, for 3 years, and in order to customize the display instead of details of the field (spent time) to a custom table in the linker of the default table (example I created the query_1 report),.\r\n !Link_to_Timelog_query.JPG!\r\nI have not found the solution to remedy this problem, please some help me to solve this problem , think the patch should be ported to the part of this code halper /issues_helper rb\r\ndef issue_spent_hours_details(issue)\r\n if issue.total_spent_hours > 0\r\n path = project_time_entries_path(issue.project, :issue_id => \"~#{issue.id}\")\r\n\r\n if issue.total_spent_hours == issue.spent_hours\r\n link_to(l_hours_short(issue.spent_hours), path)\r\n else\r\n s = issue.spent_hours > 0 ? l_hours_short(issue.spent_hours) : \"\"\r\n s << \" (#{l(:label_total)}: #{link_to l_hours_short(issue.total_spent_hours), path})\"\r\n s.html_safe\r\n end\r\n end\r\n end\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2020-12-18T23:41:24Z", "updated_on": "2021-03-15T05:58:19Z"}, {"id": 34473, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 130529, "name": "C\u00e9sar DJ Ca\u00ebsar 9114"}, "category": {"id": 10, "name": "UI"}, "subject": "Displaying the table of content on the right causes wrong position", "description": "Hi everyone,\r\nI installed the latest version of Redmine and I started to try the wiki.\r\nI wrote a simple page with titles ans subtitles, and at the very beginning of the page I put:\r\n\r\n
\r\n{{>toc}}\r\n \r\n\r\nto get the table of content on the top right corner.\r\n\r\nActually as you can see the result is quite disturbing because I would have expected to get the TOC under \"Modifier Surveiller\".\r\n\r\nI think it may be a UI bug.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "156"}], "created_on": "2020-12-18T10:42:27Z", "updated_on": "2020-12-19T09:02:35Z"}, {"id": 34457, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 487241, "name": "Marc LHERBETTE"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Show custom field in notification email", "description": "It would be nice to be able to add fields (standard or custom) in the **issue attributes** of the notification email (like the parent task as it have be done here : #34302)\r\n\r\nThe idea, in my case, is to add a user custom fields (e.g. Department or Agency of the user that submit the issue) to add more context informations of the issue", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-12-15T10:57:29Z", "updated_on": "2020-12-15T16:58:23Z"}, {"id": 34451, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 487402, "name": "Juraj Hajka"}, "category": {"id": 2, "name": "Issues"}, "subject": "error getting after upgrade redmine from 3.4.13.stable to 4.1.1", "description": "Hi all, \r\nI finished upgrade, during upgrade redmine or plugins no error or warnings .\r\nI was upgrading from following configuration.\r\nEnvironment:\r\n Redmine version 3.4.13.stable\r\n Ruby version 2.5.5-p157 (2019-03-15) [x86_64-linux-gnu]\r\n Rails version 4.2.11.1\r\n Environment production\r\n Database adapter Mysql2\r\nSCM:\r\n Git 2.20.1\r\n Filesystem \r\nRedmine plugins:\r\n redmine_contacts 4.3.2\r\n redmine_contacts_helpdesk 4.1.11\r\n redmine_reporter 1.0.3\r\n\r\nLogin screen will not appear.\r\nI see this in logs.\r\n\r\nplugins/redmine_contacts/lib/redmine_contacts.rb:75:in `settings'\r\nplugins/redmine_contacts/app/models/contacts_setting.rb:124:in `settings'\r\nplugins/redmine_contacts/app/models/contacts_setting.rb:58:in `contacts_show_in_top_menu?'\r\nplugins/redmine_contacts/init.rb:128:in `block (2 levels) in
'\r\nlib/redmine/menu_manager.rb:487:in `allowed?'\r\nlib/redmine/menu_manager.rb:197:in `block in menu_items_for'\r\nlib/redmine/menu_manager.rb:196:in `each'\r\nlib/redmine/menu_manager.rb:196:in `menu_items_for'\r\nlib/redmine/menu_manager.rb:115:in `render_menu'\r\napp/views/layouts/base.html.erb:66:in `_app_views_layouts_base_html_erb___2715056335201344404_47038341947720'\r\nlib/redmine/sudo_mode.rb:65:in `sudo_mode'\r\n Current user: admin (id=1)\r\n Rendering welcome/index.html.erb within layouts/base\r\n Rendered welcome/index.html.erb within layouts/base (25.2ms)\r\n Rendered plugins/redmine_contacts/app/views/common/_additional_assets.html.erb (1.1ms)\r\nCompleted 500 Internal Server Error in 118ms (ActiveRecord: 11.9ms)\r\n\r\nActionView::Template::Error (undefined method `with_indifferent_access' for #):\r\n 63: \r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2020-04-29T13:52:20Z", "updated_on": "2020-05-02T04:49:00Z"}, {"id": 33361, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 113681, "name": "Robert Korulczyk"}, "category": {"id": 12, "name": "Translations"}, "subject": "Update Polish translation", "description": "", "done_ratio": 0, "created_on": "2020-04-27T11:39:46Z", "updated_on": "2020-06-02T16:58:20Z"}, {"id": 33352, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Enable inline issue autocomplete in issue id query filter fields", "description": "The query filters on issues and related issues accept issue ids. I see several use-cases/benefits of enabling the inline issue subject autocomplete functionality added by #31989 for these fields.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-25T08:12:59Z", "updated_on": "2020-04-28T15:20:21Z"}, {"id": 33350, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 43, "name": "Project settings"}, "subject": "Rows in Forums tab of project setting are not striped according to odd/even rule", "description": "Tables in other tabs are striped. The table in the Forum tab should be striped as well.\r\n\r\n!{width: 714px; border: 1px solid grey;}.rows-are-not-striped.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "110"}], "created_on": "2020-04-25T00:48:59Z", "updated_on": "2020-05-15T05:50:42Z"}, {"id": 33345, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 362529, "name": "Yuichi HARADA"}, "category": {"id": 7, "name": "Accounts / authentication"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Improvement of LDAP connection error message", "description": "When LDAP cannot be connected for some reason, the following message is displayed.\r\n\r\n!{width:600px;border:1px solid #ccc;}before.png!\r\n\r\nThe error message is displayed as it is, but I don't know if it is a message from LDAP. You can understand that it is an LDAP message by adding a fixed message to the beginning as shown below.\r\n\r\n!{width:600px;border:1px solid #ccc;}after.png!", "done_ratio": 0, "created_on": "2020-04-23T05:20:20Z", "updated_on": "2020-09-13T02:26:22Z"}, {"id": 33336, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 7697, "name": "Patrice Bonhomme"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Send notification when new issue created by email ?", "description": "I am using Redmine in my company. Everything is going well. \r\n\r\nBut i am facing a problem. \r\n\r\nWhen user send an email to create an issue in Redmine, there is no notification sent while the issue is created. \r\nI can not find any parameter to set this feature. \r\n\r\n\"Email Notification\"-> \"Issue Added\" , \"Issue Updated\" in the settings are enable. \r\nIf i create an issue directly in Redmine, i receive a mail notification. \r\n\r\nAny help ? \r\n\r\n\r\nEnvironment:\r\n Redmine version 3.4.13.stable.19405\r\n Ruby version 2.5.5-p157 (2019-03-15) [x86_64-linux-gnu]\r\n Rails version 4.2.11.1\r\n Environment production\r\n Database adapter Mysql2\r\nSCM:\r\n Subversion 1.10.0\r\n Git 2.20.1\r\n Filesystem \r\nRedmine plugins:\r\n additionals 2.0.22\r\n clipboard_image_paste 1.13\r\n redmine_banner 0.1.2\r\n redmine_ldap_sync 2.1.1.devel\r\n redmine_lightbox2 0.4.5\r\n \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "150"}], "created_on": "2020-04-21T17:30:52Z", "updated_on": "2020-04-21T17:30:52Z"}, {"id": 33328, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 15, "name": "Importers"}, "subject": "Ability to import watchers when importing issues from csv", "description": "Importing watchers while importing from csv is important\r\nbecause it is used in many scenarios.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-20T11:45:30Z", "updated_on": "2020-04-20T11:45:30Z"}, {"id": 33327, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 15, "name": "Importers"}, "subject": "Import issues project tree not displaying correctly", "description": "Third or more level of nesting is not displayed on project drop-down while importing issues.\r\n\r\nI suggest using the same code used for project dropdown from filter on\r\n/projects URL\r\n\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-04-20T11:40:57Z", "updated_on": "2020-04-20T11:40:57Z"}, {"id": 33325, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 454834, "name": "Ali Hamdan"}, "category": {"id": 13, "name": "Time tracking"}, "subject": "Export spent time report as PDF", "description": "Is it possible to have a patch that will add the ability of exporting the spent time report as PDF including the custom fields", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-20T02:20:39Z", "updated_on": "2021-01-09T01:34:31Z"}, {"id": 33308, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 29628, "name": "Alexander Meindl"}, "category": {"id": 58, "name": "Issues list"}, "subject": "Implement grouping by date (e.g start, due, creation, update, closing dates) for year and month/year", "description": "Date fields in queries should be groupable with year/month only - without day.\r\n\r\nImplementation could be the same way as with TimestampQueryColumn. We could use DateQueryColumn.\r\n\r\nThe result should be (example data):\r\n\r\n- 23/5/2019\r\n- 24/5/2019\r\n- 23/3/2019\r\n\r\nfor month/year:\r\n\r\n* 5/2019\r\n** 23/5/2019\r\n** 24/5/2019\r\n* 3/2019\r\n** 23/3/2019\r\n\r\nfor year:\r\n* 2019\r\n** 23/5/2019\r\n** 24/5/2019\r\n** 23/3/2019\r\n\r\nThis would require, that three options for one date exist:\r\n\r\n* Due date\r\n* Due date (Month/Year)\r\n* Due date (Year)\r\n\r\nand \r\n\r\n* Start date\r\n* Start date (Month/Year)\r\n* Start date (Year)\r\n\r\netc.\r\n\r\nWhat do you think about this idea?\r\n\r\n\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-18T14:14:39Z", "updated_on": "2020-04-18T14:17:33Z"}, {"id": 33302, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 80025, "name": "j ronald"}, "category": {"id": 2, "name": "Issues"}, "subject": "What about the editor for \"%Done\" be a numeric editor with a spinbox", "description": "Currently it is a combobox with 11 options: 0%, 10%, ..., 100%\r\nRecenctly I'm reading a book called \"mini habit\", and got a demand that updating \"%Done\" a little for usual.\r\n\r\nThanks", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-17T09:24:14Z", "updated_on": "2020-04-19T11:34:00Z"}, {"id": 33297, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 153590, "name": "Vasili Korol"}, "category": {"id": 3, "name": "SCM"}, "subject": "Sort git tags in descending order", "description": "I think it would be a bit more convenient if the items of the \"tags\" dropdown on a Git repository page were sorted in a descending order (newest to oldest). At the moment, if there are many tags, one has to scroll down the list to find the newest ones, whereas in my experience they are more frequently used, and should therefore be shown at the top.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-16T12:28:39Z", "updated_on": "2021-04-10T06:45:31Z"}, {"id": 33291, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 361769, "name": "Liane Hampe"}, "category": {"id": 34, "name": "Gantt"}, "subject": "Gantt conversion to png failed with error w.r.t. font 'helvetica'", "description": "h2. Expected Behavior\r\n\r\nGantt-Diagramm converts to png file format.\r\n\r\nh2. Actual Behavior\r\n\r\nClicking on the png link at the bottom of the Gantt page causes an error.\r\n\r\nh3. Essentials of Error Message\r\n\r\nMiniMagick::Error in GanttsController#show \r\n`.../tmp/mini_magick20200415-1-ufk9mt.png` failed with error: convert-im6.q16: unable to read font `helvetica' @ error/annotate.c/RenderFreetype/1333. convert-im6.q16: non-conforming drawing primitive definition `text' @ error/draw.c/RenderMVGContent/4301.\r\n\r\nSee the two attached sreenshots of the very long error message.\r\n\r\nh2. Steps for Reproduction\r\n\r\n# Install Redmine according to the Technical Details below with a database populated only be Redmines default data\r\n# Define a Project by only setting a name\r\n# Create a Ticket by only setting name and due date\r\n# Go to Gantt page and click the png link at the bottom\r\n\r\nh2. Technical Details\r\n\r\nRedmine 4.1.1.stable\r\nDefault administrator account changed \t\r\nAttachments directory writable \t\r\nPlugin assets directory writable (./public/plugin_assets) \t\r\nMiniMagick available (optional) \t\r\nImageMagick convert available (optional) \t\r\nImageMagick PDF support available (optional) \t\r\n\r\nEnvironment:\r\n Redmine version 4.1.1.stable\r\n Ruby version 2.5.8-p224 (2020-03-31) [x86_64-linux]\r\n Rails version 5.2.4.2\r\n Environment development\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\nSCM:\r\n Subversion 1.10.4\r\n Mercurial 4.8.2\r\n Git 2.20.1\r\n Filesystem \r\nRedmine plugins:\r\n no plugin installed\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "160"}], "created_on": "2020-04-15T09:06:37Z", "updated_on": "2020-05-14T08:51:38Z"}, {"id": 33287, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 451841, "name": "Sarthak Bakshi"}, "subject": "Issue File Column Attachment Link Error", "description": "Attachments link on issue page inside Files column is breaking and file is unable to view.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "157"}], "created_on": "2020-04-10T19:28:55Z", "updated_on": "2020-08-16T20:41:36Z"}, {"id": 33286, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 151490, "name": "Hirofumi Kadoya"}, "subject": "Multiple issue ids in \"Subject\" filter", "description": "at custom query\r\nI can select single in subject \r\nI can select multiple in issue \r\n\r\nI'd like to select mulutiple likely issue\r\n\r\n\u30fc\u30fcJa\u3000start\u30fc\u30fc\r\n\u30ab\u30b9\u30bf\u30e0\u30af\u30a8\u30ea\u30fc\u306e\u984c\u540d\u306b\u304a\u3044\u3066\r\n\u542b\u3080\u3001\u304a\u3088\u3073\u542b\u307e\u306a\u3044\u306e\u6761\u4ef6\u306b\u3082\r\n\u30ab\u30f3\u30de\u3092\u5165\u308c\u305f\u5834\u5408\u3001\u30a2\u30f3\u30c9\u6761\u4ef6\u3068\u3057\u3066\u307b\u3057\u3044\r\n\r\n\u30c1\u30b1\u30c3\u30c8\u3068\u540c\u3058\u3088\u3046\u306b\u304a\u9858\u3044\u3057\u307e\u3059\r\n\u30fc\u30fcJa\u3000end\u30fc\u30fc", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-10T07:56:13Z", "updated_on": "2020-04-10T07:56:13Z"}, {"id": 33276, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 120777, "name": "Andreas Baumg\u00e4rtner"}, "category": {"id": 14, "name": "Custom fields"}, "subject": "add per project configuration of Custom fields / Spent time", "description": "it would be very helpful to have addtional fields with same functionality as Enumerations / Activities (time tracking) for Spent time.\r\n\r\nA - additional global field and global value list with value selection per project (exactly same as \"Activities (time tracking)\"\r\n!redmine_enumerations_activities.jpg!\r\n\r\nOR\r\n\r\nB - Custom Fields / Spent Time - add Projects to Spent Time as with Issues - see comparison below - similar to suggestion #30485\r\n!redmine_customfield_key_value.jpg!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-04-08T07:25:29Z", "updated_on": "2020-04-08T07:25:29Z"}, {"id": 33257, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 13, "name": "Time tracking"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Bulk edit for time entries does not support User filed", "description": "In Redmine 4.1, time entry has a new User field that allows entering another user's spent time (#3848).\r\n\r\nHowever, the User field is missing on the bulk edit screen for time entries. I think it is better to have the User field in bulk edit screen as well in order to reap the benefit of the new feature.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-04-05T14:26:32Z", "updated_on": "2020-04-06T06:23:09Z"}, {"id": 33240, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 34, "name": "Gantt"}, "subject": "Issue subjects in gantt are broken in Internet Explorer if the avatar server is inaccessible", "description": "Focus on issue 3 and 2 in the screenshots below. Issue subjects are not correctly displayed. This can be reproduced when the avatar server is not accessible and your browser is Internet Explorer.\r\n\r\n*BAD:*\r\n!{border: 1px solid grey;}.bad.png!\r\n\r\n*GOOD:*\r\n!{border: 1px solid grey;}.good.png!\r\n\r\n*Steps to reproduce:*\r\n1. Set an invalid URL to @avatar_server_url@ in @configration.yml@ in order to simulate that your browser cannot access to gravatar.com\r\n2. Go to \"Administration\" > Settings > \"Display\" and enable \"Use Gravatar user icons\"\r\n3. Access to Gantt with Internet Explorer. You will see broken issue subjects if the issue has an assignee\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-04-02T15:00:35Z", "updated_on": "2020-04-02T15:00:35Z"}, {"id": 33216, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 452230, "name": "James Barrante"}, "category": {"id": 7, "name": "Accounts / authentication"}, "subject": "/my/account: Prevent users from changing their Email [redmine 4.1.0 stable]", "description": "An organization's policy requires users not be able to change their Redmine e-mail address. \r\n\r\n(Extra background/scenario info: User registration, Project and Role assignment is done by a script which also uses the autologin cookie feature of Redmine: User clicks a link from an Intranet page, that script handles above user creation tasks (if user doesn't exist yet) and logs him/her into Redmine, without ever requiring them to enter a password for Redmine. Logout is done by having Apache redirect the \"/logout\" script to some different URL on the Intranet which also clears the Redmine session cookies.) So far, we are very happy and thankful to all Redmine Contributors.\r\n\r\nWhile it is possible to change the number of extra e-mail addresses from 5 (default) to 0 [Administration > Settings > Users > Maxmimum number of additional email addresses], it still means that (under /my/account) any user logged in is able to change their e-mail address, unless the e-mail address is already taken by someone else in the system.\r\n\r\nHaving an Administration setting to \"lock\" only the Email address of an account would be great. It could help enforce policy of only using the organization's e-mail addresses.\r\n\r\nFrom debug production.log, when a user updates his Email:\r\n\r\nEmailAddress Update (0.2ms) UPDATE `email_addresses` SET `address` = '[redacted]', `updated_on` = '2020-03-29 18:55:59' WHERE `email_addresses`.`id` = 2\r\n \r\n\r\nHacking I tried:\r\n* As a Ruby novice, I really am having a rough time finding my way through the code. Thanks to MVC, I don't believe it's as easy as just commenting out a line of code responsible for triggering the above SQL? Any pointer would be greatly appreciated.\r\n* Maybe app/controllers/email_addresses_controller.rb would be a place to start, but I'm not sure.\r\n\r\nFeature request:\r\n* Add a Checkbox under Administration > Settings > Users: Allow users to change their email addresses, checked by default\r\n\r\n\"Workarounds\":\r\n* Apache Rewrite Rule to block access to /my/account altogether. Easy to implement, radical and effective, but not very friendly, as some useful Preferences (Time zone, UI Language) will be unavailable to users.\r\n* Cronjob to replay any changed e-mail addresses to the MySQL database. Doesn't feel right.\r\n* MySQL trigger to roll back any UPDATE statement to the `email_addresses` table. Hackish but better than cron; will likely break once a heavier DB Migrate script runs after updating Redmine.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-30T08:26:35Z", "updated_on": "2020-03-31T08:11:52Z"}, {"id": 33211, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Include block columns (ex: Description, Last notes) in CSV export when option \"All columns\" is selected ", "description": "", "done_ratio": 0, "created_on": "2020-03-29T13:24:01Z", "updated_on": "2021-03-28T17:53:04Z"}, {"id": 33210, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 25, "name": "Website (redmine.org)"}, "subject": "Add \"Filters\" category to redmine.org", "description": "Please create a new category named \"Filters\" where we can track changes applied to the default query mechanism which is now available for Projects, Issues and Spent time. ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-29T13:23:39Z", "updated_on": "2020-04-21T09:42:20Z"}, {"id": 33207, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 8, "name": "Administration"}, "subject": "Quickly launch Redmine trial environment with Docker", "description": "This patch adds a Dockerfile to allow people who download Redmine to quickly launch the Redmine trial environment. If the user has already installed Docker, you can start Redmine with just two commands after extracting the source code of Redmine.\r\n\r\nProviding an easy way to launch Redmine with Docker can lower the hurdle to try out Redmine for people who are not familiar with Redmine.\r\n\r\nCurrently, Docker is widely used to quickly prepare an environment to use applications. Not a few people are using Docker on a daily basis, so I think this patch will benefit a lot of people.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-29T08:47:17Z", "updated_on": "2020-09-26T07:35:34Z"}, {"id": 33188, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 27561, "name": "Josef H"}, "category": {"id": 19, "name": "Attachments"}, "subject": "Migration to Active Storage as standard for attachments in Rails", "description": "Because of migration to Rails 6 and because ActiveStorage is now a very solid standard for file storage, it would be very nice to migrate current file management to ActiveStorage.\r\n\r\nIt ought to be mentioned that Active Storage supports also all major cloud storages like S3.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-23T20:06:43Z", "updated_on": "2020-03-23T20:06:43Z"}, {"id": 33181, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "subject": "IssuesSystemTest#test_index_as_csv_should_reflect_sort fails", "description": "IssuesSystemTest#test_index_as_csv_should_reflect_sort fails in trunk or 4.1-stable.\r\n\r\n\r\n\r\n$ bin/rails test test/system/issues_test.rb\r\nRun options: --seed 47671\r\n\r\n# Running:\r\n\r\nCapybara starting Puma...\r\n* Version 3.12.2 , codename: Llamas in Pajamas\r\n* Min threads: 0, max threads: 4\r\n* Listening on tcp://127.0.0.1:57898\r\n[Screenshot]: tmp/screenshots/failures_test_index_as_csv_should_reflect_sort.png\r\nF\r\n\r\nFailure:\r\nIssuesSystemTest#test_index_as_csv_should_reflect_sort [/Users/maeda/redmines/4.1-stable/test/system/issues_test.rb:365]:\r\n--- expected\r\n+++ actual\r\n@@ -1 +1 @@\r\n-[\"Add ingredients categories\", \"Blocked Issue\", \"Cannot print recipes\", \"Error 281 when updating a recipe\", \"Issue Doing the Blocking\", \"Issue due today\", \"Issue of a private subproject\", \"Private issue on public project\", \"Subproject issue\", \"Subproject issue two\", \"Subtask\", \"The quick brown fox jumps over the lazy dog\", \"test\"]\r\n+[\"test\", \"Subtask\", \"The quick brown fox jumps over the lazy dog\", \"Private issue on public project\", \"Issue Doing the Blocking\", \"Blocked Issue\", \"Issue due today\", \"Add ingredients categories\", \"Subproject issue two\", \"Issue of a private subproject\", \"Subproject issue\", \"Error 281 when updating a recipe\", \"Cannot print recipes\"]\r\n\r\n\r\n\r\nbin/rails test test/system/issues_test.rb:351\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-03-22T05:23:55Z", "updated_on": "2020-09-25T01:19:51Z"}, {"id": 33172, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 400957, "name": "Philip Dalrymple"}, "category": {"id": 2, "name": "Issues"}, "subject": "Add admin settable version statuses.", "description": "There are a number of issued (some very old) requesting a status be added to versions.\r\n\r\nIt would be better to have the statuses for version be settable by the admins for a \r\nRedmine server like the statuses for issues or as an Enumeration.\r\n\r\nThis would allow us to have more than one open status for versions for my usage the\r\nstatuses I would have would be (I think)\r\n\r\n* Future \u2014 Open but not a version we are working on. \r\n* Current \u2014 Open and the Current version we are working on.\r\n* Released \u2014 Closed but a supported release.\r\n* History \u2014 Closed in a no longer supported release.\r\n\r\nWe don't have the idea of a Locked release but of course other do.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-18T13:31:38Z", "updated_on": "2020-09-13T02:32:03Z"}, {"id": 33153, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 10, "name": "UI"}, "subject": "UI feature to quickly change issue status", "description": "One of the most often action when working with issues is to change the issue status and in the current UI, depending on the context, you can do this in two ways:\r\n1. Using the context menu wherever the issues are listed (Issues, My Page, Subtasks, Related issues, etc).\r\n2. Using \"Edit\" button from the issue page.\r\n\r\nFrom my experience, the second option is generally used because the normal flow is to open first the issue and then change the status. In a very simple scenario, this action requires at least 4 clicks: click Edit to open edit form, click to open Status dropdown, click to select the new status and then click Submit.\r\n\r\nThe scope of this feature is to discuss and find a better UI feature to allow users to change the issue status with less clicks and using a method that is focused on the issue transition, not a general Edit mode which can be quite overwhelming for some users (#3143 is caused by the same \"Edit\" mode and it's a long requested feature).\r\n\r\nI thought at three approaches:\r\n\r\n1. Buttons for each available status displayed under the issue subject:\r\n!{border: 1px solid grey; width: 80%;}status_buttons.png!\r\n\r\n2. New button \"Change status\" in the contextual area:\r\n!{border: 1px solid grey; width: 80%;}change_status_button.png!\r\n\r\n3. Display the issue status as a custom dropdown and on click, show the dropdown with the available statuses:\r\n!{border: 1px solid grey; width: 80%;}status_dropdown.png!\r\n\r\n4. Based on #33254, as a badge dropwdown:\r\n!{width: 50%; border: 1px solid grey;}.dropdown_badge.png!\r\n\r\nIn a first iteration, clicking on the issue status will work in the same way as clicking on the new status from the context menu where the issue edit form is displayed in case of any validation error. In the future, this new \"UI feature\" can be develop in order to allow users to fill in the mandatory fields or to add a note before submitting the issue.\r\n\r\nBased on the current UI, I think the second option with the \"Change status\" icon is more appropriate. Any feedback is welcome!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-15T23:43:20Z", "updated_on": "2021-05-11T09:13:09Z"}, {"id": 33151, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 448033, "name": "Rasmus Eneman"}, "category": {"id": 32, "name": "REST API"}, "subject": "Provide status for issue children via REST API", "description": "When the children to an issue is requested with `/issue/1.json?include=children` they are returned in the format:\r\n\r\n\r\n{\r\n children: Array<{\r\n id: number\r\n tracker: {\r\n id: number\r\n name: string\r\n }\r\n subject: string\r\n }>,\r\n ...\r\n}\r\n \r\n\r\nIt would be very nice if also the status where returned, like so:\r\n\r\n\r\n{\r\n children: Array<{\r\n id: number\r\n tracker: {\r\n id: number\r\n name: string\r\n }\r\n status: {\r\n id: number\r\n name: string\r\n }\r\n subject: string\r\n }>,\r\n ...\r\n}\r\n \r\n\r\nWhen displaying an overview of a parent issue it's often very helpful to be able to show the status of all child issues.\r\n\r\nThis can be worked around by sending an extra request like `/issues.json?issue_id=2,3,4` for all child issues, but it feels wasteful and unnecessarily cumbersome for what I assume would be a quite common use case.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-15T14:09:56Z", "updated_on": "2020-04-01T15:53:20Z"}, {"id": 33148, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "application stuck if query with filter \"Issue\" and with large amount of IssueIDs", "description": "Project -> Issue,\r\nAdd filter \"Issue\", operator \"Is\", value: please input a lot of IDs, such as 1,2,3,4,5,6,7.\r\nIf the amount of the IDs is too large (in my case, more than 200 IDs), the query is stuck, and there is not SIGQUIT signal sent to webserver to terminal the request.\r\nThe webserver will keep waiting for the application to response the request, passenger-status shows the CPU usages of the redmine process is 100%.\r\nAt this point, the webserver process can not response for further requests.\r\nIf you continue retry the query for more times to make all webserver process are occupied, all users can not use the webserver (always loading).\r\n\r\nPlease set the timeout for requests.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2020-03-13T16:44:15Z", "updated_on": "2020-04-08T08:01:05Z"}, {"id": 33139, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 448528, "name": "Dominik Bittl"}, "category": {"id": 46, "name": "SCM extra"}, "subject": "Redmine.pm not working with socks", "description": "Hello,\r\n\r\nI need to use authentication with Redmine.pm and mysql_sock.\r\n\r\nSetting used in Apache config:\r\n\r\nRedmineDSN \"DBI:mysql:database=xxx;mysql_socket=/tmp/proxysql.sock\"\r\nRedmineDbUser \"user\"\r\nRedmineDbPass \"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\"\r\n\r\nApache error.log message:\r\n\r\nDBI connect('database=XXX;mysql_socket=/tmp/proxysql.sock','user',...) failed: Can't connect to local MySQL server through socket '/tmp/proxysql.sock' (2) at /usr/share/perl5/Apache/Redmine.pm line 557.\r\n\r\n\r\nMy own little perl-script with same options und also using DBI is functional via socket also the redmine database config with sock works.\r\n\r\n\r\nSystem:\r\n\r\nUbuntu 18.04.4 LTS\r\nPerl v5.26.1\r\n\r\n#perl -V\r\nSummary of my perl5 (revision 5 version 26 subversion 1) configuration:\r\n\r\nPlatform:\r\nosname=linux\r\nosvers=4.9.0\r\narchname=x86_64-linux-gnu-thread-multi\r\nuname='linux localhost 4.9.0 #1 smp debian 4.9.0 x86_64 gnulinux '\r\nconfig_args='-Dusethreads -Duselargefiles -Dcc=x86_64-linux-gnu-gcc -Dcpp=x86_64-linux-gnu-cpp -Dld=x86_64-linux-gnu-gcc -Dccflags=-DDEBIAN -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/perl-hx1dVS/perl-5.26.1=. -fstack-protector-strong -Wformat -Werror=format-security -Dldflags= -Wl,-Bsymbolic-functions -Wl,-z,relro -Dlddlflags=-shared -Wl,-Bsymbolic-functions -Wl,-z,relro -Dcccdlflags=-fPIC -Darchname=x86_64-linux-gnu -Dprefix=/usr -Dprivlib=/usr/share/perl/5.26 -Darchlib=/usr/lib/x86_64-linux-gnu/perl/5.26 -Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5 -Dvendorarch=/usr/lib/x86_64-linux-gnu/perl5/5.26 -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl/5.26.1 -Dsitearch=/usr/local/lib/x86_64-linux-gnu/perl/5.26.1 -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Dsiteman3dir=/usr/local/man/man3 -Duse64bitint -Dman1ext=1 -Dman3ext=3perl -Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Ud_ualarm -Uusesfio -Uusenm -Ui_libutil -Ui_xlocale -Uversiononly -DDEBUGGING=-g -Doptimize=-O2 -dEs -Duseshrplib -Dlibperl=libperl.so.5.26.1'\r\n\r\n#dpkg -l |grep apache\r\nii apache2 2.4.29-1ubuntu4.12 amd64 Apache HTTP Server\r\nii apache2-bin 2.4.29-1ubuntu4.12 amd64 Apache HTTP Server (modules and other binary files)\r\nii apache2-data 2.4.29-1ubuntu4.12 all Apache HTTP Server (common files)\r\nii apache2-utils 2.4.29-1ubuntu4.12 amd64 Apache HTTP Server (utility programs for web servers)\r\nii libapache-dbi-perl 1.12-1 all interface connecting apache server to database via perl's DBI\r\nii libapache2-mod-perl2 2.0.10-2ubuntu3.18.04.1 amd64 Integration of perl with the Apache2 web server\r\nrc libapache2-mod-shib2 2.6.1+dfsg1-2 amd64 Federated web single sign-on system (Apache module)\r\nii libapache2-mod-svn 1.9.7-4ubuntu1 amd64 Apache Subversion server modules for Apache httpd\r\nii libapache2-reload-perl 0.13-1 all module for reloading Perl modules when changed on disk\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "134"}], "created_on": "2020-03-12T12:33:40Z", "updated_on": "2020-05-19T11:40:59Z"}, {"id": 33138, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 448528, "name": "Dominik Bittl"}, "category": {"id": 46, "name": "SCM extra"}, "subject": "Apache crashes with Redmine.pm and RedmineCacheCredsMax active", "description": "Hello,\r\n\r\nissue as described in the topic.\r\n\r\nThe Apache keeps crashing with Redmine.pm when RedmineCacheCredsMax is set.\r\n\r\n- What infos do you need further? Is there a way to debug this?\r\n\r\n\r\nSystem:\r\n\r\nUbuntu 18.04.4 LTS\r\nPerl v5.26.1\r\n\r\n\r\n#perl -V \r\nSummary of my perl5 (revision 5 version 26 subversion 1) configuration:\r\n\r\n Platform:\r\n osname=linux\r\n osvers=4.9.0\r\n archname=x86_64-linux-gnu-thread-multi\r\n uname='linux localhost 4.9.0 #1 smp debian 4.9.0 x86_64 gnulinux '\r\n config_args='-Dusethreads -Duselargefiles -Dcc=x86_64-linux-gnu-gcc -Dcpp=x86_64-linux-gnu-cpp -Dld=x86_64-linux-gnu-gcc -Dccflags=-DDEBIAN -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/perl-hx1dVS/perl-5.26.1=. -fstack-protector-strong -Wformat -Werror=format-security -Dldflags= -Wl,-Bsymbolic-functions -Wl,-z,relro -Dlddlflags=-shared -Wl,-Bsymbolic-functions -Wl,-z,relro -Dcccdlflags=-fPIC -Darchname=x86_64-linux-gnu -Dprefix=/usr -Dprivlib=/usr/share/perl/5.26 -Darchlib=/usr/lib/x86_64-linux-gnu/perl/5.26 -Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5 -Dvendorarch=/usr/lib/x86_64-linux-gnu/perl5/5.26 -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl/5.26.1 -Dsitearch=/usr/local/lib/x86_64-linux-gnu/perl/5.26.1 -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Dsiteman3dir=/usr/local/man/man3 -Duse64bitint -Dman1ext=1 -Dman3ext=3perl -Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Ud_ualarm -Uusesfio -Uusenm -Ui_libutil -Ui_xlocale -Uversiononly -DDEBUGGING=-g -Doptimize=-O2 -dEs -Duseshrplib -Dlibperl=libperl.so.5.26.1'\r\n \r\n\r\n\r\n#dpkg -l |grep apache\r\nii apache2 2.4.29-1ubuntu4.12 amd64 Apache HTTP Server\r\nii apache2-bin 2.4.29-1ubuntu4.12 amd64 Apache HTTP Server (modules and other binary files)\r\nii apache2-data 2.4.29-1ubuntu4.12 all Apache HTTP Server (common files)\r\nii apache2-utils 2.4.29-1ubuntu4.12 amd64 Apache HTTP Server (utility programs for web servers)\r\nii libapache-dbi-perl 1.12-1 all interface connecting apache server to database via perl's DBI\r\nii libapache2-mod-perl2 2.0.10-2ubuntu3.18.04.1 amd64 Integration of perl with the Apache2 web server\r\nrc libapache2-mod-shib2 2.6.1+dfsg1-2 amd64 Federated web single sign-on system (Apache module)\r\nii libapache2-mod-svn 1.9.7-4ubuntu1 amd64 Apache Subversion server modules for Apache httpd\r\nii libapache2-reload-perl 0.13-1 all module for reloading Perl modules when changed on disk\r\n \r\n\r\n\r\nvhost:\r\n [...]\r\n \r\n PerlLoadModule Apache::Redmine\r\n SVNCompressionLevel 0\r\n \r\n \r\n Require valid-user\r\n \r\n\r\n \r\n Require method GET PROPFIND OPTIONS REPORT HEAD POST\r\n \r\n Require ip XXXX\r\n Require env AllowIP\r\n \r\n \r\n \r\n\r\n \r\n\r\n\r\n #limit max size to 400MB\r\n LimitRequestBody 424288000\r\n LimitXMLRequestBody 8000000\r\n\r\n ## for mysql\r\n RedmineDSN \"DBI:mysql:database=XXX;host=XXX;port=XXXX\"\r\n RedmineDbUser \"XXXX\"\r\n RedmineDbPass \"XXXXXXXXXXXXXXXXXXXXXXXXXXX\"\r\n\r\n #Cache the last 50 auth entries\r\n RedmineCacheCredsMax 500\r\n \r\n[...]\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "134"}], "created_on": "2020-03-12T12:24:20Z", "updated_on": "2020-05-19T11:42:32Z"}, {"id": 33129, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 10, "name": "UI"}, "subject": "Restore \"Latest Projects\" to Home page", "description": "In the earlier versions of Redmine, \"Latest projects\" box was placed on the Home page. It showed recently created 5 projects and users can quickly access projects from there.\r\n\r\nHowever, the box was removed in Redmine 3.2.0 (#21148) because the project list that shows projects regardless of frequency of use is quite useless.\r\n\r\nIn Redmine 4.1, the \"Recently used projects\" feature has been implemented for the project selector (#31355). It is useful if the \"Latest projects\" box is restored and recently used projects are shown in the box. You can go to the projects you use frequently with fewer clicks. I think it improves usability.\r\n\r\nThe following screenshot is the Home page of Redmine 3.1. The \"Latest projects\" box shows recently created projects.\r\n\r\n!{width: 1024px; border: 1px solid grey;}.latest-projects.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-11T14:20:42Z", "updated_on": "2020-03-11T14:20:42Z"}, {"id": 33118, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 90398, "name": "Anthony Mallet"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Detect plain diffs in e-mail submitted issues and map to attachments", "description": "Diffs sent as plain/text message (as with git format-patch + git send-email) in\r\nissues tend to be textilized, which messes up the display. Also, the original\r\npatch file is not easily downloadable for processing.\r\n\r\nWith this patch, when a diff file is detected in a plain text message without\r\nattachment, the whole e-mail message is converted into a proper attachment\r\n(that is suitable for git am) and only the diff comment is stored in the\r\nissue description.\r\n\r\nThe diff detection is based on the following heuristics:\r\n- body contains three consecutive lines starting with \"---\", \"+++\" and \"@@\"\r\n- and body contains a line starting with \"---\", \"diff -\" or \"Index: \"\r\n\r\nThe message body is split before this detected separator.", "done_ratio": 0, "created_on": "2020-03-10T10:21:26Z", "updated_on": "2020-09-13T03:08:58Z"}, {"id": 33117, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 7, "name": "Accounts / authentication"}, "subject": "Redirect to users_path instead of edit_user_path in order to avoid confusion", "description": "Currently, a user is redirected to @edit_user_path@ (/users/*/edit) after creating a user. However, I think it is better to be redirected to @user_path@ (/users) for the following reasons:\r\n\r\n* Inconsistent. There are some exceptions but most forms in Admin page shows index page after an object is created\r\n* Confusing. Today I observed that an admin mistakenly rewrote the user that has just created. It is because they misunderstood that the form is /users/new, but it was actually /users/*/edit\r\n* I cannot find any use cases that showing @edit_user_path@ is better than @users_path@\r\n\r\n\r\ndiff --git a/app/controllers/users_controller.rb b/app/controllers/users_controller.rb\r\nindex 2fb297874..d3e853b43 100644\r\n--- a/app/controllers/users_controller.rb\r\n+++ b/app/controllers/users_controller.rb\r\n@@ -122,7 +122,7 @@ class UsersController < ApplicationController\r\n attrs = {:generate_password => @user.generate_password }\r\n redirect_to new_user_path(:user => attrs)\r\n else\r\n- redirect_to edit_user_path(@user)\r\n+ redirect_to users_path\r\n end\r\n }\r\n format.api { render :action => 'show', :status => :created, :location => user_url(@user) }\r\n\r\n$ bin/rails test test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb\r\nRun options: --seed 12509\r\n\r\n# Running:\r\n\r\nE\r\n\r\nError:\r\nMercurialAdapterTest#test_tags:\r\nRedmine::Scm::Adapters::MercurialAdapter::HgCommandAborted: hg exited with non-zero status: 255\r\n lib/redmine/scm/adapters/mercurial_adapter.rb:327:in `hg'\r\n lib/redmine/scm/adapters/mercurial_adapter.rb:133:in `summary'\r\n lib/redmine/scm/adapters/mercurial_adapter.rb:101:in `tags'\r\n test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:322:in `test_tags'\r\n\r\n\r\nbin/rails test test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:321\r\n\r\n..E\r\n\r\nError:\r\nMercurialAdapterTest#test_diff_made_by_revision:\r\nNoMethodError: undefined method `size' for nil:NilClass\r\n test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:161:in `block in test_diff_made_by_revision'\r\n test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:159:in `each'\r\n test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:159:in `test_diff_made_by_revision'\r\n\r\n\r\nbin/rails test test/unit/lib/redmine/scm/adapters/mercurial_adapter_test.rb:157\r\n.\r\n.\r\n.\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2020-03-07T01:40:39Z", "updated_on": "2020-03-07T06:25:42Z"}, {"id": 33101, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "\"<=\", \">=\", and \"between\" operator for priority filter", "description": "Currently, the priority issues filter supports only \"is\" and \"is not\" operator.\r\n\r\nI think the filter will be more useful if it has \"<=\" (less than), \">=\" (larger than), and \"between\" operators like numeric fields.\r\n\r\nUse cases:\r\n* \"Priority\", \">=\", \"Normal\" : Lists issues whose priority is normal or higher. It filters out issues with lower priority\r\n* \"Priority\", \"between\", \"High\", \"Immediate\": Lists issues that has higher priority value", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-06T00:58:11Z", "updated_on": "2020-03-06T00:58:11Z"}, {"id": 33097, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 400484, "name": "David Dole\u017eal"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Feedback about email delivery", "description": "Hi, \r\ncan anybody solved problem, when you need to know, if email notification succesfully arrive? \r\n\r\nI use Redmine 3.4.x and notification via exchange e-mail. We had 3-times error with succesful delivery. I fix it wit \" or ' in config file and it seems ok now. But I would like to log/check tool or something.\r\n\r\nThank you for reply.\r\n\r\nDavid", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-04T17:14:44Z", "updated_on": "2021-04-14T13:58:01Z"}, {"id": 33088, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 447098, "name": "Takeshi SUGIYAMA"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Should User.notify_about?(issue) consider the issue being wathced by the user?", "description": "In app/models/user.rb line 790, notify_about?(object) is defined.\r\nIn app/models/issue.rb line 1037 notified_users method's comment explains\r\n\r\n # Author and assignee are always notified unless they have been\r\n # locked or don't want to be notified\r\n \r\n\r\nMy question is, should User.notify_about?(issue) checke the passed issue being wathced by the user or not?\r\nIf it should, I would like to know whether notify_about?(object) can take into account the issue being watched or not according to the user's notification prefernces?\r\n\r\nKind attention will be appreciated.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-03-03T11:11:54Z", "updated_on": "2020-03-09T02:04:13Z"}, {"id": 33079, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 204091, "name": "Kevin Fischer"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Remove unused argument from Redmine::Helpers::TimeReport", "description": "The issue argument is never used and in that particular controller action @issue is not even set to any value.", "done_ratio": 0, "created_on": "2020-03-03T00:48:07Z", "updated_on": "2020-03-07T22:46:38Z"}, {"id": 33074, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 58883, "name": "Jaebok Oh"}, "category": {"id": 12, "name": "Translations"}, "subject": "Korean translation update for 4.1-stable", "description": "This is a Korean translation file for 4.1.0\r\nI modified some strange things together in the previous file.", "done_ratio": 0, "created_on": "2020-03-02T00:52:20Z", "updated_on": "2020-03-10T13:07:00Z"}, {"id": 33073, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 12098, "name": "Martin Cizek"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Macro argument escaping/quoting mechanism", "description": "Currently there is no way to enter a macro argument including e.g. comma (@,@), which is always treated as an argument separator - see source:trunk/lib/redmine/wiki_formatting/macros.rb#L41. This effectively prevents using e.g. the @thumbnail@ macro for some images when renaming attachments is not an option. We'll be happy to submit a patch once there is some agreement on how to approach this.\r\n\r\n*Suggestion*:\r\n* Allow double quotes for argument value delimiting.\r\n* No quotes = old behavior.\r\n* Special characters within quotes can be encoded as HTML entities (similarly to @name=\"value\"@ HTML element attributes).\r\n\r\nMakes sense?\r\n\r\nRationale:\r\n* @!@ turns off Redmine-interpreted text formatting constructs - but probably not suitable within the constructs.\r\n* [[RedmineTextFormattingTextile|Text formatting docs]] say e.g. _double quotes can be used when version name contains spaces_\r\n* Users tend to use double quotes anyway, e.g. @{{thumbnail(foo.jpg, title=\"Foo Bar\")}}@ and they hardly realize that the quotes actually become part of the argument value.\r\n* When I have a version called @My \"Version\"@, I can refer to it as @version:\"My "Version"\"@ within Textile. Does not work with Markdown though.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-03-01T11:12:37Z", "updated_on": "2020-03-01T11:12:37Z"}, {"id": 33071, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 8, "name": "Reopened"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Prevent accidental deletion of contents with sudo mode", "description": "The attached patch adds protection against deletion of contents such as issues, wiki pages, and attachments by expanding operations covered by sudo mode that has been added in Redmine 3.1 (#19851).\r\n\r\nUsers sometimes mistakenly delete contents like issues. I think it is because deleting contents is so easy if they have appropriate permissions.\r\n\r\nI think such accidents can be reduced with sudo mode. If sudo mode guards deletion of contents as well by requiring re-entering a password, users can have an opportunity to reconsider the operation.\r\n\r\n*Step 1: the user see \"Are you sure?\" dialog after clicking \"Delete\" button. Not a few users press OK without thinking.*\r\n!{border: 1px solid grey; width: 1024px;}.deletion-step-1@2x.png!\r\n\r\n*Step 2: if sudo mode is enabled in configuration.yml and the attached patch is applied, Redmine requires user to re-enter their password before performing deletion. The user may notice that they are doing a daingerous operation.*\r\n!{border: 1px solid grey; width: 1024px;}.deletion-step-2@2x.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Fixed"}], "created_on": "2020-03-01T09:16:24Z", "updated_on": "2021-01-06T03:39:59Z", "closed_on": "2020-03-10T03:27:25Z"}, {"id": 33056, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 444925, "name": "Anestis Kozakis"}, "category": {"id": 10, "name": "UI"}, "subject": "Dark Mode setting (per user)", "description": "It would be nice for a user to be able to set a \"Dark Mode\" for the Redmine UI.\r\n\r\nThis would allow people who prefer working with darker colours or have light-sensitivity issues to be able to use Redmine without any issues.\r\n\r\nMany apps and mobile devices offer Dark Mode as a standard per-user setting.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-26T22:12:58Z", "updated_on": "2020-03-26T10:21:40Z"}, {"id": 33037, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 403349, "name": "Hans Riekehof"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Support for Gitlab flavored Markdown ", "description": "Its great to see that Redmine also supports markdown in the meantime. However in the current version 4.1 the Markdown Features are quite limited.\r\nIts missing some basics things like scaling pictures, and some more advanced things like ```math blocks which would render inline Latex.\r\n\r\nIt would be great if Redmine would include something like \"kramdown\":https://kramdown.gettalong.org/documentation.html or \"GitLab Flavored Markdown\":https://gitlab.com/gitlab-org/gitlab-markup\r\n\r\nWould this be possible to include ? Both projects are already available as ruby gems. That fits good. \r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-21T08:34:11Z", "updated_on": "2020-05-02T14:19:54Z"}, {"id": 33029, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 445323, "name": "casper nielsen"}, "category": {"id": 32, "name": "REST API"}, "subject": "API POST requests fail with 422 Can't verify CSRF token authenticity. on 3.4.13, 4.0.6 and 4.1.0", "description": "I have been tasked with making our main application work with a newer version of redmine than it did before.\r\nThe old one was ancient. Our current one is 3.4.13 in a docker container.\r\n\r\n\r\nI have tried the latest three versions localhost. The behave the same in this regard:\r\nWhen I make POST requests using HTTParty or even curl, I get a 422 response code with the message \"Can't verify CSRF token authenticity\"\r\nThis is my request:\r\n\r\n HTTParty.post(\r\n \"http://localhost:3000/issues.json&key=665f63b1c6a66a3a103207c59241ea9aefbe87c4\",\r\n timeout: @options[:timeout],\r\n headers: {'Content-Type' => 'application/json'}, \r\n body: somehash.to_json\r\n )\r\n\r\nIn the redmine source code ApplicationController it calls protect_from_forgery. I don't see any exceptions on this like I would expect with api-requests.\r\nI thought CSRF protection was only meant for posted forms and the like. I may be wrong on that. How would I know what to send as a CSRF-token when making api-requests without prior requests? \r\nI read the API reference. I didn't see anything on the matter. \r\n\r\nWhat am I missing?\r\n\r\n\r\n\r\nAnother thing:\r\nI have tried putting the key in the body with the json key \"key\" and as a header with the key name 'X-Redmine-API-Key' like specified. None of those are accepted it seems.\r\nI can only make it accept the key if passed as a query parameter for some reason.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-02-20T08:23:26Z", "updated_on": "2020-03-04T06:27:26Z"}, {"id": 33025, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Optional email headers", "description": "Now 8 years later, this feature #5643 is in some cases seen by vulnerability that exposes unnecessary information.\r\n\r\nIt would be preferable to have a checkbox to completely turn-off Redmine headers.\r\n\r\nThis should probably be a patch I can create it later some time if I catch some time.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-19T10:38:19Z", "updated_on": "2020-02-19T10:39:56Z"}, {"id": 33023, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 334746, "name": "taca tadocolo"}, "category": {"id": 19, "name": "Attachments"}, "subject": "Warning occurs when displaying a few exceptional PDF thumbnail", "description": "A PDF thumbnail is displayed, but the following message is output to STDERR.\r\nThe PDF file cannot be published, but it was created with a fax image (binary image).\r\n\r\n\r\nconvert.exe: profile 'icc': 'RGB ': RGB color space not permitted on grayscale PNG `redmine_root/tmp/thumbnails/***.thumb' @ warning/png.c/MagickPNGWarningHandler/1668.\r\n \r\n\r\nThe warning disappeared after applying the following patch.\r\n\r\n\r\n--- a\\lib\\redmine\\thumbnail.rb\r\n+++ b\\lib\\redmine\\thumbnail.rb\r\n@@ -48,7 +48,7 @@\r\n size_option = \"#{size}x#{size}>\"\r\n \r\n if is_pdf\r\n- cmd = \"#{shell_quote CONVERT_BIN} #{shell_quote \"#{source}[0]\"} -thumbnail #{shell_quote size_option} #{shell_quote \"png:#{target}\"}\"\r\n+ cmd = \"#{shell_quote CONVERT_BIN} #{shell_quote \"#{source}[0]\"} -thumbnail #{shell_quote size_option} +profile icc #{shell_quote \"png:#{target}\"}\"\r\n else\r\n cmd = \"#{shell_quote CONVERT_BIN} #{shell_quote source} -auto-orient -thumbnail #{shell_quote size_option} #{shell_quote target}\"\r\n end\r\n\r\nEnvironment:\r\n Redmine version 4.0.5.stable\r\n Ruby version 2.7.0-p0 (2019-12-25) [x86_64-linux]\r\n Rails version 5.2.3\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery sendmail\r\nSCM:\r\n Git 2.25.1\r\n Filesystem \r\nRedmine plugins:\r\n redmine_messenger 1.0.6\r\n \r\n\r\n\r\nApp 244788 output: Started GET \"/tracker/projects/(PROJECT)/repository\" for (IP-ADDRESS) at 2020-02-18 11:18:50 -0500 \r\nApp 244788 output: Processing by RepositoriesController#show as HTML \r\nApp 244788 output: Parameters: {\"id\"=>\"(LOCAL_USER)\"} \r\nApp 244788 output: Current user: (REDMINE_USER) (id=5) \r\nApp 244788 output: Completed 500 Internal Server Error in 30ms (ActiveRecord: 7.6ms) \r\nApp 244788 output: \r\nApp 244788 output: FrozenError (can't modify frozen String: \"\"): \r\nApp 244788 output: \r\nApp 244788 output: lib/redmine/scm/adapters/abstract_adapter.rb:279:in `force_encoding'\r\nApp 244788 output: lib/redmine/scm/adapters/abstract_adapter.rb:279:in `scm_iconv'\r\nApp 244788 output: lib/redmine/scm/adapters/git_adapter.rb:136:in `entries'\r\nApp 244788 output: app/models/repository/git.rb:98:in `scm_entries'\r\nApp 244788 output: app/models/repository.rb:204:in `entries'\r\nApp 244788 output: app/controllers/repositories_controller.rb:86:in `show'\r\nApp 244788 output: lib/redmine/sudo_mode.rb:63:in `sudo_mode'\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "153"}], "created_on": "2020-02-18T19:45:02Z", "updated_on": "2020-08-05T22:44:54Z"}, {"id": 33018, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Add an ability to attach and embed a file to \"Image\" button in the Wiki toolbar", "description": "Currently, we have \"Image\" button in the Wiki toolbar. I think the button would be more useful and user-friendly if the button has an ability to attach a file.\r\n\r\nThe following is my idea of the new behavior.\r\n\r\n*1. You will see a file dialog if you click the \"Image\" button. You can open an image to embed with the dialog*\r\n!{width: 942px; border: 1px solid grey;}.step-1-open-a-file-with-dialog.png!\r\n\r\n*2. After opening an image with the dialog, the selected image file is attached and inserted to the textarea with markups*\r\n!{width: 542px; border: 1px solid grey;}.step-2-file-is-embedded.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-18T07:04:32Z", "updated_on": "2020-05-04T20:49:38Z"}, {"id": 33017, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 308290, "name": "Bernhard Rohloff"}, "category": {"id": 24, "name": "Documentation"}, "subject": "Complete documentation of news REST API", "description": "The documentation of the news API shows only the GET part. The API has been completed in #13468 and the other parts should be added to the documentation, as well.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-18T05:11:14Z", "updated_on": "2020-02-18T05:11:14Z"}, {"id": 33016, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 444925, "name": "Anestis Kozakis"}, "category": {"id": 6, "name": "News"}, "subject": "Adding Watchers to a News Item", "description": "At my work we feel it is a bit backwards to ask people to subscribe to a News item after it is published.\r\n\r\nIt would be more efficient if, instead, the writer of the News item could add people or a group to a News Item so they are automatically subscribed to the News item, and are also notified that a new News item has been posted, as well as to any updates posted on that News item.\r\n\r\nThis would work in the same way that adding Watchers to Issues works.\r\n\r\nI'm sure other people have had similar ideas or suggestions. I did search but couldn't find anything, as most results centred around Issues instead of News.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-18T04:23:38Z", "updated_on": "2021-04-07T08:00:42Z"}, {"id": 32985, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 388654, "name": "Ko Nagase"}, "category": {"id": 58, "name": "Issues list"}, "subject": "Garbage collection issue when exporting huge CSV", "description": "I set \"10000\" as \"Issues export limit\" (instead of default \"500\") for some reasons,\r\nbut I noticed that exporting around 10,000 issues CSV causes out of memory issue.\r\n\r\nI thought that the cause is inside some plugins, but it seems to be happen without any plugins,\r\nand after changing the following Issues Controller part, the memory usage seems to become stable (no memory leak).\r\n\r\ndiff --git a/app/controllers/issues_controller.rb b/app/controllers/issues_controller.rb\r\nindex 69a947b03..6596df30c 100644\r\n--- a/app/controllers/issues_controller.rb\r\n+++ b/app/controllers/issues_controller.rb\r\n@@ -63,8 +63,8 @@ class IssuesController < ApplicationController\r\n render_feed(@issues, :title => \"#{@project || Setting.app_title}: #{l(:label_issue_plural)}\")\r\n }\r\n format.csv {\r\n- @issues = @query.issues(:limit => Setting.issues_export_limit.to_i)\r\n- send_data(query_to_csv(@issues, @query, params[:csv]), :type => 'text/csv; header=present', :filename => 'issues.csv')\r\n+ tmp_issues = @query.issues(:limit => Setting.issues_export_limit.to_i)\r\n+ send_data(query_to_csv(tmp_issues, @query, params[:csv]), :type => 'text/csv; header=present', :filename => 'issues.csv')\r\n }\r\n format.pdf {\r\n @issues = @query.issues(:limit => Setting.issues_export_limit.to_i)\r\n\r\nDEPRECATION WARNING: Initialization autoloaded the constants ActiveRecord::Acts,\r\n ActiveRecord::Acts::Tree, Redmine::I18n, Redmine::Helpers, Redmine::Helpers::URL\r\n, Redmine::SafeAttributes, Redmine::SubclassFactory, CustomField, Redmine::Utils,\r\n Redmine::Configuration, Redmine::Scm::Adapters::CommandFailed, IssueRelation,\r\n Redmine::WikiFormatting::Macros, Redmine::Pagination, Redmine::SudoMode, ApplicationHelper\r\n, Redmine::WikiFormatting::Textile, Redmine::WikiFormatting::Textile::Formatter,\r\n Redmine::WikiFormatting::Textile::Helper, Redmine::WikiFormatting::HtmlParser\r\n, Redmine::WikiFormatting::Textile::HtmlParser, Redmine::WikiFormatting::Markdown,\r\n Redmine::WikiFormatting::Markdown::Formatter, Redmine::WikiFormatting::Markdown::HTML,\r\n Redmine::WikiFormatting::Markdown::Helper, Redmine::WikiFormatting::Markdown::HtmlParser,\r\n Redmine::Views::ApiTemplateHandler, and Setting.\r\n\r\nBeing able to do this is deprecated. Autoloading during initialization is going\r\nto be an error condition in future versions of Rails.\r\n\r\nReloading does not reboot the application, and therefore code executed during\r\ninitialization does not run again. So, if you reload ActiveRecord::Acts, for example,\r\nthe expected changes won't be reflected in that stale Module object.\r\n\r\n`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.\r\n\r\nPlease, check the \"Autoloading and Reloading Constants\" guide for solutions.\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-02-03T01:45:23Z", "updated_on": "2021-04-27T07:37:47Z"}, {"id": 32915, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 334746, "name": "taca tadocolo"}, "category": {"id": 34, "name": "Gantt"}, "subject": "Internal Server Error occurted when exporting gantt chart to png on Windows", "description": "Redmine 4.0.4 using RMagick was fine.\r\nHowever, Redmine 4.1.0 using MiniMagick does not work.\r\n\r\nprodution.log of Redmine 4.1.0 is this:\r\n\r\nStarted GET \"/redmine/projects/some_project/issues/gantt.png?...\" for (IP) at (date)\r\nProcessing by GanttsController#show as PNG\r\n Parameters: {...}\r\n Current user: admin (id=1)\r\nCompleted 500 Internal Server Error in 290ms (ActiveRecord: 63.0ms)\r\n \r\nErrno::E2BIG (Arg list too long - convert):\r\n \r\nlib/redmine/helpers/gantt.rb:381:in `to_image'\r\napp/controllers/gantts_controller.rb:44:in `block (2 levels) in show'\r\napp/controllers/gantts_controller.rb:42:in `show'\r\n \r\n\r\nOn Windows, the ImageMagick's \"convert\" command length is too long, and then error occurred.\r\nI want to shorten the command length or split the command if Redmine keeps using Minimagick.\r\nAnd there should be some exception code as below:\r\n\r\n\r\n--- a\\lib\\redmine\\helpers\\gantt.rb\r\n+++ b\\lib\\redmine\\helpers\\gantt.rb\r\n@@ -488,4 +488,15 @@\r\n end\r\n img.to_blob\r\n+ rescue\r\n+ MiniMagick::Tool::Convert.new do |gc|\r\n+ # create error message image\r\n+ gc.size('%dx%d' % [200, 50])\r\n+ gc.xc('white')\r\n+ gc.stroke('transparent').fill('red')\r\n+ # and draw error message\r\n+ gc.draw('text %d,%d %s' % [10, 20, Redmine::Utils::Shell.shell_quote('Gantt size too big.')])\r\n+ gc << img.path\r\n+ end\r\n+ img.to_blob\r\n ensure\r\n img.destroy! if img\r\n\r\n--- a/public/javascripts/application.js\r\n+++ b/public/javascripts/application.js\r\n@@ -998,13 +998,15 @@\r\n \r\n $(function () {\r\n- $('[title]').tooltip({\r\n- show: {\r\n- delay: 400\r\n- },\r\n- position: {\r\n- my: \"center bottom-5\",\r\n- at: \"center top\"\r\n- }\r\n- });\r\n+ if ($('[title]').tooltip !== undefined) {\r\n+ $('[title]').tooltip({\r\n+ show: {\r\n+ delay: 400\r\n+ },\r\n+ position: {\r\n+ my: \"center bottom-5\",\r\n+ at: \"center top\"\r\n+ }\r\n+ });\r\n+ }\r\n });\r\n \r\n\r\n# svn sw ^/branches/4.1-stable\r\n \r\n\r\n\r\n# bundle exec rake db:migrate RAILS_ENV=production\r\nrake aborted!\r\nNoMethodError: undefined method `assets' for #\r\nDid you mean? asset_host\r\n \r\nI removed the comment out of require \"sprockets/railtie\u201d in config/application.rb.\r\n\r\n\r\n# bundle exec rake db:migrate RAILS_ENV=production\r\nrake aborted!\r\nSprockets::Railtie::ManifestNeededError: Expected to find a manifest file in `app/assets/config/manifest.js`\r\nBut did not, please create this file and use it to link any assets that need\r\nto be rendered by your app:\r\n\r\nExample:\r\n //= link_tree ../images\r\n //= link_directory ../javascripts .js\r\n //= link_directory ../stylesheets .css\r\nand restart your server\r\n \r\nI created the file as per the example and ran it again.\r\nProcessing succeeded, Redmine 4.1.0 started successfully.\r\n\r\nenvironment\r\n\r\n# uname -a\r\nLinux yomi-sv01.localdomain 3.10.0-1062.1.2.el7.x86_64 #1 SMP Mon Sep 30 14:19:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux\r\n\r\n# mysql --version\r\nmysql Ver 14.14 Distrib 5.7.29, for Linux (x86_64) using EditLine wrapper\r\n\r\n# ruby bin/about\r\nEnvironment:\r\n Redmine version 4.1.0.stable.19426\r\n Ruby version 2.6.2-p47 (2019-03-13) [x86_64-linux]\r\n Rails version 5.2.4.1\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\n \r\n\r\nI always use Redmine. Thank you!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-01-22T09:12:44Z", "updated_on": "2020-02-05T05:39:45Z"}, {"id": 32847, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 20, "name": "Plugin API"}, "subject": "Ability to add custom css classes to body tag", "description": "This ability is important for plugin developers to avoid unnecessary use of deface gem.\r\n\r\nIf it's going to be implemented, also wiki page for plugin developers should\r\nbe updated, accordingly.\r\n\r\n", "done_ratio": 0, "created_on": "2020-01-21T09:44:45Z", "updated_on": "2020-02-11T15:14:41Z"}, {"id": 32845, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 351306, "name": "Ayami Yasuoka"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "New line codes are not reflected in tables created in textile format.", "description": "Textile format \r\nGET /project/1/issues.?inlude=issue_count\r\n\r\n\r\n\r\n \r\n 1 \r\n \r\n 0.7 \r\n closed \r\n 2008-04-28 \r\n none \r\n 2008-03-09T12:52:06+01:00 \r\n 2009-11-15T12:22:12+01:00 \r\n FooBarWikiPage\r\n 13 \r\n \r\n \r\n \r\n\r\nFilter by issue count :\r\n\r\n// Issue count in greater or equal to 0\r\nGET /project/1/issues.?issue_count=%3E%3D0\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-01-14T10:13:55Z", "updated_on": "2020-01-14T10:13:55Z"}, {"id": 32801, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 94920, "name": "James H"}, "category": {"id": 53, "name": "Performance"}, "subject": "Limit/Filter/Postpone the amount of shown projects and groups that the user is a member of", "description": "Requesting a way of limiting the amount of projects or groups shown in various areas of the application, or postponing the loading of the data due to performance issues.\r\n\r\nCertain users report very slow performance and the user account page for these users loads for a long time and hangs.\r\n\r\n-----\r\n\r\nCertain pages in the app loads a list of projects or groups that the user is a member of.\r\ne.g. \r\n* the main top bar has a \"Jump to a project...\" dropdown that loads all projects that the user is a member of.\r\n* the user's account page has tabs for groups and projects.\r\n\r\nI believe the page loading times and overall performance are affected when a user is a member of thousands of projects/groups.\r\nWould like a way to mitigate this.\r\n\r\nI am not sure what the best way to do this is...\r\nLazy-loading may be a possibility, paginated view that don't load the other pages until clicked, or not loading anything until you press a button to kick it off. \r\nAny solution where being a member of thousands and thousands of projects or groups does not heavily impact performance.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-01-14T00:07:34Z", "updated_on": "2020-01-14T00:12:01Z"}, {"id": 32796, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 67167, "name": "Pierre de LESPINAY"}, "category": {"id": 32, "name": "REST API"}, "subject": "API - Ability to get time entries report", "description": "Since there is already an easy way to get the \"CSV time entries report\":https://www.redmine.org/projects/redmine/wiki/RedmineTimelogReport with an HTTP request, it would be great to be able to get it with a REST request.\r\n\r\nI didn't see a way to do it for now, and I recently posted a \"StackOverflow question\":https://stackoverflow.com/questions/59661630 about it (don't hesitate to suggest any workaround here).\r\n\r\nFor the API request I would suggest to keep the same input parameters and the output format (converted to JSON). Like this:\r\n\r\n\r\nGET /time_entries/report.json?columns=day&criteria%5B%5D=user HTTP/1.1\r\nHost: my.redmine.eu\r\nAccept: application/json\r\nX-Redmine-API-Key: 07awf6s549b6s5b70s54679s45v\r\n \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-01-13T08:21:10Z", "updated_on": "2020-01-13T08:21:10Z"}, {"id": 32773, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 32682, "name": "Valdir Stiebe Junior"}, "category": {"id": 11, "name": "Projects"}, "subject": "Filter for showing subproject childrens on Projects page", "description": "On the filter system created on #29482 it would be helpful to have a filter similar to _Subproject of_ but with all children subprojects on the result.\r\nOr an option to bring all subprojects in the results.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-01-08T12:59:15Z", "updated_on": "2020-01-08T12:59:15Z"}, {"id": 32770, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 115781, "name": "Sebastian Paluch"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Text formating on Redmine Home page does not work", "description": "On Home page following text formatting is not working anymore (was working in 3.4.4)\r\n\r\n\r\nsomething *%{color:red}something%* something...\r\n \r\n\r\nIt gets displayed as plain text.\r\nThis still works in other places e.g. project overview.\r\n\r\n\r\n\r\nEnvironment:\r\n Redmine version 4.1.0.stable\r\n Ruby version 2.5.7-p206 (2019-10-01) [x64-mingw32]\r\n Rails version 5.2.4.1\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp\r\nSCM:\r\n Subversion 1.11.1\r\n Git 2.19.1\r\n Filesystem \r\nRedmine plugins:\r\n no plugin installed\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "127"}], "created_on": "2020-01-08T10:04:15Z", "updated_on": "2020-04-11T09:52:21Z"}, {"id": 32766, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 399737, "name": "Simon Busse"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Remove the URI limitation from external markdown links", "description": "*Problem (usecase)*\r\nThe Markdown Module of Redmine limits the possible URIs in markdown written links ([[RedmineTextFormattingMarkdown#External-links]]). But for us it is a very important feature to be able to link directly from Redmine to other apps. Therefore we need to be able to set links e.g. with the URI zpl://... (zeplin.io App on MacOS). With Textile this is possible, but not with Markdown.\r\nIMHO the security gain of the limitation is small, especially since there is no limitation with Textile.\r\n\r\n*possible solution*\r\nRemove the URI limitation in Markdown (/lib/redmine/helpers/uri.rb). Alternatively, the possible URIs could be made adjustable.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2020-01-08T08:36:01Z", "updated_on": "2021-04-17T17:45:28Z"}, {"id": 32762, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 437087, "name": "Ruud Poutsma"}, "subject": "Unicode character fails edit Issue", "description": "", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2020-01-07T10:03:36Z", "updated_on": "2020-01-07T10:54:48Z"}, {"id": 32747, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 10527, "name": "pasquale [:dedalus]"}, "category": {"id": 12, "name": "Translations"}, "subject": "Fix wrong translation for \"time entries\" in redmine 4.1.0", "description": "I have fixed 3 incorrect strings related to translation of \"time entries\"", "done_ratio": 0, "created_on": "2020-01-03T12:24:50Z", "updated_on": "2020-01-11T14:11:47Z"}, {"id": 32740, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 435980, "name": "liam Bosh"}, "category": {"id": 39, "name": "PDF export"}, "subject": "Incorrect characters when copying out of a Redmine generated PDF", "description": "When copying the text out of a Redmine generated PDF opened in Adobe Acrobat DC (2019.021.20058) the text when pasted is just shown as squares rather than the actual text.\r\ni.e. \r\n\"Description\r\njkjk\"\r\n\r\nbecomes \r\n\"", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "157"}], "created_on": "2020-01-02T14:34:10Z", "updated_on": "2020-01-05T10:04:21Z"}, {"id": 32739, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 8, "name": "Reopened"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 435613, "name": "Robert R\u00f6ttger"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Truncated images are still attached to the ticket when created by incoming e-mail", "description": "This ticket is refering to: https://www.redmine.org/projects/redmine/repository/revisions/3226\r\n\r\nI have a Mail looking like:\r\n\r\n\r\nCONTENT\r\n------\r\nSIGNATURE TEXT\r\nSIGNATURE IMAGE\r\n \r\n\r\nI setup my delimiter \"------\" in incoming mail settings in redmine.\r\nI send a mail. Ticket is Created.\r\n\r\nTicket Content Looks like:\r\n\r\n\r\nCONTENT\r\n \r\n\r\nEverything is truncated perfectly.\r\n \r\n*BUT:* the signature image is attached to the ticket. This shouldnt happen since its truncated. Maybe there must be changed in the parse order? First strip, then parse files? Instead of parse files and then strip. Please have a look at this.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Invalid"}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2020-01-02T13:08:33Z", "updated_on": "2020-01-06T09:03:46Z", "closed_on": "2020-01-05T10:28:42Z"}, {"id": 32729, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 435613, "name": "Robert R\u00f6ttger"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Line breaks when creating ticket or comment via Mail", "description": "Hello,\r\n\r\nthis affects new created issues from mail and tickets comments coming from mail.\r\n\r\nwhen I send a mail like this:\r\n\r\n\r\nhello\r\nmy\r\nname\r\nis\r\n\r\ntest\r\n \r\n\r\nI will get in redmine:\r\n\r\n\r\nhello
\r\nmy
\r\nname
\r\nis
\r\n
\r\ntest
\r\n \r\n\r\nthis looks like this:\r\n\r\n\r\nhello\r\n\r\nmy\r\n\r\nname\r\n\r\nis\r\n\r\n\r\ntest\r\n \r\n\r\nthis is pretty ugly and space consuming. its like double line breaks. can we not use instead of tags?\r\n\r\nthe prefered structure could be:\r\n\r\n
\r\nhello
\r\ntest
\r\n \r\n\r\n*you get what i mean? only open a new paragraph when there is an empty line between.*\r\n\r\n\r\ntested with mails coming from outlook and from web interface mails.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-12-30T10:13:20Z", "updated_on": "2020-11-29T05:07:12Z"}, {"id": 32706, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 435613, "name": "Robert R\u00f6ttger"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Creating new ticket via e-mail: use inline images also inline", "description": "Hello,\r\n\r\nwhen i send a email containing an image in the text (not in attachments) then it would be nice if it also is inside the text (inline) when the ticket will be created in redmine. its fine that the image file attached to the ticket to make it work. but it would be great if we can also display the image in the right position out of the box.\r\n\r\nI found this: https://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails\r\n\r\n_Redmine tries to use the plain text part of the email to fill the description of the issue.\r\nIf a HTML-only email is received, HTML tags are removed from its body.\r\n\r\nEmail attachments are automatically attached to the issue, unless their size exceeds the maximum attachment size defined in the application settings._\r\n\r\n\r\nthis kind of answers my question why it is like this now. but i think this could be rethought. i think it could be easy to translate html image tags into redmine image shortcut.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-12-27T15:04:47Z", "updated_on": "2020-05-03T04:04:39Z"}, {"id": 32704, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 435605, "name": "quancept quancept"}, "category": {"id": 4, "name": "Documents"}, "subject": "ActionView::Template::Error (undefined method `position' for nil:NilClass):", "description": "Started GET \"/redmine/projects/chinastockreceiver/documents\" for 127.0.0.1 at 2019-12-27 20:12:30 +0800\r\nProcessing by DocumentsController#index as HTML\r\n Parameters: {\"project_id\"=>\"chinastockreceiver\"}\r\n Current user: xuxf (id=17)\r\n Rendered attachments/_form.html.erb (15.7ms)\r\n Rendered documents/_form.html.erb (31.3ms)\r\n Rendered documents/index.html.erb within layouts/base (31.3ms)\r\nCompleted 500 Internal Server Error in 78.3ms\r\n\r\nActionView::Template::Error (undefined method `position' for nil:NilClass):\r\n 18: \r\n 19: <% if @grouped.empty? %><%= l(:label_no_data) %>
<% end %>\r\n 20: \r\n 21: <% @grouped.keys.sort.each do |group| %>\r\n 22: <%= group %> \r\n 23: <%= render :partial => 'documents/document', :collection => @grouped[group] %>\r\n 24: <% end %>\r\n app/models/enumeration.rb:93:in `<=>'\r\n app/views/documents/index.html.erb:21:in `sort'\r\n app/views/documents/index.html.erb:21:in `_app_views_documents_index_html_erb__107423285_27756576'", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "114"}], "created_on": "2019-12-27T12:59:56Z", "updated_on": "2020-06-01T10:07:16Z"}, {"id": 32664, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 5, "name": "Forums"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Adding an empty reply to a forum message does not show any error", "description": "Steps to reproduce:\r\n\r\n1. Open any forum topic and click \"Reply\"\r\n2. Attach any file and click \"Submit\"\r\n3. You will see \"Successful update\" message but the reply is not added. The attachment is silently discarded\r\n\r\nExpected behavior:\r\n\r\n\"Content cannot be blank\" error should be shown.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-20T00:45:35Z", "updated_on": "2020-02-04T09:33:24Z"}, {"id": 32663, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 434805, "name": "abdelrahman osama"}, "category": {"id": 2, "name": "Issues"}, "subject": "negative string size (or size too big)", "description": "*Hi,\r\nwhen i run script (RAILS_ENV=production scl enable ea-ruby24 'bundle exec rake db:migrate') give me the below issue :*\r\n\r\nrake aborted!\r\nArgumentError: negative string size (or size too big)\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/mysql2_adapter.rb:82:in `escape'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/mysql2_adapter.rb:82:in `quote_string'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/abstract/quoting.rb:166:in `_quote'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/abstract/quoting.rb:18:in `quote'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/mysql/schema_statements.rb:135:in `quoted_scope'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/mysql/schema_statements.rb:122:in `data_source_sql'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/connection_adapters/abstract/schema_statements.rb:61:in `table_exists?'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/schema_migration.rb:22:in `table_exists?'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/schema_migration.rb:26:in `create_table'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/migration.rb:1187:in `initialize'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/migration.rb:1036:in `new'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/migration.rb:1036:in `up'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/migration.rb:1011:in `migrate'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/tasks/database_tasks.rb:172:in `migrate'\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/activerecord-5.2.0/lib/active_record/railties/databases.rake:60:in `block (2 levels) in '\r\n/usr/local/rvm/gems/ruby-2.4.2/gems/rake-13.0.1/exe/rake:27:in `'\r\n/usr/local/rvm/gems/ruby-2.4.2/bin/ruby_executable_hooks:15:in `eval'\r\n/usr/local/rvm/gems/ruby-2.4.2/bin/ruby_executable_hooks:15:in `'\r\nTasks: TOP => db:migrate\r\n(See full trace by running task with --trace)\r\n\r\n\r\n*Any Help* ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-19T17:45:19Z", "updated_on": "2019-12-19T17:45:19Z"}, {"id": 32636, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 434241, "name": "M C"}, "category": {"id": 39, "name": "PDF export"}, "subject": "Export Wiki pages to pdf: background of table cells don't maintain its color", "description": "When exporting wiki pages to pdf and the wiki-page contain tables with colored backgrounds (e.g. we color-code the rows according to the type of information in that row), the exported tables in the pdf do not maintain the background color of the cells. Instead the background of the cells default to white or lightgey.\r\n\r\n{background:#f00; color:#fff}. |_. Col 1 |_. Col 2|\r\n|||\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "153"}], "created_on": "2019-12-13T11:45:43Z", "updated_on": "2019-12-13T11:45:43Z"}, {"id": 32626, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411127, "name": "Adrian Fey"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Delay notification E-Mails to allow edits / error corrections (without resend)", "description": "In a majority of my projects it happens a lot, that tickets will be created and include typos or errors and will be edited shortly after creation.\r\n\r\nWhen using the edit function in Redmine those changes are not resend by E-Mail if only the description of a comment was edited.\r\n\r\nIf someone adds information to a comment with the edit function or corrects a typo, all watchers will only receive (and probably read) the uncorrected version in the E-Mail.\r\n\r\nFor this reason it would be nice to have a parameter to set a delay for E-Mails.\r\nFor each change to a ticket by a user within this delay (delay is restarted after each change), the notification will be held back. \r\nIf more changes are made, the notification should merge does additional changes and send the final result, after the delay has passed.\r\n\r\nFor my projects this delay would be somewhere around 300 seconds, since our Tickets are not solved \"just in time\", this delay would be acceptable and would greatly reduce the amount of received E-Mails.\r\nThe massive amount of E-Mails often also leads to decreased awareness and more time consumption because of reading duplicate information on corrected tickets.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-12-12T10:14:09Z", "updated_on": "2019-12-12T10:14:09Z"}, {"id": 32612, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 306584, "name": "jwjw yy"}, "subject": "Distinct can be removed due to unique constraint in database", "description": "Hi, we are a research team that aims to detect and fix performance and data constraints problems in application built upon ORM framework, such as Rails. Redmine provides us with a good platform. \r\n\r\nThere are two queries can be improved by removing the distinct keyword based on the unique constraint created in database. \r\n\r\n\r\n@principals ||= Principal.active.joins(:members).where(\"#{Member.table_name}.project_id = ?\", id).distinct\r\n\r\n \r\n\r\n\r\n @users ||= User.active.joins(:members).where(\"#{Member.table_name}.project_id = ?\", \r\n\r\n \r\nconstraint is redmine/db/migrate/20101104182107_add_unique_index_on_members.rb\r\nadd_index :members, [:user_id, :project_id], :unique => true\r\n\r\nwhich means (user_id, project_id) will be unique. so this will make above two queries return distinct results without the `distinct` call.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-11T17:31:47Z", "updated_on": "2019-12-11T17:31:47Z"}, {"id": 32610, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 306584, "name": "jwjw yy"}, "subject": "A inner join can be removed", "description": "There is a query\r\n\r\nSELECT DISTINCT(issues.id) FROM issues INNER JOIN projects ON projects.id = issues.project_id INNER JOIN issue_statuses ON issue_statuses.id = issues.status_id LEFT OUTER JOIN users ON users.id = issues.assigned_to_id LEFT OUTER JOIN trackers ON trackers.id = issues.tracker_id LEFT OUTER JOIN enumerations ON enumerations.id = issues.priority_id AND enumerations.type IN ('IssuePriority') LEFT OUTER JOIN versions ON versions.id = issues.priority_id WHERE (projects.status <> 9 AND projects.id IN (SELECT em.project_id FROM enabled_modules em WHERE em.name='issue_tracking')) AND ((issues.status_id IN (SELECT id FROM issue_statuses WHERE is_closed=0)) AND projects.id = 3821) ORDER BY issues.id DESC LIMIT 501;\r\n \r\nwhich actually can be simplied due to the foreign key and presence constraint\r\n-- remove LEFT OUTER JOIN (because of id being PK, already done by postgres)\r\n-- remove INNER JOIN (because of FK; no need to add issues.project_id IS NOT NULL / issues.status_id IS NOT NULL because of constraint)\r\n-- remove DISTINCT (FK)\r\n\r\nAfter removing, the query becomes: \r\n\r\nSELECT issues.id FROM issues INNER JOIN projects ON projects.id = issues.project_id LEFT OUTER JOIN enumerations ON enumerations.id = issues.priority_id AND enumerations.type IN ('IssuePriority') WHERE (projects.status <> 9 AND projects.id IN (SELECT em.project_id FROM enabled_modules em WHERE em.name='issue_tracking')) AND ((issues.status_id IN (SELECT id FROM issue_statuses WHERE is_closed=0)) AND projects.id = 3821) ORDER BY issues.id DESC LIMIT 501;\r\n \r\n\r\nIt can make the code easier to read and faster\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-11T17:24:53Z", "updated_on": "2019-12-11T17:24:53Z"}, {"id": 32609, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "PRE: texts in PRE of issue mail will be renderred as large font and with multiple line break", "description": "texts in a pre block will be renderred with large font, and there will have double line break, in the notification mail.\r\n\r\nh2. View issue from browser:\r\n!Browser.png!\r\n\r\n\r\n\r\nh2. View issue in mail:\r\n!Outlook.png!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-11T15:09:02Z", "updated_on": "2019-12-11T15:09:02Z"}, {"id": 32608, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 2, "name": "Issues"}, "subject": "Watchers Invalid error when copying issue between project while users are member", "description": "Project1: adding members one by one for each users.\r\nProject2: adding members using the group, which group contains all the users of Project1.\r\n\r\nIssue1 is created in Project1, with watchers of Project1.\r\nCopy issue, set project as Project2, Watchers Invalid error pop up when submitting.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-11T14:59:26Z", "updated_on": "2019-12-12T07:37:53Z"}, {"id": 32605, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "feature: option to set the relation (AND?OR?brackets?) between different filers enabled for the query", "description": "Currently the default relationship between all filters enabled in Issue Query is \"AND\".\r\nBut this kind of filter is not powful enough.\r\n\r\nIf there is option to choose relationship for each new added filter, and option to set the brackets to combine them into different parts, that would be much more flexible for use.\r\n\r\nAnd together with my another issue https://www.redmine.org/issues/32561 to enable multiple add for a single filter, that would be pretty.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-12-11T10:45:30Z", "updated_on": "2019-12-11T10:45:30Z"}, {"id": 32602, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 68804, "name": "Israel Romero "}, "category": {"id": 32, "name": "REST API"}, "subject": "Add API support for enumerations in custom_fields", "description": "We have many enumeration values for distinct custom fields. It's hard to maintain manually. Could be possible add an API endpoint to handle new enumeration values for a given custom field? keeping alphabetically ordered?\r\n\r\nThanks in advance", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-12-11T09:04:32Z", "updated_on": "2019-12-11T09:04:32Z"}, {"id": 32583, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 416835, "name": "Ninad Patil"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Not able to generate ticket through mail using crontab", "description": "I have configure crontab for generating ticket through mail\r\n\r\nBelow is entry \r\n* * * * * rake -f /var/www/redmine/Rakefile redmine:email:receive_imap RAILS_ENV=\"production\" host=email.***.com username=connect@com password=*****\r\n\r\nWhen i manually executing this command working properly but we i scheduled in crontab not able to generate ticket\r\n\r\nKindly suggest is any problem in mention above command", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-12-09T10:55:55Z", "updated_on": "2019-12-09T10:55:55Z"}, {"id": 32563, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 12098, "name": "Martin Cizek"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Redmine 4 crashing with SEGFAULT under stress test when Markdown is used", "description": "Disclosure: my real motivation is to provide even more ammunition for #32424. But this issue is still valid and represents also a DOS and possibly other security vulnerability.\r\n\r\nThe Redcarpet-based wiki formatter is shared in Redmine, see source:trunk/lib/redmine/wiki_formatting/markdown/formatter.rb. I guess that with Rails 5 on Redmine 4, multithreaded operation became available by default. And when the app server supports multithreading, it just happens that Redmine is multithreaded (not a Rails expert). Redcarpet instance is not thread-safe - I've found \"this issue\":https://github.com/vmg/redcarpet/issues/570, opened for more than three years atm. \r\n\r\nSteps to reproduce:\r\n* @docker run redmine4@ Note[1]\r\n* Configure markdown as rext formatting, create some larger wiki pages, create an API key\r\n* Run a stress test with parallel requests, we were using 12 workers invoking @curl -sf -g -H \"X-Redmine-API-Key: $api_key\" -o \"$o\" \"$url/$q\"@\r\n\r\nfn1. Yes, it's using not recommended Webrick within @rails server@, still hope it's not an excuse for this behavior. :) Actually, we first came across this when creating a rake task for processing markup format conversions in parallel. But it happened also when we were doing rendering tests using standard Redmine stack, which is this issue.\r\n\r\nExpected result: everything is rendering fine.\r\n\r\nActual result: ruby segfaults after a few hundred pages rendered.\r\n\r\nruby: markdown.c:2896: sd_markdown_render: Assertion `md->work_bufs[BUFFER_SPAN].size == 0' failed.\r\n/usr/src/redmine/lib/redmine/wiki_formatting/markdown/formatter.rb:82: [BUG] Segmentation fault at 0x0000000000000000\r\nruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]\r\n \r\n\r\nPossible solutions:\r\n* Do not share Redcarpet formatter\r\n* Mutex it\r\n* Make it thread local\r\n* Document that multithreaded operation must be prevented when Markdown is used\r\n* Get rid of Redcarpet (yes, please! Plus #32424)\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "153"}], "created_on": "2019-12-08T13:20:24Z", "updated_on": "2019-12-08T13:20:24Z"}, {"id": 32561, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "feature: add support to add multiple instance for a single filter", "description": "If i want to filter issues with filter of a multiple value allowed field, named \"OS\", it contains some of predefined values such as OS1, OS2, OS3...\r\nIf i want to filter issues has value OS1 AND OS2, with the feature, I can:\r\n\r\nfirst add Filter \"OS\", operator \"IS\", value \"OS1\".\r\nthen add FIlter \"OS\" again, operator \"IS\", value \"OS2\".\r\nAnd apply.\r\n\r\nThis will be useful for lots of usage.\r\nSuch as IS OS1 and IS NOT OS2\r\nContains string1 and not contains string2\r\n...\r\n\r\nit's very useful.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-12-06T15:23:14Z", "updated_on": "2020-01-03T17:51:01Z"}, {"id": 32558, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 306584, "name": "jwjw yy"}, "subject": "Distinct can be removed ", "description": "In apps/redmine/app/models/project.rb, there is `User.active.joins(:members).where(\"#{Member.table_name}.project_id = ?\", id).distinct`. which will be translated to `SELECT DISTINCT users.* FROM users INNER JOIN members ON members.user_id = users.id WHERE users.status = 1 AND (members.project_id = ?);`\r\n\r\nActually DISTINCT is not necessary due to the uniqueness constraint in member.rb: `validate: user_id, uniqueness: {:scope => project_id}`, which indicates that for member1(member_id1, user_id, project_id) , and member2(member_id2, user_id, project_id), there is member_id1 = member_id2. Or else the uniqueness constraint will be violated. As a result the join result will not return duplicate users. \r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-12-06T03:07:20Z", "updated_on": "2019-12-06T03:07:20Z"}, {"id": 32548, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 36999, "name": "J\u00e9r\u00f4me BATAILLE"}, "category": {"id": 54, "name": "Hook requests"}, "subject": "Add new hook in projects/settings/_issues.html.erb for custom fields", "description": "This would be very helpful to add new features from plugins related to custom fields.\r\n\r\nThanks a lot to take in accout this very small patch\r\n\r\n <% unless @issue_custom_fields.empty? %>\r\n <%= toggle_checkboxes_link('#project_issue_custom_fields input[type=checkbox]:enabled') %><%=l(:label_custom_field_plural)%> \r\n <% @issue_custom_fields.each do |custom_field| %>\r\n \r\n <%= check_box_tag 'project[issue_custom_field_ids][]', custom_field.id, (@project.all_issue_custom_fields.include? custom_field),\r\n :disabled => (custom_field.is_for_all? ? \"disabled\" : nil),\r\n :id => nil %>\r\n <%= custom_field_name_tag(custom_field) %>\r\n \r\n <% end %>\r\n <%= hidden_field_tag 'project[issue_custom_field_ids][]', '' %>\r\n \r\ndiff --git a/lib/redmine/notifiable.rb b/lib/redmine/notifiable.rb\r\nindex 41fd736..822d216 100644\r\n--- a/lib/redmine/notifiable.rb\r\n+++ b/lib/redmine/notifiable.rb\r\n@@ -21,6 +21,9 @@ module Redmine\r\n notifications << Notifiable.new('message_posted')\r\n notifications << Notifiable.new('wiki_content_added')\r\n notifications << Notifiable.new('wiki_content_updated')\r\n+ Redmine::Hook.call_hook(:add_notifiable).each do |notifiable|\r\n+ notifications += notifiable\r\n+ end\r\n notifications\r\n end\r\n end\r\n\r\n\r\n# In plugins/my_plugin/lib/hooks.rb\r\nmodule MyPluginHooks\r\n class MyPluginHooks < Redmine::Hook::Listener\r\n def add_notifiable(_context)\r\n [Redmine::Notifiable.new('my_plugin_new_notifiable')]\r\n end\r\n end\r\nend\r\n\r\n# In plugins/my_plugin/init.rb\r\n...\r\nrequire_relative 'lib/hooks.rb'\r\n...\r\n\r\n\r\n# Now we can use\r\nSetting.notified_events.include?('my_plugin_new_notifiable')\r\n\r\n\r\n\r\n[Thu, 20 Jul 2006 04:04:21 JST +09:00,\r\n Thu, 20 Jul 2006 04:07:27 JST +09:00,\r\n Thu, 14 Nov 2019 16:27:41 JST +09:00,\r\n Tue, 19 Nov 2019 16:27:41 JST +09:00,\r\n Sun, 24 Nov 2019 16:27:41 JST +09:00,\r\n Sun, 24 Nov 2019 16:27:41 JST +09:00,\r\n Sun, 24 Nov 2019 16:27:41 JST +09:00,\r\n Tue, 26 Nov 2019 16:27:41 JST +09:00,\r\n Fri, 29 Nov 2019 16:26:41 JST +09:00,\r\n Fri, 29 Nov 2019 16:26:41 JST +09:00,\r\n Fri, 29 Nov 2019 16:26:41 JST +09:00]\r\n\r\n> Issue.all.open.group_by{|i| i.created_on.to_date}.map{|k, values| [k, values.count]}.to_h\r\n{Thu, 20 Jul 2006=>2,\r\n Tue, 19 Nov 2019=>1,\r\n Tue, 26 Nov 2019=>1,\r\n Fri, 29 Nov 2019=>3,\r\n Thu, 14 Nov 2019=>1,\r\n Sun, 24 Nov 2019=>3}\r\n\r\n> query.result_count_by_group\r\n{Wed, 19 Jul 2006=>2,\r\n Tue, 19 Nov 2019=>1,\r\n Tue, 26 Nov 2019=>1,\r\n Fri, 29 Nov 2019=>3,\r\n Thu, 14 Nov 2019=>1,\r\n Sun, 24 Nov 2019=>3}\r\n\r\n# http://www.redmine.org/projects/redmine/repository/entry/trunk/lib/redmine/database.rb#L71\r\n if postgresql?\r\n if time_zone\r\n identifier = ActiveSupport::TimeZone.find_tzinfo(time_zone.name).identifier\r\n \"(#{column}::timestamptz AT TIME ZONE '#{identifier}')::date\"\r\n else\r\n \"#{column}::date\"\r\n end\r\n else\r\n # ...\r\n\r\nrequire 'redmine/my_page'\r\n\r\nrequire_dependency 'redmine/my_page'\r\n\r\nbundle install --without development test\r\n \r\n\r\nfinishes with message\r\n\r\n\r\nBundle complete! 28 Gemfile dependencies, 59 gems now installed.\r\nGems in the groups development and test were not installed.\r\nUse `bundle show [gemname]` to see where a bundled gem is installed.\r\n \r\n\r\nRunning\r\n\r\nbundle exec rake generate_secret_token\r\n \r\n\r\ncrashes with\r\n\r\n\r\n/usr/lib/ruby/2.5.0/rubygems/resolver.rb:231:in `search_for': Unable to resolve dependency: user requested 'did_you_mean (= 1.2.0)' (Gem::UnsatisfiableDependencyError)\r\n \r\n\r\nRunning\r\nrake generate_secret_token\r\n \r\n\r\n(without _bundle exec_)\r\n\r\nhowever works and produces the file /config/initializers/secret_token.rb\r\n\r\nRunning\r\n\r\nbundle exec rake db:migrate RAILS_ENV=production \r\n \r\n\r\ncrashes with:\r\n\r\n 20: from /usr/local/bin/rake:23:in `'\r\n 19: from /usr/lib/ruby/2.5.0/rubygems.rb:309:in `activate_bin_path'\r\n 18: from /usr/lib/ruby/2.5.0/rubygems.rb:309:in `synchronize'\r\n 17: from /usr/lib/ruby/2.5.0/rubygems.rb:311:in `block in activate_bin_path'\r\n 16: from /usr/lib/ruby/2.5.0/rubygems.rb:243:in `finish_resolve'\r\n 15: from /usr/lib/ruby/2.5.0/rubygems/request_set.rb:397:in `resolve_current'\r\n 14: from /usr/lib/ruby/2.5.0/rubygems/request_set.rb:385:in `resolve'\r\n 13: from /usr/lib/ruby/2.5.0/rubygems/resolver.rb:188:in `resolve'\r\n 12: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:42:in `resolve'\r\n 11: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:64:in `resolve'\r\n 10: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:106:in `start_resolution'\r\n 9: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:165:in `initial_state'\r\n 8: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:51:in `sort_dependencies'\r\n 7: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:69:in `with_no_such_dependency_error_handling'\r\n 6: from /usr/lib/ruby/2.5.0/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:52:in `block in sort_dependencies'\r\n 5: from /usr/lib/ruby/2.5.0/rubygems/resolver.rb:277:in `sort_dependencies'\r\n 4: from /usr/lib/ruby/2.5.0/rubygems/resolver.rb:277:in `with_index'\r\n 3: from /usr/lib/ruby/2.5.0/rubygems/resolver.rb:277:in `sort_by'\r\n 2: from /usr/lib/ruby/2.5.0/rubygems/resolver.rb:277:in `each'\r\n 1: from /usr/lib/ruby/2.5.0/rubygems/resolver.rb:283:in `block in sort_dependencies'\r\n/usr/lib/ruby/2.5.0/rubygems/resolver.rb:231:in `search_for': Unable to resolve dependency: user requested 'did_you_mean (= 1.2.0)' (Gem::UnsatisfiableDependencyError)\r\n\r\n \r\n\r\nRunning\r\n\r\nrake db:migrate RAILS_ENV=production\r\n \r\n\r\n(without _bundle exec_)\r\n\r\nResults in\r\n\r\nrake aborted!\r\nNameError: undefined local variable or method `config' for main:Object\r\n/usr/share/redmine/plugins/open_id_authentication/init.rb:7:in `'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\r\n/usr/share/redmine/lib/redmine/plugin.rb:175:in `block in load'\r\n/usr/share/redmine/lib/redmine/plugin.rb:166:in `each'\r\n/usr/share/redmine/lib/redmine/plugin.rb:166:in `load'\r\n/usr/share/redmine/config/initializers/30-redmine.rb:21:in `'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `block in load'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer'\r\n/var/lib/gems/2.5.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in `instrument'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:656:in `load_config_initializer'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in '\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `each'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `block in '\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `instance_exec'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `run'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `each'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:60:in `run_initializers'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/application.rb:361:in `initialize!'\r\n/usr/share/redmine/config/environment.rb:14:in `'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/application.rb:337:in `require'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/application.rb:337:in `require_environment!'\r\n/var/lib/gems/2.5.0/gems/railties-5.2.3/lib/rails/application.rb:520:in `block in run_tasks_blocks'\r\n/var/lib/gems/2.5.0/gems/rake-13.0.0/exe/rake:27:in `'\r\nTasks: TOP => db:migrate => db:load_config => environment\r\n \r\n\r\n\r\nI have\r\nruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]\r\ninstalled.\r\n\r\nAs a consequence, I am not able to finish the upgrade procedure.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "153"}], "created_on": "2019-11-10T15:12:19Z", "updated_on": "2019-11-10T15:12:19Z"}, {"id": 32438, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 10527, "name": "pasquale [:dedalus]"}, "assigned_to": {"id": 1, "name": "Jean-Philippe Lang"}, "category": {"id": 25, "name": "Website (redmine.org)"}, "subject": "Update the public site www.redmine.org ti latest release", "description": "This because we can have a realistic feedback on some issues that is difficult to reproduce (for example #32314, #31241 etc)", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-11-09T10:59:19Z", "updated_on": "2020-12-28T01:53:24Z"}, {"id": 32435, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 429275, "name": "Stanislav Ogryzkov"}, "category": {"id": 12, "name": "Translations"}, "subject": "The \u201cApply\u201d button translation to Russian", "description": "Now the \u201cApply\u201d button (on the \u201cUpdate\u201d issue page) is translated to Russian as \u00ab\u041f\u0440\u0438\u043d\u044f\u0442\u044c\u00bb while should be translated as \u00ab\u041f\u0440\u0438\u043c\u0435\u043d\u0438\u0442\u044c\u00bb.\r\n\r\nIf there's some Russian language file I could fix myself and attach it here, please attach one.", "done_ratio": 0, "created_on": "2019-11-08T07:01:38Z", "updated_on": "2020-07-28T04:28:21Z"}, {"id": 32433, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 14, "name": "Custom fields"}, "subject": "feature: option for CustomField to update the values by some of roles and different default value for different project", "description": " if there is option of the Administration, do define some of the roles to have the permission to define the Value/DefaultValue of some of the Redmine Custom Fields, and different default value for different project, it would be great.\r\n\r\nWe can use it to manage the pre-defined values of custom fields directly in the project by role, without turn to Administrator to update the pre-defined value again and again.\r\nAnd we can set the default value for different project.\r\nOr maybe even, we can set the pre-defined value for different project all or project, different default value for different project or all project.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-11-07T07:22:07Z", "updated_on": "2020-03-02T08:53:56Z"}, {"id": 32426, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Search from journal for specific value of specific field during specific period", "description": "Currently the query filter set can only search the last value of the fields of issues.\r\nAnd the filter \"Updated\" can only search updated during a period, but can't search what is updated, and what is/was the value of it.\r\n\r\nIt would be better to expand the query of the \"Updated\" to search from the journal.\r\nsuch as:\r\nupdated: add more query criteria to filter which property/field is updated, and the old/new value of that property/field\r\nor:\r\nquery: field value was xxx at xxx time, operator can be was during, value: field value + datetime1 + datetime2\r\nor: \r\nquery: updated + fieldvalue at that time", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-11-06T14:56:07Z", "updated_on": "2019-11-06T14:56:07Z"}, {"id": 32424, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 40856, "name": "Jens Kr\u00e4mer"}, "assigned_to": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 26, "name": "Text formatting"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "CommonMark Markdown Text Formatting", "description": "This patch introduces a new text formatting named _CommonMark Markdown (GitHub Flavored)_. It is based on \"CommonMarker\":https://github.com/gjtorikian/commonmarker and \"HTMLPipeline\":https://github.com/jch/html-pipeline. The formatter was extracted from \"Planio\":https://plan.io/hosted-redmine where it will soon become the default for new accounts.\r\n\r\nWe built this instead of going with the existing RedCarpet Markdown implementation for a number of reasons:\r\n\r\n* From time to time users who are using the current Markdown formatter ask for a spec / formal list of all supported features. No such thing exists for RedCarpet. There is \"CommonMark\":https://commonmark.org/ but RedCarpet isn't going to support it in the short to medium term (see next point).\r\n* The future development of RedCarpet is uncertain. Few excerpts from a \"GitHub issue\":https://github.com/vmg/redcarpet/issues/429 , a year ago:\r\n\r\n> Commonmark won't be supported anytime soon\r\n\r\nand\r\n\r\n> A general message about the project for people skimming this thread: I'm sorry Redcarpet isn't really active anymore but my resources are pretty limited since I'm committed to other open source projects and still a student. Feel free to use any existing alternative ; this project isn't the great tool it used to be when it was maintained by Vicent.\r\n\r\n* With CommonMark evolving as a Markdown spec that is supported by many implementations and endorsed by organizations like Gitlab and GitHub (which both did the switch from RedCarpet to CommonMarker a while ago), it quickly becomes what users expect when they hear 'Markdown'.\r\n* Migrating existing Textile content is a bit easier since Pandoc has a dedicated Github Flavored Markdown writer module.\r\n* The HTML pipeline approach encourages splitting up the formatting process into it's different aspects (html generation, sanitizing, syntax highlighting etc) which allows for better testability and has potential for future re-use of components with other text formatters. Further, HTML pipeline filters work on actual DOM nodes, making tasks like adding classes to links etc much more straight forward and less prone to bugs than doing so with regular expressions.\r\n\r\nLast but not least, this formatter solves a number of currently open issues regarding the RedCarpet based _Markdown_ Formatter:\r\n\r\n* #19880 (Incorrect syntax for links in Markdown)\r\n* #20497 (Markdown formatting supporting HTML)\r\n* #20841 (Bare URLs in Markdown don't have \"external\" class)\r\n* #29172 (Markdown: External links broken)\r\n\r\nThe main reason why we want to introduce this as a third formatting option and not just replace the existing Markdown formatter is line endings - this formatter does not insert hard breaks (@\r\nEnvironment:\r\n Redmine version 3.4.12.stable\r\n Ruby version 2.4.6-p354 (2019-04-01) [x86_64-linux]\r\n Rails version 4.2.11.1\r\n Environment production\r\n Database adapter Mysql2\r\nSCM:\r\n Subversion 1.9.7\r\n Git 2.17.1\r\n Filesystem \r\nRedmine plugins:\r\n redmine_tags 3.2.2\r\n scrum 0.18.0\r\n \r\n\r\nApache configuration:\r\n\r\n\r\nPassengerRuby /usr/share/rvm/wrappers/ruby-2.4.6/ruby\r\n\r\n\r\n ServerName our_great.server\r\n DocumentRoot /var/redmine_staging/public\r\n PassengerStickySessions on\r\n\r\n \r\n Allow from all\r\n Options -MultiViews\r\n Require all granted\r\n \r\n \r\n \r\n\r\nProxy:\r\n\r\n\r\nProxyPass /redmine-qa http://localhost:3300 nocanon\r\nProxyPassReverse /redmine-qa http://localhost:3300\r\nProxyRequests Off\r\nAllowEncodedSlashes NoDecode\r\n \r\n Options +Indexes +ExecCGI +FollowSymLinks -MultiViews\r\n Order Allow,Deny\r\n Allow from all\r\n \r\n \r\n\r\nenvironment.rb\r\n\r\n\r\n# Load the Rails application\r\nrequire File.expand_path('../application', __FILE__)\r\n # Make sure there's no plugin in vendor/plugin before starting\r\nvendor_plugins_dir = File.join(Rails.root, \"vendor\", \"plugins\")\r\nif Dir.glob(File.join(vendor_plugins_dir, \"*\")).any?\r\n $stderr.puts \"Plugins in vendor/plugins (#{vendor_plugins_dir}) are no longer allowed. \" +\r\n \"Please, put your Redmine plugins in the `plugins` directory at the root of your \" +\r\n \"Redmine directory (#{File.join(Rails.root, \"plugins\")})\"\r\n exit 1\r\nend\r\n\r\n# Initialize the Rails application\r\nRails.application.initialize!\r\n\r\nRedmine::Utils::relative_url_root = \"/redmine-qa\"\r\n \r\n\r\nIn addition, this wiki will need updating probably:\r\nhttps://www.redmine.org/projects/redmine/wiki/HowTo_Install_Redmine_on_subdirectory_(sub-URI)_on_Apache", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "154"}], "created_on": "2019-11-05T08:41:06Z", "updated_on": "2019-11-05T08:41:06Z"}, {"id": 32405, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 428314, "name": "Besnik Bleta"}, "category": {"id": 12, "name": "Translations"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Updating sq translation", "description": "Hello,\r\n\r\nHere\u2019s an attempt to update and complete sq translation of Redmine. \r\nI\u2019d appreciate if someone can run the tests on them, as I failed to do so myself.\r\n\r\nTIA,\r\nBesnik", "done_ratio": 0, "created_on": "2019-11-04T17:23:20Z", "updated_on": "2020-11-27T15:53:24Z"}, {"id": 32404, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 428180, "name": "Simon Hori"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Group results is different between MySQL and PostgreSQL", "description": "Recently we've migrated a huge DB from MySQL to PostgreSQL. And noticed a small difference with *Group results by* function.\r\n\r\nAs you see the screenshot below, MySQL shows *(blank)* group *first* but PostgreSQL shows *(blank)* group *last*.\r\n\r\n!PostgreSQL-MySQL-NULL.png!\r\n\r\nI guess it is because `NULLS LAST` is the default for ASC order in PostgreSQL.\r\nCan you enforce `NULLS FIRST` in the SQL query to postgres?\r\nhttps://www.postgresql.org/docs/8.3/queries-order.html\r\n\r\nWe believe that it would be very much appreciated since many of our users want to group issues by assignee to find unassigned issues. Also it would be nice if Redmine works consistently irrespective of db engines.\r\n\r\n\r\n Redmine version 3.4.11.stable\r\n Ruby version 2.4.6-p354 (2019-04-01) [x86_64-linux]\r\n Rails version 4.2.11.1\r\n Database adapter PostgreSQL\r\n \r\n\r\nThank you.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-11-04T14:56:30Z", "updated_on": "2019-11-19T08:41:35Z"}, {"id": 32399, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 107353, "name": "Marius BALTEANU"}, "category": {"id": 15, "name": "Importers"}, "subject": "Drop support for migrating from Trac or Mantins", "description": "In the last 3 or 4 years there were no improvements made to the scripts provided by Redmine to migrate from Mantis or Trac to Redmine. During these years, Redmine improved a lot. Also, there are at least 45 \"open issues\":http://www.redmine.org/projects/redmine/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=category_id&op%5Bcategory_id%5D=%3D&v%5Bcategory_id%5D%5B%5D=15&f%5B%5D=subject&op%5Bsubject%5D=%7E&v%5Bsubject%5D%5B%5D=trac&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=subject&c%5B%5D=updated_on&c%5B%5D=category&group_by= related to migration from Trac and \"14\":http://www.redmine.org/projects/redmine/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=category_id&op%5Bcategory_id%5D=%3D&v%5Bcategory_id%5D%5B%5D=15&f%5B%5D=subject&op%5Bsubject%5D=%7E&v%5Bsubject%5D%5B%5D=mantis&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=subject&c%5B%5D=updated_on&c%5B%5D=category&group_by= related to migration from Mantis.\r\n\r\nMy proposal is to drop support for those 2 migration scripts.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-11-02T13:43:43Z", "updated_on": "2019-12-06T13:36:41Z"}, {"id": 32381, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 36999, "name": "J\u00e9r\u00f4me BATAILLE"}, "category": {"id": 1, "name": "Wiki"}, "subject": "Wiki preview : manage dynamic content", "description": "Hi,\r\n\r\n* *In public/javascripts/application.js*\r\nThe wiki toolbar preview event is written like this :\r\n\r\n\r\n $('#content').on('click', 'div.jstTabs a.tab-preview', function(event){\r\n...\r\n\r\n $('body').on('click', '#content.scrum div.jstTabs a.tab-preview', function(event){\r\n...\r\n\", \"Add new - \"\r\n\r\nAny feedback is welcome.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-26T21:48:50Z", "updated_on": "2019-11-21T05:40:23Z"}, {"id": 32342, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 310708, "name": "Martina A."}, "category": {"id": 52, "name": "Files"}, "subject": "File list CSV report", "description": "Is it possible to export the list of uploaded files as CSV report?\r\nIncluding Filename, Date, Size, D/L, MD5\r\nIn addition the name of the person, who did the upload.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-25T08:48:41Z", "updated_on": "2019-10-25T08:48:41Z"}, {"id": 32326, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 10527, "name": "pasquale [:dedalus]"}, "assigned_to": {"id": 10527, "name": "pasquale [:dedalus]"}, "category": {"id": 12, "name": "Translations"}, "subject": "Update it.yml locale", "description": "* added various missing strings;\r\n* reorder strings into the file;\r\n* made some changes to already translated strings for consistency.\r\n\r\n", "done_ratio": 0, "created_on": "2019-10-23T11:23:26Z", "updated_on": "2019-10-29T08:51:21Z"}, {"id": 32322, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "changes made to filter/column/groupby is not saved to session cookie", "description": "changes made to filter/column/groupby is not saved to session cookie, after the browser is closed and restarted, the settings recovered to default values.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-10-22T07:31:33Z", "updated_on": "2020-03-02T11:19:12Z"}, {"id": 32317, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Issue filter: locale: label_issue: confusing the Issue and IssueID", "description": "From the Issue Filter, the \"Issue\" actually should be \"IssueID\", but displayed as \"Issue\".\r\nAnyway it will confuse users.\r\n\r\nEn: Issue, IssueID\r\nzh: \u95ee\u9898, \u95ee\u9898\u7f16\u53f7\r\nzh-TW: \u8b70\u984c, \u8b70\u984c\u7de8\u865f", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-22T05:37:13Z", "updated_on": "2019-10-22T20:41:57Z"}, {"id": 32312, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 425397, "name": "Yury Vashinko"}, "subject": "Disable auto selecting in top right Project filter", "description": "Add configuration point to be able to disable autoswitching project while viewing issue", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-21T07:53:55Z", "updated_on": "2019-10-21T07:53:55Z"}, {"id": 32311, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 56, "name": "Issues filter"}, "subject": "Filter Issues by multiple issue_id doesn't support space character or semicolon/dash as the separator", "description": "Issues -> Filter -> Issue\r\nstatement \"is\", input the filter value as multiple ids, such as \"1,2,3\".\r\n\r\nIt only supports comma \",\" as the separator of issue ids.\r\nIt doesn't support other common separators, such as space, semicolon, dash.\r\n\r\nAnd actually if we copied the ids from the id column from excel, it would be multiple lines combined with also semicolon.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-21T07:20:05Z", "updated_on": "2019-12-25T08:35:29Z"}, {"id": 32305, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 26, "name": "Text formatting"}, "subject": "Use of notextile tag disables Redmine revision links", "description": "As observed [yet] only on redmine.org (see #29482#note-90 and #29482#note-91), comments (in this case issue notes) having the following structure does not render the revision as a link:\r\n\r\n
@ User One: Some text before @some code@ before _some italic text_ before a revision link like rDDDD.\r\nUser One wrote:\r\n> @ User One: Some text before @some code@ before _some italic text_ before a revision link like rDDDD.\r\n \r\nStarted GET \"/queries/filter?project_id=1&type=IssueQuery&name=author_id\" for 127.0.0.1 at 2019-10-18 17:34:50 +0900\r\nProcessing by QueriesController#filter as JSON\r\n Parameters: {\"project_id\"=>\"1\", \"type\"=>\"IssueQuery\", \"name\"=>\"author_id\"}\r\n.\r\n.\r\n.\r\n Rendering common/error.html.erb\r\n Rendered common/error.html.erb (1.2ms)\r\nCompleted 403 Forbidden in 16ms (Views: 6.4ms | ActiveRecord: 2.4ms)\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-18T08:41:51Z", "updated_on": "2019-10-18T08:41:51Z"}, {"id": 32296, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411898, "name": "Masahiro IUCHI"}, "category": {"id": 30, "name": "Code cleanup/refactoring"}, "subject": "Ignore rubocop offense", "description": "I found a rubocop offense is remaining.\r\n\r\n\r\n$ rubocop db/migrate/20190510070108_add_unique_id_to_import_items.rb\r\nInspecting 1 file\r\nC\r\n\r\nOffenses:\r\n\r\ndb/migrate/20190510070108_add_unique_id_to_import_items.rb:3:5: C: Rails/BulkChangeTable: You can combine alter queries using bulk: true options.\r\n change_table :import_items do |t|\r\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\r\n\r\n1 file inspected, 1 offense detected\r\n \r\n\r\nEnvironment information:\r\n\r\n\r\n$ RAILS_ENV=test bin/about\r\n\r\nEnvironment:\r\n Redmine version 4.0.4.devel.18732\r\n Ruby version 2.5.5-p157 (2019-03-15) [x86_64-darwin19]\r\n Rails version 5.2.3\r\n Environment test\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::InlineAdapter\r\n Mailer delivery test\r\nSCM:\r\n Subversion 1.10.4\r\n Git 2.21.0\r\n Filesystem\r\nRedmine plugins:\r\n no plugin installed\r\n \r\n\r\nI have created a patch to ignore it like other migration files.\r\n", "done_ratio": 0, "created_on": "2019-10-18T06:42:08Z", "updated_on": "2020-10-13T08:19:14Z"}, {"id": 32293, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 45, "name": "Gems support"}, "subject": "Redmine does not start if optional openid gems are not installed", "description": "At source:tags/4.0.4/Gemfile#L28, openid gems are stated as optional.\r\n\r\n\r\n# Optional gem for OpenID authentication\r\ngroup :openid do\r\n gem \"ruby-openid\", \"~> 2.3.0\", :require => \"openid\"\r\n gem \"rack-openid\"\r\nend\r\n \r\n\r\nHowever, but Redmine fails to start with the error \"LoadError: cannot load such file -- openid\" if you skipped installing openid gems.\r\n\r\n\r\nSteps to reproduce:\r\n\r\n$ svn co https://svn.redmine.org/redmine/trunk redmine\r\n$ cd redmine\r\n$ vim config/database.yml # configure config/database.yml\r\n$ bundle install --without openid\r\n$ bin/rake db:migrate\r\nrake aborted!\r\nLoadError: cannot load such file -- openid\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\r\n/private/tmp/redmine/lib/plugins/open_id_authentication/lib/open_id_authentication.rb:2:in `'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\r\n/private/tmp/redmine/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\r\n/private/tmp/redmine/lib/plugins/open_id_authentication/init.rb:7:in `block in '\r\n/private/tmp/redmine/config/initializers/00-core_plugins.rb:14:in `eval'\r\n/private/tmp/redmine/config/initializers/00-core_plugins.rb:14:in `block in '\r\n/private/tmp/redmine/config/initializers/00-core_plugins.rb:4:in `each'\r\n/private/tmp/redmine/config/initializers/00-core_plugins.rb:4:in `'\r\n.\r\n.\r\n.\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-18T02:15:28Z", "updated_on": "2019-10-20T04:52:46Z"}, {"id": 32278, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 49905, "name": "Brice Beaumesnil"}, "category": {"id": 22, "name": "Roadmap"}, "subject": "Display Global Roadmap without any tracker", "description": "The idea : \r\n\r\n- Display Roadmap page without any selected tracker. It's impossible : if we deselect all trackers and \"Apply\" : they are automatically reselected all. This view is usefull for CTO for example, it's just to see all projets advancement without any details.\r\n\r\nAnd better, if we can make filter on trakcers (with ordering) and save result like Issues page...\r\n\r\nThank you for your great work.\r\n\r\nbest regards", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-15T09:12:41Z", "updated_on": "2019-10-17T08:12:53Z"}, {"id": 32253, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 188597, "name": "Guillermo ML"}, "category": {"id": 24, "name": "Documentation"}, "subject": "Last Mercurial version supported", "description": "In [[RedmineRepositories]] the Mercurial versions supported are from 1.2 to 4.3.1.\r\n\r\nWe upgraded Redmine from 3.4.4 to 4.0.4 (centos 6.9 with Mercurial 1.4) and got this error:\r\n\r\nhg --config extensions.redminehelper=redminehelper.py rhsummary\r\n*** failed to import extension redminehelper from redminehelper.py: 'module' object has no attribute 'command'\r\nhg: unknown command 'rhsummary'\r\nMercurial Distributed SCM\r\n \r\n\r\nWe upgraded Mercurial from 1.4 to 4.0 and the problem was solved.\r\n\r\nI would update the wiki myself, but I don't know which is the minimum version supported.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-14T11:55:59Z", "updated_on": "2019-10-14T11:55:59Z"}, {"id": 32246, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 423516, "name": "Wurzel mann"}, "category": {"id": 1, "name": "Wiki"}, "subject": "[Redmine API] functionality to export whole wiki", "description": "I'm trying to export my whole wiki via the Redmine API, but the export whole wiki function as seen in the bottom right-hand corner when sorting by index is not working.\r\n\r\nIt is possible to export single pages via the API, but not the whole wiki, but I'd be really great to be able to backup the wiki this way in an automated fashion.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-13T20:01:22Z", "updated_on": "2019-10-13T20:01:22Z"}, {"id": 32201, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1565, "name": "Mischa The Evil"}, "category": {"id": 25, "name": "Website (redmine.org)"}, "subject": "Issue auto-assignment to JPL based on Website category", "description": "Is this still desirable/needed?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-05T03:26:47Z", "updated_on": "2019-10-08T04:36:01Z"}, {"id": 32193, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 334743, "name": "Hinako Tajima"}, "category": {"id": 51, "name": "Security"}, "subject": "Add turn on/off button to control sending security notifications", "description": "For sending security notifications, I wish to add the function that to make possible with controlling turn on/off by configuration or management console.\r\n\r\n\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u901a\u77e5\u30e1\u30fc\u30eb\u306e\u9001\u4fe1\u3092\u8a2d\u5b9a\u3067ON/OFF\u3067\u304d\u308b\u3088\u3046\u306b\u3057\u3066\u307b\u3057\u3044\u3002", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-04T05:17:58Z", "updated_on": "2019-10-09T07:44:45Z"}, {"id": 32191, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 322509, "name": "Jon Schell"}, "category": {"id": 3, "name": "SCM"}, "subject": "Duplicate associated revisions when using multiple repositories for a project", "description": "I have a project that has several repositories linked to it. Repo A includes an extern to a folder in Repo B. When a commit is made to Repo A the associated issue displays the associated revision entry twice. Both are identical. When a commit is made to Repo B, it's done correctly with a single entry. The commits are not spanning the repos over the extern, they are entirely within one repo or the other.\r\n\r\nAttached picture shows the first entry only once because it's done to Repo B. The rest are commits to Repo A.\r\n\r\nWe do have the option to fetch commits automatically turned off and instead we run a cron job using \"redmine:fetch_changesets\" to update it.\r\n\r\nDatabase manager version: Mysql2\r\nRuby version: 2.1.5-p273 (2014-11-13) [x86_64-linux-gnu]\r\nRails version: 4.2.8\r\nRedmine version: 3.4.3.stable\r\nscm binary version: svn 1.8.10\r\nNo plugins\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Duplicate"}, {"id": 4, "name": "Affected version", "value": "133"}], "created_on": "2019-10-04T00:20:17Z", "updated_on": "2019-10-07T17:28:52Z", "closed_on": "2019-10-06T01:39:56Z"}, {"id": 32183, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 9, "name": "Email notifications"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Notification sub-events for \"Issue updated\" does not cover all events which consist its parent", "description": "You can configure notification events in \"Administration\" > \"Settings\" > \"Select actions for which email notifications should be sent.\". In the section, you can see \"Issue updated\" and its sub-events, \"Note added\", \"Status updated\", \"Assignee updated\", and \"Priority updated\".\r\n\r\nThe issue I am going to point out is that the four sub-events don't cover all notification types that handled by the \"Issue updated\" event. For example, add/remove relations trigger notifications if \"Issue updated\" is enabled. But there is no such sub-event on the page.\r\n\r\nAs a result, the following two configurations work differently. I think most users expect that the two configurations work the same. It is confusing.\r\n\r\n!{width: 370px; border: 1px solid #ccc;}.notified-events-config-1@2x.png!\r\n\r\n!{width: 370px; border: 1px solid #ccc;}.notified-events-config-2@2x.png!\r\n\r\n\r\n\r\nIt is quite misleading. Many users misunderstand that \"Issue updated\" consists of \"Note added\", \"Status updated\", \"Assignee updated\", and \" Priority updated\". But \"Issue updated\" includes some other \"hidden\" events such as an update of description and a change of relation. Probably users never think that \"Issue updated\" includes \"hidden\" events.\r\n\r\nMy idea to resolve the problem is to add a new sub-event \"Other issue attributes updated\". This sub-event covers all other events (I mentioned before as \"hidden events\").\r\n\r\n!{width: 380px; border: 1px solid #ccc;}.other-issue-attributes-event@2x.png!\r\n\r\nThe benefits of adding the sub-event as follows:\r\n\r\n* Users can easily understand that there are some other events that trigger notifications\r\n* It makes easy for users to find the way to disable unimportant notifications such as \"Relation added\"\r\n* Makes things consistent. There are no \"hidden\" events any longer", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-10-03T05:16:15Z", "updated_on": "2019-11-04T02:53:15Z"}, {"id": 32181, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 420648, "name": "Ahmet Demir"}, "category": {"id": 41, "name": "Issues workflow"}, "subject": "Auto Status Change from New to In Progress", "description": "Hi All,\r\n\r\nIs there any way to change status automatically when we update the new issue?\r\n\r\nThanks,\r\nAhmet", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-02T09:08:05Z", "updated_on": "2019-10-02T09:08:05Z"}, {"id": 32178, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 310708, "name": "Martina A."}, "category": {"id": 14, "name": "Custom fields"}, "subject": "Conditioned Custom Fields", "description": "Dear all,\r\n\r\nis it possible to create conditioned custom fields, which pop-up only, if a first custom field is answered with a predefined content?\r\n\r\nCustom Field 1 = Answer 1 -> other custom fields appear and completion is possible\r\nCustom Field 1 = Answer 2 -> the other custom fields remain invisible, completion is not necessary\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-10-01T08:50:50Z", "updated_on": "2019-10-01T08:50:50Z"}, {"id": 32176, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 420231, "name": "Prashant Chavan"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Emails are not getting triggered", "description": "When we create a new ticket and update existing one emails are not getting triggered. Kindly help as we have to manually inform to business every time.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-09-30T12:32:51Z", "updated_on": "2019-11-07T08:33:33Z"}, {"id": 32168, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 56, "name": "Issues filter"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Allow issue id with \"#\" prefix for the value of issue ids filter", "description": "I found an inconsistent behavior regarding issues filter.\r\n\r\n\"Parent task\" and \"Subtasks\" filter accept issue ids with \"#\" prefix (e.g. !#123), however, \"Issues\" filter does not. I think \"Issues\" filter should also behave the same.\r\n\r\n|_. Filter value|_. \"Parent task\" / \"Subtasks\" filter |_. \"Issue\" filter |\r\n| @10,11@ | OK | OK |\r\n| @#10,#11@ | OK | \"Issue is invalid\" error |\r\n| @10, 11@ | OK | \"Issue is invalid\" error |\r\n\r\n!{width: 548px; border: 1px solid #ccc;}.validation-error@2x.png!\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-09-29T01:27:15Z", "updated_on": "2019-10-02T06:26:15Z"}, {"id": 32167, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Inconsistent border coloring of UI elements?", "description": "- Table lists (list.table), Boxes (.box) and fieldsets (fieldset) border color is #e4e4e4\r\n- Gantt (table.gantt-table) border color is #c0c0c0\r\n- Calendar (table.cal) border color is #d7d7d7\r\n- Separrator after tabs (#content .tabs ul), Footer (#footer) border color is #bbbbbb\r\n- Sidebar (#sidebar), My page box (.mypage-box) border color is #dddddd\r\n- Buttons, input fields, text areas current border color is #cccccc\r\n\r\nQuestion is, was this intended or perhaps more, or even all of those elements could have the same border color?\r\nI am thinking all of them could, except maybe anything that falls under the *input* tag.\r\nI think before any patch is to be proposed, a discussion on which elements could be border-colored the same, would be great.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-09-28T16:17:33Z", "updated_on": "2019-09-28T16:17:33Z"}, {"id": 32166, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Rounded corners on table.gantt-table", "description": "This patch is a follow up to #32014 to add 3px border-radius to gantt table.", "done_ratio": 0, "created_on": "2019-09-28T12:42:55Z", "updated_on": "2019-10-03T12:45:20Z"}, {"id": 32163, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 223595, "name": "Enziin System"}, "category": {"id": 12, "name": "Translations"}, "subject": "Update locales for Vietnamese", "description": "Update locales for Vietnamese", "done_ratio": 0, "created_on": "2019-09-28T02:53:13Z", "updated_on": "2019-10-06T02:13:46Z"}, {"id": 32162, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 308290, "name": "Bernhard Rohloff"}, "category": {"id": 10, "name": "UI"}, "subject": "Improved progress bars for issues and versions", "description": "This patch implements an improved and more versatile version of the bar graphs shown for version and issue progress.\r\nDespite the existing solution it's less restricted to a specific purpose. It's not limited to two stacked bars only and every bar can have it's own tooltip.\r\nThe bars can be styled as stack or next to each other. Label and graph are wrapped in a div which one can give a separate class and styling.\r\nThe progress bars in this patch are animated and have a subtle highlighting effect when they are hovered. The coloring fits the default theme and provides more contrast to the background.\r\n\r\nI'm looking forward for your feedback. :-)\r\n\r\nh3. Issues\r\n\r\n!{width:600px; border: 1px solid darkgrey; float:left; margin-right: 5px;}issue_list.png!\r\n\r\n!{width:600px; border: 1px solid darkgrey;}issue_details.png!\r\n\r\nh3. Versions\r\n\r\n!{width:600px; border: 1px solid darkgrey; float: left; margin-right: 5px;}version_overview.png!\r\n\r\n!{width:600px; border: 1px solid darkgrey;}version.png!", "done_ratio": 0, "created_on": "2019-09-27T15:58:31Z", "updated_on": "2019-09-28T11:41:01Z"}, {"id": 32155, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Fix the overflow problems in project jump", "description": "Some rounded +menu elements+ in Redmine are missing *overflow:hidden;* parameter, which results in corners of child menu elements to stick outside of the parent box which contains them, this results in rounded element, not to look so rounded after all.\r\nThis patch fixes it and in addition, sets border radius to 3px like everywhere else \r\n\r\n!overflowfix3.png! !overflowfix1.png! !overflowfix2.png!\r\n\r\nP.S. 1 ticket per issue, but this was way too small of a change, with micro issues which are kind of related, didn't want to open a separate issue, sorry, but you will insist, I can separate it ;-)\r\n", "done_ratio": 0, "created_on": "2019-09-26T16:12:39Z", "updated_on": "2019-09-26T16:12:39Z"}, {"id": 32154, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 8, "name": "Administration"}, "subject": "Value of custom fields will not be copied when copy project with issues included", "description": "Value of custom fields will not be copied when copy project with issues included.\r\nAll the values of all the custom fields will be blank unless there is default value of that custom field.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "148"}], "created_on": "2019-09-26T15:29:33Z", "updated_on": "2019-09-26T15:29:33Z"}, {"id": 32149, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 393064, "name": "Taine Woo"}, "category": {"id": 8, "name": "Administration"}, "subject": "Project copy failed to copy Issues if Category is set to required: Project#copy_issues: issue #xxx could not be copied: [\"Category cannot be blank\"]", "description": "Project copy failed to copy Issues if Category is set to required, while Members, Issues and Issue categories are all selected for copy.\r\n\r\nError log:\r\nProject#copy_issues: issue #xxx could not be copied: [\"xxx cannot be blank\"]\r\n\r\nTested on 4.0.3", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "148"}], "created_on": "2019-09-26T12:12:27Z", "updated_on": "2019-09-26T12:12:27Z"}, {"id": 32142, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Send notification when a user is created via LDAP on-the-fly user creation", "description": "Redmine has LDAP on the fly user creation feature (see [[RedmineLDAP#On-the-fly-user-creation]]). After the on-the-fly creation, admins have to perform some tasks such as checking if the creation is OK and adding the user to groups or projects.\r\n\r\nCurrently, however, no notification is sent to admins after a user is automatically created, so admins have no chance to notice that the user was created.\r\n\r\nI think some notification should be sent to admins when a user is created via LDAP on-the-fly user creation feature.", "done_ratio": 0, "created_on": "2019-09-26T00:39:21Z", "updated_on": "2019-09-26T00:39:21Z"}, {"id": 32140, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 419186, "name": "Sylvain Faivre"}, "category": {"id": 24, "name": "Documentation"}, "subject": "Document MySQL database migration to utf8mb8", "description": "Feature #31921 included in 4.1.0 sets utf8mb4 as default encoding for new MySQL databases setups.\r\n\r\nIn the description, Marius BALTEANU added :\r\n> I'll try to create later a Wiki page regarding the steps required to migrate and existing installation or at least some useful links.\r\n\r\nThere is no documentation explaining how to migrate yet.\r\n\r\n#21398 includes a migration script, but people in that thread reported failures with the script.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-25T14:47:11Z", "updated_on": "2021-03-19T14:19:25Z"}, {"id": 32132, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Replace gantt primitives with CSS generated vector primitives", "description": "This patch keeps the same exact look as before, just replacing primitives with the same exact vector ones and eliminating the need for external png images.", "done_ratio": 0, "created_on": "2019-09-24T20:36:55Z", "updated_on": "2019-09-26T04:55:29Z"}, {"id": 32116, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 8, "name": "Administration"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Add configured theme to Redmine::Info", "description": "*Administration | Information* \r\n\r\nDisplays various info about system, but doesn't display which theme is currently being used.\r\n\r\n\r\n\r\nEnvironment:\r\n Redmine version 3.4.10.stable\r\n Ruby version 2.3.3-p222 (2016-11-21) [x86_64-linux]\r\n Rails version 4.2.11.1\r\n Environment production\r\n Database adapter Mysql2\r\nSCM:\r\n Subversion 1.9.3\r\n Git 2.7.4\r\n Filesystem \r\nRedmine plugins:\r\n \r\n\r\nIt is important to know which theme is used, because there is many themes available on internet, \r\nand some themes don't show everything, or have bugs.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-23T06:49:13Z", "updated_on": "2021-08-06T21:08:17Z"}, {"id": 32115, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Move search bar and project selector to the top bar", "description": "I made this quick patch more as some kind of preparation for #31353 (you may also add to this ticket to #31353 as related).\r\nI think search bar and project selector elements will make more sense in the top bar, if avatar with user options fly-out will be added to the top bar. That's because top bar will have to become larger, hence to utilize available space more efficiently search bar and project selector might need to be moved to the top bar.\r\n\r\nHow it will look after the patch is applied\r\n\r\n!newtopbar.png!\r\n\r\nTo win back some vertical space, we could also reduce the height of header later on, and even more space could be won if, as Bernhard suggested, we could combine the application header title with project breadcrumbs later on.\r\n\r\nP.S. I didn't mess with floating rules in this patch, so bars are still floating left for now. I think floating could then also be adjusted a bit later.", "done_ratio": 0, "created_on": "2019-09-22T21:51:30Z", "updated_on": "2019-09-23T03:52:54Z"}, {"id": 32114, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Give project list cards the same background like grid cells in many other views", "description": "The color #f6f6f6 is used in other grid cells nearly everywhere else now.\r\nIMHO by giving that same background to project cards as well, they start to feel a little bit less hollow than before.\r\n\r\n!projectcardsbg.png!", "done_ratio": 0, "created_on": "2019-09-22T21:03:02Z", "updated_on": "2019-09-22T23:35:00Z"}, {"id": 32109, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 322398, "name": "Andrey Galkin"}, "category": {"id": 2, "name": "Issues"}, "subject": "Obey sub-task sharing settings on new issue creation", "description": "There have been previous efforts to improve sub-task management, but they lack support for cross-project sharing setting. \r\n\r\nBelow is a patch which has been tested manually. Some extra test case are desired, but I would be unable to help more unfortunately.\r\n\r\n\r\nIndex: app/models/issue.rb\r\n===================================================================\r\n--- app/models/issue.rb (revision 18330)\r\n+++ app/models/issue.rb (working copy)\r\n@@ -1509,7 +1509,18 @@\r\n # Returns a scope of projects that user can assign the issue to\r\n def allowed_target_projects(user=User.current, context=nil)\r\n if new_record? && context.is_a?(Project) && !copy?\r\n- current_project = context.self_and_descendants\r\n+ case Setting.cross_project_subtasks\r\n+ when 'system'\r\n+ current_project = nil\r\n+ when 'tree'\r\n+ current_project = context.root.self_and_descendants\r\n+ when 'hierarchy'\r\n+ current_project = context.hierarchy\r\n+ when 'descendants'\r\n+ current_project = context.self_and_descendants\r\n+ else\r\n+ current_project = nil\r\n+ end\r\n elsif new_record?\r\n current_project = nil\r\n else\r\n\r\ncurl -H 'Content-Type: application/json' \\\r\n -G -K redmine-admin.auth \\\r\n 'https://redmine.example.com/users.json?name=firstname.lastname'\r\n \r\n\r\nit will only return the requested account when the account is active. This means that I have to make two request for @status=1@ and @status=3@ to find a user when I don't know if the account is locked or not :(\r\n\t\r\nI would have suspected that @status=*@ would return all kinds of users, similarly to how it works for [[Rest Issues]] with @status_id=*@, but this is apparently not the case.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-18T16:34:52Z", "updated_on": "2021-02-20T16:44:16Z"}, {"id": 32086, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 416835, "name": "Ninad Patil"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "How can i generate ticket through particular sender ID", "description": "We are having multiple project and need to generate ticket through sender mail id with respect to project\r\nHow can i generate ticket through sender mail id ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-18T07:53:14Z", "updated_on": "2019-09-18T07:53:14Z"}, {"id": 32085, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 8, "name": "Administration"}, "fixed_version": {"id": 155, "name": "5.0.0"}, "subject": "Allow newline as a separator in \"Allowed extensions\", \"Disallowed extensions\", \"Exclude attachments by name\" field in Administration", "description": "Currently, those fields are displayed as textarea but only comma is allowed as a values separator.\r\n\r\nI think newline should be allowed as well because it is very natural to use newline in order to separate values in textarea.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-18T01:32:03Z", "updated_on": "2021-03-26T07:39:34Z"}, {"id": 32080, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Merge as much stylesheets as possible into one file to decrease http requests", "description": "I think application.css, context_menu.css, context_menu_rtl.css, jstoolbar.css, responsive.css, rtl.css, scm.css should be merged.\r\nWhat do you think?", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-17T12:04:50Z", "updated_on": "2019-09-18T18:15:49Z"}, {"id": 32047, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 151490, "name": "Hirofumi Kadoya"}, "category": {"id": 2, "name": "Issues"}, "subject": "Do not delete parent issues that have child issues", "description": "Do not delete parent issues that have child issues please\r\n\r\n--jp--\r\n\u5b50\u30c1\u30b1\u30c3\u30c8\u304c\u3042\u308b\u30c1\u30b1\u30c3\u30c8\u3092\u524a\u9664\u3057\u305f\u5834\u5408\u3001\u5b50\u30c1\u30b1\u30c3\u30c8\u542b\u3081\u3066\u6d88\u3048\u3066\u3057\u307e\u3044\u307e\u3059\r\n\u5b50\u30c1\u30b1\u30c3\u30c8\u304c\u3042\u308b\u89aa\u30c1\u30b1\u30c3\u30c8\u3092\u524a\u9664\u3067\u304d\u306a\u3044\u3088\u3046\u306a\u5236\u9650\u3092\u304b\u3051\u3066\u3082\u3089\u3048\u307e\u305b\u3093\u304b\uff1f\r\n\uff70\uff70\uff70", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-09-11T07:19:43Z", "updated_on": "2019-09-12T07:39:49Z"}, {"id": 32042, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 14, "name": "Custom fields"}, "subject": "Show in summary", "description": "Add \"Show in summary\" when creating/editing custom field.\r\n\r\nShow in summary would show custom field in summary (report) which is accessible via issues sidebar.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-10T09:23:50Z", "updated_on": "2019-09-10T09:23:50Z"}, {"id": 32040, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 415755, "name": "Joshua Jobin"}, "category": {"id": 28, "name": "LDAP"}, "subject": "Create LDAP Type Custom Field", "description": "We use Redmine with our LDAP server. The on-the-fly user creation is a great feature.\r\n\r\nI am wondering if we could also add an LDAP format custom field.\r\nThe problem we are encountering, is that in order for us to connect an issue with a person they would have to sign in to Redmine to create their User object. It would be nice to be able to relate an Issue to the LDAP profile (by searching by email for example), so that when they do eventually login to Redmine they would see all of their related issues.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-09T17:03:26Z", "updated_on": "2019-09-09T17:03:26Z"}, {"id": 32030, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 332, "name": "Go MAEDA"}, "assigned_to": {"id": 332, "name": "Go MAEDA"}, "category": {"id": 43, "name": "Project settings"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Show Gravatar icons in the Members tab in the project setting", "description": "It makes easier to distinguish users. In addition, it improves consistency. Users page in Administration already shows Gravatar icons.\r\n\r\n!{width: 1024px; border: 1px solid #ccc;}.members-tab@2x.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-08T08:10:37Z", "updated_on": "2020-01-04T02:57:24Z"}, {"id": 32029, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Replace gantt and calendar tooltips with jquery tooltips", "description": "I think jquery tool-tips should also be used as gantt and calendar tool-tips which display brief information when rolling cursor over issue lines of the timeline/calendar cells, because currently those kind of tool-tips in gantt/calendar aren't designed to spawn on the left, right, below or over the issue lines, depending on which side a free space available, so the tool-tip wouldn't end up half cut outside of the window.\r\nI tested the way jquery tool-tips are displayed and saw that they actually support that kind of smart behavior.\r\n\r\n!http://www.redmine.org/attachments/download/23810/gantttooltip.png!\r\n\r\nPatch is to be posted.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-07T21:21:56Z", "updated_on": "2020-02-29T12:19:53Z"}, {"id": 32021, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Give project description, homepage and custom fields an own box too", "description": "This patch wraps project information like description, homepage, custom fields in the box if they exist.\r\nCouple of very minor problems with this patch, but aren't catastrophic to not consider proceeding:\r\n\r\n1. If a custom field exists and assigned to the project, the box will be displayed even if it's in the unset state (aka selected empty), I couldn't figure out how to quickly check length of the fields to make suitable logic.\r\n2. This will need localization for all languages in the future, perhaps Information isn't suitable label title as well, and something more universal might need to be found.\r\n\r\nOn the other hand, now the per project views feel more like something complete and consistent.\r\n!infobox.png!", "done_ratio": 0, "created_on": "2019-09-04T19:04:04Z", "updated_on": "2019-09-17T10:15:42Z"}, {"id": 32018, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "Visually consolidate project selector and the popup box with the projects", "description": "!preview.png!", "done_ratio": 0, "created_on": "2019-09-04T17:14:43Z", "updated_on": "2019-09-04T17:16:44Z"}, {"id": 32017, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "subject": "A much happier blue palette for the header (#header + #top-menu)", "description": "This patch also makes search bar + project selector \"camouflage\" a bit until clicked.\r\n!newheader.png!\r\n!focusedsearchbar.png!\r\n!focusedselector.png!", "done_ratio": 0, "created_on": "2019-09-04T17:11:15Z", "updated_on": "2019-09-06T19:03:59Z"}, {"id": 32016, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 4, "name": "Anonymous"}, "category": {"id": 10, "name": "UI"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Rounded coreners on roadmap's progress bar", "description": "Same motivation as for #32013", "done_ratio": 0, "created_on": "2019-09-04T17:01:20Z", "updated_on": "2019-10-06T09:04:27Z"}, {"id": 32009, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 412895, "name": "Jannis H\u00fcbl"}, "category": {"id": 2, "name": "Issues"}, "subject": "Allow to directly edit Issues", "description": "Hi, \r\n\r\nthanks for this amazing application, we introduced redmine in our company and it works great sofar. But people are complaining about the following:\r\n\r\nBefore editing or writing a comment they must press edit. So I am thinking about: would it not make sense to allow to automaticly enter the edit mode?\r\n\r\nI guess this would require to make a switch in the show template, and showing the form instead of the Values. \r\n\r\nSorry if this was already discussed earlier, but I could not find something regarding this. \r\n\r\nCheers, \r\n\r\njannis", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-04T10:21:54Z", "updated_on": "2019-09-04T10:21:54Z"}, {"id": 32005, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 1329, "name": "Ewan Makepeace"}, "category": {"id": 2, "name": "Issues"}, "subject": "Better Category Handling", "description": "One of my central projects had become hard to manage so I split out about 25% of the functionality into a new project. As I set about moving 100's (and soon 1000's) of tasks to the new project I realised a major drawback of my approach - all the category information is lost.\r\n\r\n# I would like an option to copy a project and optionally copy all its categories.\r\n# I would also like this: #23066\r\n\r\nThis issue is related to, but does not duplicate #5358 as my projects are not necessarily subprojects.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-04T08:01:59Z", "updated_on": "2019-10-07T12:50:07Z"}, {"id": 32003, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 9, "name": "Confirmed"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 362529, "name": "Yuichi HARADA"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "Project copy always send email notifications ignoring \"Send email notifications during the project copy\" option", "description": "When copying a project in the projects list(Administration > Projects), you can disable sending an email by unchecking the \"Send email notifications during the project copy\" checkbox.\r\nHowever, even if this checkbox is unchecking, email notifications are sent.\r\n\r\n!{width:50%;border:1px solid #ccc;}ScreenShot_2019-09-04.png!", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "99"}], "created_on": "2019-09-04T02:00:21Z", "updated_on": "2019-09-13T09:27:34Z"}, {"id": 32000, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 25010, "name": "Heiko Robert"}, "category": {"id": 9, "name": "Email notifications"}, "subject": "abstraction layer for notifications", "description": "Redmine provides an email notification feature. These days email is only one channel for notifications. Many organisations switch to different messaging based architectures to notify users (chat, message hubs, ...) and phase out email.\r\nUnfortunately redmine has no abstraction layer for creating the notification. Instead the email notification is rendered directly into an rfc mail body. This makes it very hard to implement plugins sending the same content to other systems since the plugin has to code the same thing again. Even worse: when using other plugins like \"checklist\" these notifications are not seen by any solution trying to route the notifiation to other channels.\r\n\r\nIn short: Please refactor notifications to an abstract implementation where mail is only one channel and which may support different markup outputs like html, md, plain text. Plugins should be able to hook in to add more notification events/contents or consume these events.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-03T09:15:56Z", "updated_on": "2019-09-03T09:15:56Z"}, {"id": 31996, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 414440, "name": "vincent vega"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Auto assign new user to project by email issue", "description": "I have a bunch of projects with different email adresses to receive issues from unknown users.\r\nSo, some man 'Joe' send an email to 'support@example.com' and new user 'Joe' created with new issue in project 'Example.com'\r\nHow to add Joe automatically to project?\r\nIf Joe send email to 'support@foo.bar' need to make him a part of 'Foo' project, etc\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-09-02T13:57:00Z", "updated_on": "2019-09-02T13:57:00Z"}, {"id": 31987, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 3, "name": "Patch"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 21945, "name": "Kuniharu AKAHANE"}, "category": {"id": 3, "name": "SCM"}, "fixed_version": {"id": 32, "name": "Candidate for next major release"}, "subject": "Add rake task which synchronize all revisions in repositories related with all active projects", "description": "Hi, there.\r\n\r\nThank you JPL and all who contributed to improving Redmine such an excellent software.\r\n\r\nI wrote a rake task patch changesets.rake .\r\nThis rake task synchronize all revisions in repositories which related with all active projects.\r\nIt is useful when some user mistake to write commit-comment for repository. \r\n\r\n* Use Case\r\n## Refs # <- forgot to write issue_id and/or comment.\r\n## Refs #xxxxx <- wrong issue_id\r\n## <- forgot to write commit \r\n\r\n\r\nI know Redmine has a feature to add a reference between issue and commit on web pages.\r\nBut it does not cover all case, and a bunch of mistakes by a thousand of users on a hundred repositories.\r\nAlso when i disconnect and reconnect between active project and repository, those additional reference above will be lost.\r\n\r\nEven i fix wrong comments on repository, but it will not sync to redmine repository tab and issue reference.\r\nSo, i think it would be nice if i have a synchronize rake task.\r\n\r\n( @kou assisted me for writing this patch. Thanks @kou. )", "done_ratio": 0, "created_on": "2019-08-31T05:53:13Z", "updated_on": "2021-03-28T14:58:41Z", "closed_on": "2019-06-03T14:56:45Z"}, {"id": 31986, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 412290, "name": "Adauto Serpa"}, "category": {"id": 13, "name": "Time tracking"}, "subject": "Error selecting issues between dates after upgrading redmine 2.3.2 to 4.0.x", "description": "\r\n\r\nHi,\r\n\r\nI'm having problem to upgrade redmine 2.3.2 to 4.0.\r\n\r\nAfter the Redmine update time entry reports do not bring the times entered on the corresponding dates.\r\n\r\nExample Task list(dd/mm/yyyy):\r\n\r\nTask 22572 executed on 01/07/2019\r\nTask 22566 executed on 01/07/2019\r\nTask 22204 executed on 01/07/2019\r\nTask 22573 executed on 01/07/2019\r\nTask 22584 executed on 02/07/2019\r\nTask 18257 executed on 02/07/2019\r\nTask 22585 executed on 02/07/2019\r\nTask 22584 executed on 03/07/2019\r\nTask 22117 executed on 03/07/2019\r\nTask 22177 executed on 04/07/2019\r\nTask 22584 executed on 04/07/2019\r\n\r\nSelecting dates between 01/07/2019 and 03/07/2019\r\nthe result I have is(dd/mm/yyyy):\r\n\r\nTask 22584 executed on 02/07/2019\r\nTask 18257 executed on 02/07/2019\r\nTask 22585 executed on 02/07/2019\r\nTask 22584 executed on 03/07/2019\r\nTask 22117 executed on 03/07/2019\r\nTask 22177 executed on 04/07/2019\r\nTask 22584 executed on 04/07/2019\r\n\r\nAs we can see redmine does not list the tasks of day 01 and lists the tasks of day 04 that should not be listed.\r\nI suspected at first that it could be the database version, as it had migrated to MySQL version 8, but the problem persists in version 5.7.\r\n\r\nTo list the tasks of day 01 I have to specify the date of the day before 31.\r\nVery strange this behavior of redmine.\r\n\r\nIf I create issues in a new database, Redmine behaves correctly.\r\n\r\nDoes anyone have any idea how or why this problem occurs?\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-08-30T17:14:32Z", "updated_on": "2019-09-12T17:25:35Z"}, {"id": 31972, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 259873, "name": "Mizuki ISHIKAWA"}, "category": {"id": 10, "name": "UI"}, "subject": "An empty group_count badge is displayed when grouped with created_on", "description": "Reproduction procedure\r\n* Use MySQL\r\n* \"Time zone data\":https://dev.mysql.com/doc/refman/5.6/en/mysql-tzinfo-to-sql.html is not loaded\r\n* Change user language from UTC to something else\r\n* Group by created_on at issues/index\r\n\r\nWhen the above conditions are met, the group_count badge will be displayed as empty as shown in the screenshot.\r\n!{width: 500px; border: 1px solid #ccc}ScreenShot-2019-08-29-10.49.27.png!\r\n\r\nIt doesn't matter if group_count is nil because MySQL doesn't get group_count if it doesn't load time zone data.\r\nThe problem is that an empty badge is displayed at that time.\r\n\r\nBadge should also be hidden if group_count is not successfully acquired(like \"timelog\":http://www.redmine.org/projects/redmine/repository/entry/trunk/app/views/timelog/_list.html.erb#L25).\r\n\r\nThis is a problem with trunk.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-08-29T02:09:34Z", "updated_on": "2019-09-11T00:49:09Z"}, {"id": 31968, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 3, "name": "Resolved"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411935, "name": "Amit Mehendale"}, "category": {"id": 19, "name": "Attachments"}, "subject": "MIME Content Type is not properly handled while attaching the files", "description": "Recently upgraded to 4.0.4. While doing the Information security testing, Team raised a vulnerability\r\n*\"The application does not validate the content type of file being uploaded. This would enable an adversary to upload a malicious file onto the server.\"*\r\n\r\nIf I change the extension of a file from *.com* to *.pdf*, Redmine allows file upload in issues as attachment and stores contenttype as \"*application/pdf*\" in table.\r\n\r\nDue to this issue we are unable to roll out new version.\r\n\r\nUrgent help required.\r\nThanks", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-08-28T06:19:20Z", "updated_on": "2019-08-28T12:41:58Z"}, {"id": 31957, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 413302, "name": "strhuan blomquist"}, "category": {"id": 9, "name": "Email notifications"}, "subject": " ActionMailer need to limit how many maximum connections it opens ", "description": "Microsoft office 365 smtp server has made some changes that will cause\r\nthis error message\r\n\r\nEmail delivery error: 432 4.3.2 STOREDRV.ClientSubmit; sender thread limit exceeded \r\nbasically \r\n\r\nNew throttling limit for concurrent connections that submit messages\r\nThe service has various limits to prevent abuse and to ensure fair use. An additional limit is being added. Under the new limit, up to three concurrent connections are allowed to send email messages at the same time. If an application tries to send more than three messages at the same time by using multiple connections, each connection will receive the following error message:\r\n\r\n432 4.3.2 STOREDRV.ClientSubmit; sender thread limit exceeded\r\n \r\nhttps://docs.microsoft.com/en-us/exchange/troubleshoot/send-emails/smtp-submission-improvements\r\n\r\nother projects have worked around it by introducing a \r\nmaxConnections: 3 limitation to there mailers\r\nex \r\n\r\nhttps://support.sisense.com/hc/en-us/community/posts/360029660673--Custom-SMTP-Email-Server-Solution-for-Outlook365-error-432-4-3-2-STOREDRV-ClientSubmit-sender-thread-limit-exceeded-\r\n\r\n\r\nmy setup \r\n\r\nEnvironment:\r\n Redmine version 4.0.2.stable\r\n Ruby version 2.6.1-p33 (2019-01-30) [x86_64-linux]\r\n Rails version 5.2.2\r\n Environment production\r\n Database adapter Mysql2\r\n Mailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\n Mailer delivery smtp", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "146"}], "created_on": "2019-08-27T08:44:55Z", "updated_on": "2019-08-28T07:52:35Z"}, {"id": 31956, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 400484, "name": "David Dole\u017eal"}, "category": {"id": 2, "name": "Issues"}, "subject": "All members of project as watchers", "description": "Hi,\r\nafter discussion I post here my idea for patch / plugin / implement to the core. \r\n\r\n*IDEA:*\r\nAll projects have define members\r\n\r\n1) When I create new issue, all members of project will be set as watchers\r\n2) When I change project from one to another, all members from new project will be add = for example: I have issue in Project A. Dave, Mark, George and Diana are members = watchers of Project A. I edit an issue in project A and change project to Project B. Only Frank and Peter are members = watchers of Project B. Result is: Dave, Mark, George, Diana, Frank and Peter are set as watchers for issue, which move from Project A to Project B\r\n\r\n*WHY:*\r\nIf you have many projects, where is few people (from 4 to 10 for example), it's really annoying everytime clicking user by user to define them as watchers. Solution by groups, when you click on group as watcher is OK, but is manual - so what if operator forget? This would be automatic.\r\n\r\n*WHERE TO SETUP:*\r\nProject > Setting > Information > \"Do you want all members define as watchers for issues?\" YES/NO\r\nIt will be easy to manage and all will recognize what does it mean.\r\n\r\nUnfortunetly I'm not able to develop it myself. Let me know, if you want more discussion about this idea.\r\n\r\nWith best regards\r\nDavid", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-27T08:42:25Z", "updated_on": "2019-08-27T08:42:25Z"}, {"id": 31953, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 10568, "name": "Robert Schneider"}, "category": {"id": 11, "name": "Projects"}, "subject": "Show creation date in project overview", "description": "In the administration area, the list of projects exposes the creation date, i.e. this information does already exist for each project. A project contains a creation date.\r\n\r\nCould this little date be shown anywhere on the project overview page, please? Not editable or so. Just show this information. Because if one is not an administrator the creation date of the project cannot be figured out.\r\n\r\nOptionally, the creation date could be shown an the project overview page. But I guess you don't like to populate that page with any additional information, as long as #29482 is not realized.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-27T07:11:25Z", "updated_on": "2019-08-27T07:11:25Z"}, {"id": 31936, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 412386, "name": "Rahul Patil"}, "category": {"id": 19, "name": "Attachments"}, "subject": "Cannot download issue-attachments that contains one or more \u201c+\u201d (Plus Sign) characters ", "description": "To recreate it - just create an Issue, create a text file with any name containing \"+\" (plus sign) e.g. \"Test+File.txt\" and attach that file to the issue and submit. \r\nAfter that open that issue, and try to download that file. It will show \"404 - File or directory not found.\" error. \r\nThen edit the attachments - rename the file to \"Test_File.txt\", and then try downloading it - it will get downloaded without any issues.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-08-22T12:16:38Z", "updated_on": "2019-08-22T12:43:47Z"}, {"id": 31932, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 309040, "name": "Razmig Varsam"}, "category": {"id": 43, "name": "Project settings"}, "subject": "Add Sponsor in the Group Results By Drop Down for Custom Queries", "description": "Is it possible to add the Sponsor in the Group Results By drop down section in the custom query section? Right now, that option is not there and I find that it's beneficial to sort tickets by Sponsor by not having to export to Excel or Google Sheets to do so.\r\n\r\nI know that you can more than one Sponsor per ticket so I don't know if that's the issue.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-08-21T16:22:24Z", "updated_on": "2019-08-21T16:22:24Z"}, {"id": 31930, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 412304, "name": "Will Tsus"}, "category": {"id": 32, "name": "REST API"}, "subject": "REST API for Versions (roadmap) Relationship and percentage", "description": "It would be great to have versions relationship and percentage available via the REST API.\r\n\r\nExample: GET /versions/172/relations.xml", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-20T20:37:42Z", "updated_on": "2019-08-20T20:37:42Z"}, {"id": 31912, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 966, "name": "Thomas Stark"}, "category": {"id": 2, "name": "Issues"}, "subject": "ActionView::Template::Error (undefined method `name' for nil:NilClass):", "description": "Got this error and didn't know, what to do.\r\n\r\n\r\n 85: \r\n 86: <%=l(:field_description)%>
\r\n 87: \r\n 88: <%= textilizable @issue, :description, :attachments => @issue.attachments %>\r\n 89:
\r\n 90: \r\nEnvironment:\r\n Redmine version 3.4.4.stable\r\n Ruby version 2.5.1-p57 (2018-03-29) [x86_64-linux-gnu]\r\n Rails version 4.2.10\r\n Environment production\r\n Database adapter Mysql2\r\nSCM:\r\n Git 2.17.1\r\n Filesystem \r\nRedmine plugins:\r\n no plugin installed\r\n ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "134"}], "created_on": "2019-08-16T05:31:26Z", "updated_on": "2019-08-16T11:04:36Z"}, {"id": 31908, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411886, "name": "Vladimir Arkhipov"}, "subject": "Do not load all projects in project jump box", "description": "In our installation we have more than 3000 projects. All of these projects are loaded in browser on each page every time you open any url and 90% of page content is html with project names. We use Favourite Projects Plugin https://www.redmine.org/plugins/favorite_projects which allows to reduce number of projects loaded in project jump box. But in Redmine versions 3.4 and 4.1 there are many great improvements of standard functionality (#23310, #31355) and only one little thing is missing. \r\n\r\nI think that projects should be loaded in project jump box dynamically when user typing in search box. By default you can show only N first projects or don't show anything (only bookmarks and recently used projects from #31355). ", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-15T20:07:21Z", "updated_on": "2019-08-15T20:07:21Z"}, {"id": 31900, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411668, "name": "Gerhard Kronstorfer"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "Problem with tickets issued by rdm-mailhandler on redmine 4.0.4", "description": "Hi,\r\n\r\nmy Installation on a CentOS 7 Servere:\r\n\r\nEnvironment:\r\nRedmine version 4.0.4.stable\r\nRuby version 2.6.2-p47 (2019-03-13) [x86_64-linux]\r\nRails version 5.2.3\r\nEnvironment production\r\nDatabase adapter Mysql2\r\nMailer queue ActiveJob::QueueAdapters::AsyncAdapter\r\nMailer delivery smtp\r\nSCM:\r\nGit 1.8.3.1\r\nFilesystem\r\nRedmine plugins:\r\nredmine_checklists 3.1.16\r\nredmine_ckeditor 1.2.2\r\n\r\nWhen I send the following Mail to redmine:\r\n\r\n\r\nThis is a test\r\n--\r\n\r\nMit freundlichen Gr\u00fc\u00dfen / With best regards\r\ni.V. Ing. Gerhard Kronstorfer\r\nAbteilungsleiter EDV\r\n \r\n\r\nI get the following ticket (created by rdm-mailhandler):\r\n\r\n\r\nThis is a multi-part message in MIME format.\r\n--------------5CDD95DC82FDEC6C69D3183F\r\nContent-Type: text/plain; charset=utf-8; format=flowed\r\nContent-Transfer-Encoding: 8bit\r\n\r\nThis is a test\r\n--\r\n\r\nMit freundlichen Gr????en / With best regards\r\ni.V. Ing. Gerhard Kronstorfer\r\nAbteilungsleiter EDV\r\n \r\n\r\nYou can see that there are four additional lines at the start of the ticket which shouldn't be there and that there is a problem with the special characters in the signature.\r\n\r\nIf I send the same message to my old Installation (redmine 3 on Centos 6) everything ist fine.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": "Cant reproduce"}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-08-14T17:18:26Z", "updated_on": "2019-09-04T01:35:45Z"}, {"id": 31886, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 306584, "name": "jwjw yy"}, "subject": "There is no limitation for the content of news ", "description": "\r\nIn my deployed Redmine, I tried to create a news with more than 65536 characters. And I got this as attached. There should be a constraint in new.rb, such as:\r\n\r\nvalidates_length_of :description, maximum: 65535\r\n \r\neven more, in the news/_form.html, \r\n\r\nmaxlength => 65535 should be added to the textarea. I have attached the patch.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": ""}], "created_on": "2019-08-13T05:35:43Z", "updated_on": "2019-08-13T05:41:59Z"}, {"id": 31882, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 5107, "name": "Aleksandar Pavic"}, "category": {"id": 41, "name": "Issues workflow"}, "subject": "Raise maximum length of issue status name", "description": "Currently on issue_statuses table, length of name is varchar 30, however it's not enough for issue status name in many cases, and different languages. \r\n\r\nPlease raise it to varchar 250 or some other longer value.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-12T15:26:14Z", "updated_on": "2019-08-29T14:41:46Z"}, {"id": 31872, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 10, "name": "Needs feedback"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 127712, "name": "sergio R"}, "category": {"id": 41, "name": "Issues workflow"}, "subject": "Status Transitions are not saved", "description": "Using redmine 3.4.11 with MSSQL\r\n\r\nWhen I try to change status transitions they are not saved.\r\nOnce you enable a transition it stays enabled forever.\r\nEven if I try to unchecked it and save it, it does not work.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "150"}], "created_on": "2019-08-09T15:58:40Z", "updated_on": "2019-08-12T14:11:02Z"}, {"id": 31864, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411127, "name": "Adrian Fey"}, "category": {"id": 32, "name": "REST API"}, "subject": "Issue/TimeEntry API does not report root_id", "description": "I would expect, that the Issues API exposes all fields, which I can find in the corresponding tables when accessing the database directly.\r\n\r\nFor my current project I am missing the root_id field, which I require to build a report which indents child issues.\r\n\r\nUse case:\r\nI want to make a report about all Tickets, that have been worked on during a time period.\r\nCurrently my approach would be:\r\n# Get all TimeEntrys with Spent_on in my timeframe\r\n# Get all Issues for those TimeEntrys\r\n# Truncate all Issues where issue_id <> root_id (can't be done currently, because information is not provided via API)\r\n# For all the root issues then again grab all children and build a tree\r\n\r\nThis by far isn't ideal request count wise, but everything else would require to have the root_issue_id information also on TimeEntrys.\r\n\r\nIf TimeEntrys would also provide root_id of the issue, then I could simply:\r\n# Get all TimeEntrys with Spent_on between my timeframe\r\n# Concat all root_ids to a comma separated string and retrieve all root issues in one request\r\n# recursively grab the children, if existing, and build the tree\r\n\r\nAn even better approach might be to extend the Api for Issues to Include TimeEntrys and vice versa.\r\nThat way one would be very flexible in making reports, which depend on time_spent during periods.\r\n\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-07T15:14:03Z", "updated_on": "2019-08-07T15:14:03Z"}, {"id": 31863, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 2, "name": "Feature"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 411125, "name": "G.L. E.I.D"}, "category": {"id": 32, "name": "REST API"}, "subject": "Added in the task display of the list of identifiers of subtasks. Rest api GET /issues.[format](json, xml)", "description": "Welcome, I recently started using redmine via rest api, when requesting GET /issues.[format] redmine sends a list of tasks, each task contains a parent ID, if any, but no child ID, which is not very convenient. I fixed the code. Now the list of subtasks ' IDs is also displayed in the tasks during the query.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}], "created_on": "2019-08-07T14:21:58Z", "updated_on": "2020-11-25T12:44:00Z"}, {"id": 31838, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 410551, "name": "Tomis\u0142aw Kity\u0144ski"}, "category": {"id": 1, "name": "Wiki"}, "subject": "Improper parsing of wiki links", "description": "In case where wiki link is followed by opening parenthesis, it seems like parsing goes wild. For instance this sequence:\r\n\r\n\r\nOne two [[three|The Three]] (four) five.\r\n \r\n\r\nshould produce this output:\r\n\r\n> One two _The Three_ (four) five.\r\n\r\nbut it produces this:\r\n\r\n> One two _[three|The Three]_ five.\r\n\r\nIt actually acts, as external link, where \"four\" is the URL, but:\r\n* there is a space between last closing square bracket and opening parenthesis (I would understand this behavior when there would be no space),\r\n* square brackets are doubled, but external link mode took precedence over wiki link.\r\n\r\nCurrently one needs to escape opening parenthesis with backslash to force parser to see such a sequence as wiki link, not external link. IMO this looks like a glitch.\r\n", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "145"}], "created_on": "2019-08-01T17:49:03Z", "updated_on": "2019-08-07T00:22:03Z"}, {"id": 31834, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 146724, "name": "Francesco Moro"}, "category": {"id": 29, "name": "Email receiving"}, "subject": "redmine:email:receive_imap broken with ruby < 1.6.3 and Google Imap", "description": "Hello,\r\n\r\nreferring to this message I opened in the forum\r\nhttp://www.redmine.org/boards/2/topics/57726\r\n\r\nHello,\r\n\r\nI'm on the latest Redmine 4.0.4 on my Ubuntu 18.04;\r\nRails 5.2.3\r\nRuby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]\r\nApache/2.4.29 (Ubuntu)\r\nPhusion Passenger 5.0.30\r\n\r\nSince a couple of days I've always used to generate new Issues from email, fetching from several gsuite (gmail) accounts.\r\nHere is a sample of one of my many crons:\r\n\r\n\r\n/8 * * * * /usr/local/bin/rake -f /usr/share/redmine/Rakefile redmine:email:receive_imap RAILS_ENV=\"production\" host=imap.gmail.com port=993 username=my_email@mydomain.com password=my_password ssl=1 folder=issues_folder project=my_project priority=Normal tracker=MyTracker move_on_success=read move_on_failure=failed unknown_user=create default_group=default_group no_permission_check=1\r\n \r\n\r\nIt has been working since a couple of years but starting from Wednesday (probably) it stopped.\r\nHere is the error I get with a --trace:\r\n\r\n\r\n** Invoke redmine:email:receive_imap (first_time)\r\n** Invoke environment (first_time)\r\n** Execute environment\r\n** Execute redmine:email:receive_imap\r\nrake aborted!\r\nOpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate)\r\n/usr/lib/ruby/2.5.0/net/protocol.rb:44:in `connect_nonblock'\r\n/usr/lib/ruby/2.5.0/net/protocol.rb:44:in `ssl_socket_connect'\r\n/usr/lib/ruby/2.5.0/net/imap.rb:1531:in `start_tls_session'\r\n/usr/lib/ruby/2.5.0/net/imap.rb:1092:in `initialize'\r\n/usr/share/redmine-4.0.4/lib/redmine/imap.rb:30:in `new'\r\n/usr/share/redmine-4.0.4/lib/redmine/imap.rb:30:in `check'\r\n/usr/share/redmine-4.0.4/lib/tasks/email.rake:121:in `block (4 levels) in '\r\n/usr/share/redmine-4.0.4/app/models/mailer.rb:612:in `with_synched_deliveries'\r\n/usr/share/redmine-4.0.4/lib/tasks/email.rake:120:in `block (3 levels) in '\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `block in execute'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `each'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `execute'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/task.rb:214:in `block in invoke_with_call_chain'\r\n/usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/task.rb:194:in `invoke_with_call_chain'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/task.rb:183:in `invoke'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:160:in `invoke_task'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `block (2 levels) in top_level'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `each'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `block in top_level'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:125:in `run_with_threads'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:110:in `top_level'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:83:in `block in run'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:186:in `standard_exception_handling'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/lib/rake/application.rb:80:in `run'\r\n/var/lib/gems/2.5.0/gems/rake-12.3.3/exe/rake:27:in `'\r\n/usr/local/bin/rake:23:in `load'\r\n/usr/local/bin/rake:23:in `'\r\nTasks: TOP => redmine:email:receive_imap\r\n \r\n\r\nI found out the problem has been patched in ruby 1.6.3\r\nhttps://github.com/ruby/openssl/issues/238\r\n\r\nmaybe redmine should be \"fixed\"? In my ubuntu 18.04 I needed a manual patch (ruby 2.6.3 not available as update, and I did not want to install it manually)\r\n\r\nif you need further information just ask.\r\nthank you", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-07-31T13:52:21Z", "updated_on": "2019-07-31T13:52:21Z"}, {"id": 31831, "project": {"id": 1, "name": "Redmine"}, "tracker": {"id": 1, "name": "Defect"}, "status": {"id": 1, "name": "New"}, "priority": {"id": 4, "name": "Normal"}, "author": {"id": 410375, "name": "Tibinko H"}, "fixed_version": {"id": 33, "name": "Candidate for next minor release"}, "subject": "Back url parse in validation", "description": "Hello,\r\n\r\nfor example on issues screen, when you apply filters, it generates an url containing:\r\n\r\nutf8=\u2713\r\n \r\n\r\nBecause of this bulk_edit (for instance) is unable to redirect back to this url.\r\nThe reason is a function in application_controller.rb - validate_back_url\r\n\r\n\r\nURI.parse(back_url) is unable to parse the special character mentioned above.\r\n \r\n\r\nThe quicke workaround would be\r\n\r\nURI.parse(URI.encode(back_url))\r\n \r\nbut i am not sure that is sufficient.", "done_ratio": 0, "custom_fields": [{"id": 2, "name": "Resolution", "value": ""}, {"id": 4, "name": "Affected version", "value": "151"}], "created_on": "2019-07-31T10:04:23Z", "updated_on": "2019-08-01T08:49:53Z"}], "total_count": 500}