Activity
From 2016-10-18 to 2016-10-20
2016-10-20
-
17:23 Defect #24109: Forums tab is missing but link is accessible
- https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/
-
15:23 Defect #24109: Forums tab is missing but link is accessible
- I use rvm with this ruby version because of no issues so far.
-
10:13 Defect #24109 (Needs feedback): Forums tab is missing but link is accessible
- #23964#note-1
> Why do you use such very old Ruby?
#23964#note-3
> ...
-
09:54 Defect #24109 (Closed): Forums tab is missing but link is accessible
- If I enable *Forum* module then Forum tab is not appears, however I could access it directly by link with _boards_ at the end.
-
15:15 Defect #24111: Moving the parent issue from subproject to another project moves sub issues too
- An important note to the sub tasks is, that the sub tasks has to be in the same project like the main task.
The project of sub tasks which belongs to another project are not changed.
Example: -
13:38 Defect #24111 (New): Moving the parent issue from subproject to another project moves sub issues too
- If an issue with sub tasks is moved to another project (main project of the current one) the sub tasks are automatically moved to the new project, too.
Further no remark is written to the history of any of the tasks, neither to the pare... -
14:53 Feature #10989: Prevent parent issue from being closed if a child issue is open
- Here it is.
-
12:23 Feature #10989: Prevent parent issue from being closed if a child issue is open
- Marius BALTEANU wrote:
> Let me know what do you think in order to update the patch.
Please update the patch. -
14:46 Feature #24089: Call to Action (CTA) and improved conversion for registration
- Looks perfect. I would like to see it in next release.
-
13:50 Feature #15201: Filter "Assignee" should contain locked users
- +1
and agree as well with Henning Kroger regarding time_entries. If someone left from the company half way of a version and we want to display the timelog report for all issues related to the version. The timelog from the locked-user w... -
13:40 Feature #11069: Ability to search tasks of Locked Users
- + 1
-
10:32 Feature #7754: Plugin priority
- Slightly related to #6324, #23131
-
10:26 Feature #23131: Plugin load order defined by inter-plugin dependencies
- Wouldn't a simple topological sort (ruby @TSort@) in @lib/redmine/plugin.rb@self.load@ do the trick?
Of course provided that we can get information about the dependencies without having to load the plugins first... Chicken/Egg problem.
-
04:18 Defect #24104: Filter "in the past days"
- What value is "in the past days"?
Neto Foltz wrote:
> Let's imagine today morning (oct 19).
> ...
I think it is expected behavior if you use *3* "in the past days".
2016-10-19
-
23:51 Feature #5864: Regex Text on Receiver Email
- We made a patch with tests that implements this feature. Without regex delimiters, we weren't able to truncate correctly the emails received. I think that this feature is really needed in core.
-
21:02 Defect #24104: Filter "in the past days"
- Let's imagine today morning (oct 19).
Every morning, I get a report of time tracking using the filter "in the past days". At this time, when I take the report, if nobody did a new time register today (oct 19), the report show data unt... -
15:26 Defect #24104 (Needs feedback): Filter "in the past days"
- Please describe more details.
-
14:40 Defect #24104 (Closed): Filter "in the past days"
- Hi,
using the filter "in the past days" to get time tracking reports, when someone register a spent time today, the report shows hours from yesterday. Instead it, if no one do a register of time today, the system just show hours from da... -
15:18 Defect #24102 (Closed): Opening "Custom Fields" in Administration leads to "Internal Server Error"
- Redmine core does not have "OrderCustomField".
-
12:33 Defect #24102 (Closed): Opening "Custom Fields" in Administration leads to "Internal Server Error"
- On our Redmine 3.2 installation we recognized that after some (not identifiable) moment the "Custom Fields" Entry in "administration" leads to an
-
09:31 Feature #13919: Mention user on issues and wiki pages using @user with autocomplete
- +1
-
09:30 Feature #3058: Show issue history using tabs
- @Mark, did you manage to resolve the issue with time entries?
-
03:45 Defect #24094 (Closed): Error with non ASCII characters in Wiki
-
02:06 Feature #15520: Markdown formatting
- Yes markdown is supported everywhere where textile is supported, including issues, as long as you select the markdown format in Redmine global settings.
2016-10-18
-
22:38 Feature #15520: Markdown formatting
- Perhaps this is a silly question, but is Markdown supported at all outside of wiki pages? I have people begging for it in areas like this one right here we're looking at - the issue tracker.
-
19:37 Defect #24094: Error with non ASCII characters in Wiki
- Please close this issue as apparently it works in the new version used here at redmine.org. I'll try to upgrade.
-
18:53 Defect #24094 (Needs feedback): Error with non ASCII characters in Wiki
- Please see [[submissions]].
-
18:09 Defect #24094 (Closed): Error with non ASCII characters in Wiki
- When creating/saving a Wiki page or an issue description (also wiki format) that contain some non-ASCII characters like (ț ă), Redmine shows the following "Redmine 500 error" page:
"
Internal error
An error occurred on the page yo... -
19:36 Defect #24090 (Closed): ArgumentError: Invalid Timezone: UTC
-
11:01 Defect #24090 (Closed): ArgumentError: Invalid Timezone: UTC
- When /redmine/config/application.rb:25 is default:
-
17:30 Defect #24092: bundler error: selenium-webdriver requires Ruby version >= 2.0.
- I create and attach a patch of Gemfile like r15274 .
-
17:24 Defect #24092 (Closed): bundler error: selenium-webdriver requires Ruby version >= 2.0.
- Error message encountered when running **bundle install** with Redmine v3.3.1 and Ruby 1.9.3.
-
05:29 Defect #24052 (Closed): Unable to select columns in Administration, Settings, Issue Tracking, Default columns displayed on the issue list
- Thank you for your feedback.