Activity
From 2020-04-15 to 2020-04-17
2020-04-17
-
23:02 Patch #30919: Group Issues Custom Fields - (Form like Issues)
- Yuri Azanov wrote:
> Can you make diff patch for redmine 4.1.0 please?
Here it is. -
17:20 Feature #1385: Script for import from JIRA
- Hi guys!!! I need some help, please...
I had problems running scripts to migrate Jira (Cloud version) to Redmine 4.0.5 (from Bitnami) over Windows Server 2016 and SQL-Server 2017 database. When I ran "export" script, I get this (--tra... -
14:17 Feature #16195: Role with Issue visibility Permission as "View Issues within current users' group"
+1 Great feature.-
13:50 Defect #33303 (Closed): CustomField float 2.000,55 instead of 2,000.55
- Hello,
I have created a custom field. Selected as a floating point number.
If I enter a number in the field then I get an error message that the number is not accepted. I want to enter the number in this format *2.000,55*. But that o... -
11:24 Feature #33302 (New): What about the editor for "%Done" be a numeric editor with a spinbox
- Currently it is a combobox with 11 options: 0%, 10%, ..., 100%
Recenctly I'm reading a book called "mini habit", and got a demand that updating "%Done" a little for usual.
Thanks -
10:02 Feature #24763: Force SSL when Setting.protocol is "https"
- Go MAEDA wrote:
> Marius BALTEANU wrote:
> ...
These are valid points, even if these type of tests should not be made on "production" mode and even in intranet they should use https. Some companies are using self signed certificates wh... -
08:29 Feature #24763: Force SSL when Setting.protocol is "https"
- My original post, is that changing from http to https in settings, does nothing, you don't get redirected to https...
We can either remove that setting, since it doesn't do anything...
Or make it work, by having it set force_ssl = ... -
06:54 Feature #24763: Force SSL when Setting.protocol is "https"
- Marius BALTEANU wrote:
> I agree that Redmine default settings should contain better security settings. For now, I propose to enforce SSL on production environment. "Let's Encrypt":https://letsencrypt.org/ it's a good option for those w... -
06:42 Feature #33301 (Closed): Add option to include enabled issue custom fields in projects#show API response
- This is helpful in case the custom fields of a project are to be manipulated via the API - you have to know the currently assigned fields in order to update that list.
2020-04-16
-
21:23
Defect #33299 (Closed): "404 error" issue
- Hi,
I just installed Redmine (last version) on my Ubuntu 18.04 server.
After creating my first project, I have an "404 error" when accessing to issues, Gantt or calendar page, anybody could help?
Thanks -
21:07 Patch #33298: Bulgarian translation
- I forgot to set category Translations, I'm sorry.
-
21:05 Patch #33298 (Closed): Bulgarian translation
- Bulgarian translation of
* error_attachments_too_many
* error_bulk_download_size_too_big
* setting_bulk_download_max_size
* label_download_all_attachments
Related to #7056, #18555 -
20:17 Patch #30919: Group Issues Custom Fields - (Form like Issues)
- Can you make diff patch for redmine 4.1.0 please?
-
19:17 Feature #24763: Force SSL when Setting.protocol is "https"
- @Marius
that code enforces SSL always, what I'm alluding is that if you choose in settings to use HTTPS,
then force_ssl = true should be set...
Unfortunately I can't write code and test, at the moment... -
17:57 Feature #24763: Force SSL when Setting.protocol is "https"
- I agree that Redmine default settings should contain better security settings. For now, I propose to enforce SSL on production environment. "Let's Encrypt":https://letsencrypt.org/ it's a good option for those who don't want to buy a cer...
-
18:08 Feature #6641: creating project-specific activities
- This is related to #4077.
"System Activity" (enumeration_system_activity in locales) is baffling when there's no other kind. -
18:05 Defect #33273 (Reopened): Total estimated time column shows up as decimal value regardless of time setting
- Attached the patch to back port to 4.0.8 as well.
-
17:37 Feature #33296: Load default custom queries when running redmine:load_default_data rake task
- Nice idea.
Maybe it's a good idea to add some default queries on a fresh install and not only as default data? -
15:00 Feature #33296: Load default custom queries when running redmine:load_default_data rake task
- +1 for the integration of this proposal. A few notes nevertheless:
* Wouldn't such default custom queries be useful also for the other @Query@ subclasses?
* Regarding your comment that ??"[...] Currently, it is a bit difficult for begi... -
13:40 Feature #33296 (Closed): Load default custom queries when running redmine:load_default_data rake task
- redmine:load_default_data loads various kinds of default data such as roles, permissions, issue statuses, trackers, workflows, and enumerations, to a fresh installation of Redmine. These default data will save users time and allow them t...
-
14:28 Feature #33297 (New): Sort git tags in descending order
- 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 t...
-
13:54 Feature #24681: Syntax highlighter: replace CodeRay with Rouge
- This broke Java syntax again. :(
https://github.com/rouge-ruby/rouge/pull/1414
-
04:48 Feature #13919: Mention user on issues and wiki pages using @user with autocomplete
- De Lo wrote:
> In Gitlab, when you mention someone, they gets automatically subscribed to the thread and receives all further updates on the issue. We use that behaviour in our company and it very well suits our needs.
> ...
I think th... -
04:47 Feature #13919: Mention user on issues and wiki pages using @user with autocomplete
- Marius BALTEANU wrote:
> Thanks Mizuki for the work made on top of my patch. I took a look over your patches and I'm not sure why all those changes made to @ApplicationHelper#parse_redmine_links@ and @User@ are needed, most probably I m... -
04:04 Patch #18419: Copy news along with the project
- Updated the patch for the latest trunk.
2020-04-15
-
19:22 Patch #32054: Add test for 4 byte characters (emoji) support
- I have already added Emoji test (r19699).
git_urf8 test repository is not extracted due to this.
https://www.redmine.org/builds/logs/build_trunk_mysql_ruby-2.6_1044.html -
19:18 Defect #24030: When SVN or Git repository has a commit comment include an emoji (4 bytes charactor), error occurs
- Marius BALTEANU wrote:
> Toshi, what do you think if we assign this to version:"4.2.0"? We already have a ticket there for utf8mb4 support on mysql, please see #32054.
Good idea. -
19:16 Defect #24030 (Closed): When SVN or Git repository has a commit comment include an emoji (4 bytes charactor), error occurs
- Conclusion:
No error with correct server configuration and "encoding: utf8mb4" of database.yml.
source:trunk/config/database.yml.example@19705#L12 -
19:15 Defect #24030: When SVN or Git repository has a commit comment include an emoji (4 bytes charactor), error occurs
- Toshi, what do you think if we assign this to version:"4.2.0"? We already have a ticket there for utf8mb4 support on mysql (#32054).
-
19:08 Defect #24030: When SVN or Git repository has a commit comment include an emoji (4 bytes charactor), error occurs
- This is Mercurial bundle file and its results.
!mercurial.png! -
19:02 Defect #24030: When SVN or Git repository has a commit comment include an emoji (4 bytes charactor), error occurs
- This is Subversion test repository and test code.
Same results with git.
I give up to commit because it is very risky
if [[Continuous_integration|CI server]] is NOT utf8mb4, tests skip. -
18:16 Defect #24030: When SVN or Git repository has a commit comment include an emoji (4 bytes charactor), error occurs
- I have added new test repository and tests because existing test repository encoding is 'ISO-8859-1'.
source:trunk/test/unit/repository_git_test.rb@19705#L42
On my CentOS 7 MySQL 5.5.62, utf8mb4 environment passes test.
!env.png!
... -
18:35 Feature #4367: Ability to delete an issue status that is in use
- Guillermo ML wrote:
> In #31361 (for 4.1.0) implemented the second option.
I have 2 problems with that implementation:
* the main one is lack of i18n;
* the other is lack of details.
-
14:03 Feature #4367: Ability to delete an issue status that is in use
- In #31361 (for 4.1.0) implemented the second option.
As you say in note-1 issues in archived projects could be a problem, these issue will not shown in a search. You'll have to search through a SQL query. -
17:04 Defect #33273: Total estimated time column shows up as decimal value regardless of time setting
- Marius BALTEANU wrote:
> Go Maeda, is there any reason for why we don't merge this to 4.0.8 as well?
This is because I simply didn't want to do manual work. r19702 cannot be auto-merged to 4.0-stable. But I will do it if you or someo... -
16:43 Defect #33273: Total estimated time column shows up as decimal value regardless of time setting
- Go MAEDA wrote:
> Committed the patch. Thank you for your report and fix.
Go Maeda, is there any reason for why we don't merge this to 4.0.8 as well? -
16:26 Defect #33273 (Closed): Total estimated time column shows up as decimal value regardless of time setting
- Committed the patch. Thank you for your report and fix.
-
16:49 Revision 19705 (svn): Update Rouge to 3.18.0 (#32468).
-
16:24 Revision 19704 (svn): Merged r19702 and r19703 from trunk to 4.1-stable (#33273).
-
16:15 Revision 19703 (svn): Test for r19702 (#33273).
- Patch by Go MAEDA.
-
16:11 Revision 19702 (svn): Total estimated time column shows up as decimal value regardless of time setting (#33273).
- Patch by Farook Al-Sammarraie.
-
14:19 Defect #33290: Unnecessary database access when IssueQuery class is defined
- I can confirm this problem with Redmine 4.1. It is very difficult to test plugins with the bug.
-
11:40 Defect #33290: Unnecessary database access when IssueQuery class is defined
- This only happens from Redmine 4.1 by the way.
The commit bringing the change was r17724 -
10:49 Defect #33290 (Closed): Unnecessary database access when IssueQuery class is defined
- During plugin development I found out that the definition of the Query class accesses the database just by being defined.
The reason for this is the `groupable` method in the `TimestampQueryColumn` class which tries to access the curr... -
12:43 Feature #3058: Show issue history using tabs
- Ali Hamdan wrote:
> Dears,
> ...
Please open a new issue for this request. -
03:00 Feature #3058: Show issue history using tabs
- Dears,
just an additional feature to mention it will be great if the PDF export of the issue will include the time entry(time+comment+custome fields) under history
Thanks. -
11:06 Defect #33291 (Resolved): Gantt conversion to png failed with error w.r.t. font 'helvetica'
- h2. Expected Behavior
Gantt-Diagramm converts to png file format.
h2. Actual Behavior
Clicking on the png link at the bottom of the Gantt page causes an error.
h3. Essentials of Error Message
MiniMagick::Error in GanttsCon... -
08:57 Defect #33287: Issue File Column Attachment Link Error
- Go MAEDA wrote:
> Sarthak Bakshi wrote:
> ...
Problem is the link is being displayed as /redmine/attachments/id instead of /redmine/attachments/id/filename.
To preview the file using magnifying icon file link should be /redmine/attach... -
07:10 Defect #33287: Issue File Column Attachment Link Error
- Mischa The Evil wrote:
> FWIW: This also seems to be the subject of the message#59108 forum thread.
Thanks, but I think my problem in the thread is different. I can download attachements and I can't see them in the attachement viewer... -
00:04 Defect #33287: Issue File Column Attachment Link Error
- Sarthak Bakshi wrote:
> 6) If you hover over that attachments you will be able to see that the link is breaking in half.
I don't understand what does "the link is breaking in half" and what is broken. If you click the link, you will ... -
04:45 Patch #20287: Administration: Using grids instead of tables
- Greg T wrote:
> Frederico Camara wrote:
> ...
How I miss git when altering patches. I may have changed the file instead of the patch by mistake.
New patch, disregard the other.