Activity
From 2018-11-20 to 2018-11-22
2018-11-22
-
17:15 Defect #30009: Empty sort criteria for issue query gives error
- I can confirm the defect. It also occurs on the latest trunk.
Switching the query works as expected. As Kumar wrote it only occurs after applying the query a second time. -
11:55 Defect #30009: Empty sort criteria for issue query gives error
- It is reproducible on a clean install of Redmine 3.4.6.
After you save the query,make sure the same query is loaded & click apply.
Since the middle criteria for sort is left empty,the to_param method in Redmine::SortCriteria throws "... -
11:32 Defect #30009 (Needs feedback): Empty sort criteria for issue query gives error
- I could not reproduce the problem. Can you see any error regarding this problem in log/production.log ?
-
11:24 Defect #30009 (Closed): Empty sort criteria for issue query gives error
- When saving an Issue query,provide the sort criteria like below, i.e leaving the middle one empty.
!sort.PNG!
Save the query.
With the new query loaded,click on apply.
It gives error.
Bug occured on redmine: 3.4.6 -
07:39 Defect #8395 (New): Tags start with 'pre' are handled as 'pre' tag in Textile
- LGTM. The patch can be applied to the trunk and 3.4-stable cleanly. Setting target version to 3.4.7.
-
06:50 Feature #4511: Allow adding user groups as watchers for issues
- I fixed the CPU 100% issue of Cleber Souza codes
Redmine 3.4.4.stable
Original: https://github.com/piccio/redmine_watchers_groups
Fixes
2018-11-21
-
11:37 Feature #4511: Allow adding user groups as watchers for issues
- > cleber souza wrote:
> ...
Hi Cleber Souza
I installed the plugin you provided for Redmine v3.4.4.stable, it works for creating issues with groups watchers, but when I open the issue I just created, the ruby process takes CPU 100%..... -
10:33 Patch #29885: Fix 403 error while adding new watchers when selected issues in context_menu from different projects
- Confirmed the problem.
-
10:29 Patch #29885: Fix 403 error while adding new watchers when selected issues in context_menu from different projects
- Andrey Lobanov (RedSoft) wrote:
> Can anyone review this patch?
Could you add a test to the patch? -
10:28 Patch #29885: Fix 403 error while adding new watchers when selected issues in context_menu from different projects
- Can anyone review this patch?
-
08:16 Feature #8757: Add hook for bulk edit post-save state
- +1
I am modifying a plugin that reads journal of bulk edit issues, too.
https://github.com/jcppkkk/redmine_hipchat/commit/45d740de41bcaa68f64d5def16a9367e6291ed8b#diff-a7f255c397e668f358fc183f6802c3f3R25
Julián Maestri wrote:
> Pat... -
07:25 Defect #20788: REST API with JSON content missing attributes with false values
- LGTM. Setting the target version to 3.3.9.
-
03:31 Defect #20788: REST API with JSON content missing attributes with false values
- JSON result was missing value of false or nil.
The reason is that we assume as 'true' the result of @[false].any?@ . However actual this result is 'false'.
https://ruby-doc.org/core/Enumerable.html#method-i-any-3F
I made a patch, ... -
02:48 Feature #27313: More custom queries on My page
- +1
-
01:05 Defect #30001 (Closed): CSV importer ignores shared version names of other projects
- When importing issues from CSV, you cannot set a target version for an issue if the specified version name in the CSV is a shared version of another project.
This issue was reported to "redmine.tokyo community":https://redmine.tokyo/i...
2018-11-20
-
21:16 Feature #5655 (Closed): Allow related issues to be started/due on the same date.
-
21:15 Feature #5655: Allow related issues to be started/due on the same date.
- Sebastian C wrote:
> 8 years later, is there any update on this?
> ...
There were some discussions about this on #3195. I'll close this issue as duplicated. -
16:48 Feature #5655: Allow related issues to be started/due on the same date.
- 8 years later, is there any update on this?
Using a delay of -1 certainly works but it's incredibly confusing to anyone who doesn't know _why_ it was necessary to do so. -
14:55 Feature #11963: Hide the estimated times on issues for certain roles
- +1
-
14:55 Feature #12005: Mightful workflow field enhancement: hide
- +1
-
09:42 Feature #8095: Allow overriding the default text formatting in each project
- We are using Redmine for several years with textile formating and we would like to switch to Markdown progressively.
Will this feature request be implemented soon ?
-
09:41 Patch #30000 (Closed): Japanese translation update (r17623)
- Translated @error_token_expired@.
-
09:41 Patch #29999 (Closed): Update rdoc gem
- Redmine uses rdoc gem 4.3.0 that was released 2 years ago. According to the commit log of r15945, this is because the newer versions of rdoc requires RubyGems 2.2 which is too high for Redmine at that time.
But now, the current trunk ... -
09:10 Feature #25747: Spent time - CUSTOM fields - edit permission - WEB UI vs. API access
- I agree.
I've tried to disable custom field from editing too, but this isn't possible either from the UI side or database. Manually changing value of the column 'editable' or 'visible' in the custom_fields table doesn't affect the custo... -
08:20 Defect #29911 (Closed): [Email Notification] _involved in_ clarification
- Nicolas Felix, you can find some patches in the related tickets of #8488.
-
08:06 Defect #29911 (Resolved): [Email Notification] _involved in_ clarification
- Ok, thanks Anders for clarification.
I will look if any plugin enable us to send mails do any people involved in the ticket,
meaning here _watchers_, _author_ and _anybody assigned at any given time_ -
07:22 Defect #8395: Tags start with 'pre' are handled as 'pre' tag in Textile
- Go MAEDA wrote:
> After applying the patch #8395#note-4, an unnecessary blank line is inserted before the first line inside @pre@. Could you check the patch?
Thank you for pointing out my patch's bug (#8395#note-6). I confirmed same ... -
06:50 Feature #29993: Option to unarchive the project when admins visit an archived project
- +1 I think in this particular case it would be great if the link would provide a view to the admin where he could recover the project directly.