Activity
From 2013-09-22 to 2013-09-24
2013-09-24
-
22:56 Feature #4138: Add spent time comments in search
- I have created a rough patch, against Redmine trunk at r12160, that should provide this feature.
Known issues:
* shown search results display @created_on@ date of time entry comments instead of date from :date
* time entry comments ... -
22:37 Feature #9063 (Closed): Searchable comments from "Log time"
- Closing as a duplicate of #4138.
-
21:06 Defect #9331 (Closed): Status list is sometimes missing values
-
19:24 Feature #11222: Extend plugins compatibility information
- Posibility to leave comments for plugins where we can discuss compatibility and other points would be also very useful addition.
-
17:38 Feature #5298: Store attachments in sub directories
- *Failed to run on my machine, Windows 2012 Server x64*
Bitnami ruby stack v1.9.3-14 installed to C:\BitNami\rubystack-1.9.3-14
Environment:
* Redmine version 2.3.3.stable
* Ruby version 1.9.3-p231 (... -
17:11 Feature #6166: Support german umlauts and whitespaces in login string
- I just want to add myself as one more victim of this shortcoming. It's 2013 and we should be able to use proper usernames by now. Please consider to extend the allowable characters.
-
16:22 Feature #3647: Data Import/Export System
- +1
-
16:18 Defect #14851: Time spent not recorded (Git)
- I have the same issue, using 2.3.3.stable via BitNami and mercurial, default branch.
I see commits at issue, but spent time is not logged.
I have fixed it thanks to Toshi, which mentioned, that the user of SCM (hg or git) has to have... -
16:07 Defect #14621: AJAX call on the issue form resets data entered during the request
- Jean-Philippe Lang wrote:
> I see your point but blocking fields would affect user experience for the vast majority of people who don't have this concern.
If they don't have this concern this is probably that the call is fast enough ... -
15:45 Feature #4911: Multiple issue update rules with different keywords in commit messages
- I am looking for the exactly same feature.
-
15:40 Defect #14977 (Closed): Internal Server Error while uploading file
- Hello,
Sometimes Redmine stops uploading files and shows Internal Server Error when I try to attach file to issue. Application restart fixes it, but after some time problem comes again (now once a day).
Environment:
Redmine vers... -
14:32 Feature #11159: REST API for getting CustomField definitions
- A patch for 'GET /custom_fields.xml' (without the filtering part) is available in #9664.
-
14:29 Feature #9664: CRUD operations for "custom field definitions" (not setting custom fields on issues!)
- I have a patch which implement only the 'R' part, that is lists the available custom fields, for admin users (redmine-customfields-rest.patch). It has been tested on Redmine 2.3.0 and 2.3.2.
And here is a wiki doc which would fit as h... -
14:14 Feature #8016: Drag-and-drop issue (ticket) ordering
- +1
-
13:59 Defect #14976 (Closed): authentication required configurable
- when authentication required option is checked, all url required logined. but i expect some url is accessible to anonymous users, like '/attachments/download/3029/picture431-1.png', or else these image can't be displayed in email
-
13:06 Patch #14972: French locale update
- Alexis Blandin wrote:
> The french academy say that foreign words take a plural french form when this words are commonly used.
Oh... Well, I only asked my wife and a friend of mine, both said they'd not add a plural "s"...
> ...
Tr... -
09:34 Patch #14972: French locale update
- The french academy say that foreign words take a plural french form when this words are commonly used.
Notice about this rule : http://www.academie-francaise.fr/niky-orange
Plural form of underscore : http://fr.wiktionary.org/wiki/u... -
12:59 Defect #14975 (Closed): ELSA CFD : Fatal error during the post
- You're posting to the wrong website...
-
10:37 Defect #14975 (Closed): ELSA CFD : Fatal error during the post
- Hello,
I have launched 4 ELSA calculations this week-end. Only one was correctly repatriated. The 3 other ones have a fatal error during the post. The 3 elsa calculations ran correctly, only the post has failed.
I have launched retr... -
12:40 Defect #13698: Wrong argument error when sending email notifications after upgrading to 2.3.0
- I changed the setting "tls" to false and it worked.
See part of my configuration.yml -
12:40 Feature #5458: Extend Start/Due date to include time
- Thanks it works now !
-
12:27 Feature #5458: Extend Start/Due date to include time
- Rupesh H wrote:
> >pablo pablo wrote:>Thanks!!!
> ...
Apologies, V8 should fix it :)
-
12:21 Feature #5458: Extend Start/Due date to include time
- >pablo pablo wrote:>Thanks!!!
> ...
Does not work for me too..
Getting following trace in production.log
NoMethodError (undefined method `to_date' for nil:NilClass):
lib/redmine/helpers/calendar.rb:51:in `block in events='
... -
11:32 Feature #5458: Extend Start/Due date to include time
- pablo pablo wrote:
> After applying the patch the calendar stops to work : it doesn't show neither the old tasks nor the new ones...even if the time-feature is disabled in the project´s proprieties.
> ...
Fixed this by simply doing a t... -
11:51 Feature #7697: Extend watchers functionality of wiki and forums to be like issues
- +1
-
11:05 Defect #14939: Wiki link to specific issues failed
- duplicated by http://www.redmine.org/issues/14606
-
11:05 Defect #14939 (Resolved): Wiki link to specific issues failed
-
10:42 Patch #14606: Internal error when copying an issue + on "my page" in block "assigned to me"
- I get the same issue when viewing an issue.
The user.reload works fixed it too.
Before reload I get:[58, nil, nil]
After reload I get: [13, 15, 60]
-
10:04 Feature #11361: Custom Field Groups, and User Specific Fields
- +1 for this. Apart from visibility and hiding, there is a need to 'group' the custom fields.
This can be implemented by simply assigning a category field to the custom fields. Thus when custom fields are rendered, a block is formed b... -
09:36 Defect #14894 (Closed): Make issue links in Redmine open in a new window
-
06:08 Feature #14961: Reconsider moving from svn to git & GitHub
- Toshi MARUYAMA wrote:
> rm user wrote:
> ...
That's very good. Do not get me wrong I'm glad that you guys are putting so much effort into this redmine project.
I'm just saying my own personal thoughts about git, because I've used sv... -
05:41 Feature #14961: Reconsider moving from svn to git & GitHub
rm user wrote:
> Maybe it's because main developers are very conservative and like to stick to SVN.
No, we are not conservative.
Our rule is that *all bug fixes and features should have tests*.
It equals that *coverage should b...-
04:05 Feature #14961: Reconsider moving from svn to git & GitHub
- >So, for code review, we should use codereview plugin instead of other hosting service.
http://www.redmine.org/plugins/codereview
I don't think this plugin gives enough functionality for code review.
It basically creates a blank I...
2013-09-23
-
22:46 Defect #14939: Wiki link to specific issues failed
- I find out that it is user.groups in app/models/issue.rb that seems "corrupted".
users.groups.map(&:id) returns either [25, nil, nil] or [nil, nil, nil].
But I expect [13, 15,60]. -
17:52 Defect #14939: Wiki link to specific issues failed
- Actually, the "internal error" occured due to wrong sql request.
The syntax is wrong.
We observed a similar issue when reading an issue.
We need to investiguate why there is a syntax error in the generated request. -
22:14 Feature #14945 (Closed): Outlook inline image replace [cid:..] by redmine !inline image!
-
22:12 Patch #14972: French locale update
- ... changes underscore to underscores (plural form).
Native speakers told me they'd rather not use the plural form, reasoning that it's not a french word but a foreign one and as such, may stay in its native form. -
14:17 Patch #14972 (Closed): French locale update
- Some typo errors.
-
19:16 Defect #14621: AJAX call on the issue form resets data entered during the request
- Another option would be to detect the fields that were manually changed by the user during the ajax call and only restore these fields.
-
19:10 Defect #14621: AJAX call on the issue form resets data entered during the request
- I see your point but blocking fields would affect user experience for the vast majority of people who don't have this concern.
-
19:04 Patch #14767: More CSS classes on various fields
- Adding css classes about relations adds too many queries, I'm not in favor of it. Also, @tracker-#{tracker.name.downcase}@ is not acceptable as we cannot be sure that it makes a valid css class name.
-
18:55 Feature #14630 (Closed): wiki_syntax.html per language (wiki help localization mechanism)
-
18:54 Feature #3039: Make annotation why you receive a mail from redmine depend on your notification options
- This would require to send many emails for each notification and would really slow down issue updates. I'm afraid it won't make it for 2.4.0.
-
16:02 Feature #1828: Default target version for new issues
- +1 Because we'd like to make the target version mandatory for bug reports but set it to the current live version by default.
-
15:59 Feature #11637: Can you create a tree structure in Issue list
- Marcus Fleuti wrote:
> Looking very nice! Is this gonna find its way into the official release?
maybe?! .. if the author of redmine like to. -
13:51 Defect #14906 (Resolved): Excessive queries on roles table when show a Issue
- Hi,
I found the "problem". I have selected the option "Allow issue assignment to groups".
After unselected this, the excessive queries was finished.
Thanks. -
13:17 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> > Git branch is the reffernce to revisions.
> ...
I dislike "--no-ff merge".
Because revision graph becomes very dirty.
As I described my "Japanese presentation":http://marutosi.bitbucket.org/RxTstudy-20130622... -
12:56 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> > Have you read our Contributing guide?
> ...
Our commit rule is "Bug fix and adding feature should have *tests*".
We accept patches with this rule.
It does not related Pull request or Patches.
> My point is... -
11:31 Feature #14961: Reconsider moving from svn to git & GitHub
- > Have you read our Contributing guide?
> ...
Yes I've read it and I raise this issue as a request to revise it :).
I have strong concerns that Redmine project is losing people attention and willingness to help and I thing switch to gi... -
01:30 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> What do you mean by sample in comment 9 - that you can delete branch with name 'stable'? I don't get it.
Subversion and Mercurial branch tie to *one* branch.
r12156 is trunk, r12160 is 2.3-stable.
Git branch... -
01:19 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> Refering to your comment https://www.chiliproject.org/issues/601#note-32 :
> ...
I disagree all of your this comment.
We use "CI server":http://www.redmine.org/builds/index.html and "Covarage":http://www.redmine.... -
01:10 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> What do you mean by sample in comment 9 - that you can delete branch with name 'stable'? I don't get it.
> ...
Have you read our [[Contribute|Contributing guide]]?
> That being said I think that Redmine project... -
12:50 Patch #14971 (Closed): Plugin rollback migration
- The first migration is not rollback-able
with :
@rake redmine:plugins:migrate NAME=<plugin_name> VERSION=<version_name>
because there is no previous migration to migrate to.
Here is a patch to be able to rollback plugins, with a ... -
11:20 Defect #11888: No e-mail notification for non-members who are watchers
- For your information, I have developed a plugin that solves the problem, compatible with Redmine 2.3.2: https://github.com/maxrossello/redmine_extended_watchers
There are two branches:
- in the master branch, watchers are enabled to ... -
10:20 Defect #14874 (Closed): custom field as filter in view ALL issues
- "Here":http://www.redmine.org/boards/2/topics/39402?r=39520#message-39520 is the answer.
-
06:07 Defect #14960 (Resolved): migrate_from_mantis.rake does not import Mantis users, uses too short password
- Fixed as advice. Thank you.
-
05:30 Defect #14969 (New): ActiceSupport::TimeWithZone failed in migrate_from_mantis.rake
- The Redmine installation information as below:
@Information
Redmine 2.3.3.stable
Default administrator account changed True
Attachments directory writable True
Plugin assets directory writable True
RMagick available (optional... -
04:53 Defect #14865: Incoming email raises with attachment depending on the email client
- Redmine uses "mail".
Please feed back to "mail" author.
https://github.com/mikel/mail -
01:51 Patch #2525: Redmine management of Git repositories
- William Van Hevelingen wrote:
> The redmine_git_hosting plugin doesn't look actively maintained...... and doesn't support redmine 2.x. There is a 2.0-migration branch but it hasn't been touched in the last ~4 months.
try this - https... -
01:49 Feature #2048: Code Review Module
- Dipan Mehta wrote:
> You can use the "Code Review plugin":http://www.redmine.org/plugins/codereview. It works very well and quite the perfect module.
no it's not giving accept/reject functionality and not e-mailing status to the pers...
2013-09-22
-
18:39 Feature #14961: Reconsider moving from svn to git & GitHub
- Refering to your comment https://www.chiliproject.org/issues/601#note-32 :
> pull request is not suitable for big well-maintained centralized project.
I think PRs works quite good with projects in all sizes and technologies. Great ackn... -
18:38 Feature #14961: Reconsider moving from svn to git & GitHub
- What do you mean by sample in comment 9 - that you can delete branch with name 'stable'? I don't get it.
I've read discussion in PR https://github.com/torvalds/linux/pull/17 and I completly agree with Linus arguments. Linux and Git pr... -
05:53 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> Also many centralized companies buy 'GitHub Enterprise' just because of this feature - the ability to easy share your fix with people.
GitHub is one of Git hosting service.
Bitbukcet, CodePlex, Google Code, Sou... -
05:46 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> At current state GitHub is de facto best way to share an opensource project and involve many people, beacause it is so easy to fix one thing and send Pull Request with the fix.
> ...
GitHub is *not* de facto best ... -
05:37 Feature #14961: Reconsider moving from svn to git & GitHub
- Łukasz Jąder wrote:
> What do you mean by "Git branch is not stable"? Please provide some details. -
17:43 Defect #14967 (Closed): Search Issues PGSqlError when select multiple ids
- Help me please:
Processing IssuesController#index () [POST]
Parameters: {"controller"=>"issues", "values"=>{"priority_id"=>["3"], "status_id"=>["1,9,10"], "due_date"=>[""], "created_on"=>[""], "tracker_id"=>["5"], "do
Query::State... -
15:01 Feature #14966 (New): "Spent Time" report: maximal criteria amount is hard-coded by now, should become configurable
- Sometimes I need to include more than three criteria in report (for example, Project->Issue->Activity->User). I was surprised to know that this constant (3) is hardcoded inside two files: /app/views/timelog/report.html.erb:27 and /lib/re...
-
14:25 Defect #14965: QueryColumn::sql_for_field assumes that operators "issue is opened/closed" deal with field named 'status_id' only - not extendable
- Forget to mention: usage of #{queries_table_name} also looks very strange, all other operators use #{db_table} instead. That was the main problem for me - I had to select all TimeEntry which are related to closed issues, and #{queries_ta...
-
14:20 Defect #14965 (Closed): QueryColumn::sql_for_field assumes that operators "issue is opened/closed" deal with field named 'status_id' only - not extendable
- While trying to add some custom filters I found out that even if you call sql_for_field with specific table and field name, it still uses #{queries_table_name}.status_id as field in generated WHERE statement. You can see the problem in /...
-
12:30 Defect #14964 (Closed): No http(s) support in Subversion in redmine stack
- I have installed Bitname Redmine stack on a CentOS server. When I try to access my subversion server using https, I get error:
"The entry or revision was not found in the repository."
Here is the version info: CentOS Linux release 6...