Activity
From 2012-01-04 to 2012-01-06
2012-01-06
-
20:39 Feature #5541: Project Status "Closed"
- Watched.
My key requirement is to have the knowledge contained in an archived project be searchable. -
20:17 Feature #6721: Allow setting issue assignment by username via REST interface
- can we just keep "assigned_to_id" for backward compatibility and
add "assigned_to" parameter, which would take either ID or Login name? if "assigned_to" is used, then "assigned_to_id" is ignored (and should be marked as "deprecated" an... -
14:44 Feature #6721: Allow setting issue assignment by username via REST interface
- Looks like I had an unrelated error. I have modified the code to enable the usage of @assigned_to_id=[login]@. You should be able to use login instead of id.
-
13:16 Feature #6721: Allow setting issue assignment by username via REST interface
- I tried to do it but it is interfering with other methods:
* Create issue with group assignment
* Update issues with group assignment
These methods use the group id for the assigned_to_id field. @assigned_to_name@ seems to be a safe... -
12:19 Feature #6721: Allow setting issue assignment by username via REST interface
- Etienne Massip wrote:
> Actually you should remove the changes in @IssueController@ and use the @assigned_to_id=<username>@ syntax (for consistency with @project_id@).
As far as I know project_id is cannot be updated with the api. So... -
09:41 Feature #6721: Allow setting issue assignment by username via REST interface
- Sridhar P wrote:
> Here you go. User.find works the same way that Project.find does; you can get user by User.find([username]) and User.find([id]).
Yes, I think it's cleaner now since the behavior will be the same everywhere in the a... -
07:04 Feature #6721: Allow setting issue assignment by username via REST interface
- Here you go. User.find works the same way that Project.find does; you can get user by User.find([username]) and User.find([id]).
I have used better names for the functions that fetch the id from the login name. -
06:16 Feature #6721: Allow setting issue assignment by username via REST interface
- Etienne Massip wrote:
> I was wondering if the @Project@ model way could be applied: source:/trunk/app/models/project.rb#L253
As I understand it, yes, it can be done. That would impact every User.find([id]) call. If that is the prefe... -
18:11 Feature #1919: Separate permissions for changing assigned-to, % finished and target version
- This issue is very narrowly-focused and discrete, which I think makes it a great candidate for near-term implementation. Judging by the number of related (and still open) issues, plus the number of comments posted to those issues, the de...
-
14:06 Feature #9197: Allow more than one parent issue for a single issue
- Watching this.
-
13:37 Defect #9937 (Closed): Repository settings are not saved when all SCM are disabled
- When I disable all SCM in "Administration -> Settings -> Repositories" and press save, I get the message "Successful update.", but all previously disabled SCM are checked and enabled again.
-
12:49 Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- +1
-
11:46 Feature #1005: Add the addition/removal/change of related issues to the history
- +1: it's a necessary feature
-
10:46 Feature #3055: Option to copy attachments when copying an issue
- +1
-
10:40 Feature #3055: Option to copy attachments when copying an issue
- +1
-
10:28 Defect #9500: Watchers list before and after creation issue
- I can also confirm the issue, and do agree with the original reporter that this is an issue. My reasoning is that while I agree with what Mischa is saying about not suggesting to add watchers that don't have the permission, if *I* have t...
-
10:25 Defect #9936 (Closed): Error when displaying an issue from a query sorted by an association
- Hi, since approximately one week, we have this error raising when we're getting issues#show :
-
08:57 Feature #9923: User type custom fields should be filterable by "Me".
- +1
-
08:06 Feature #1278: Creating global (default) categories.
- I would like to work on this. Is it okay to use the existing issue_categories table with project_id set to 0 for the global categories? Or is there a better approach?
-
06:57 Feature #6296: Bulk-edit custom fields through context menu
- +1
2012-01-05
-
22:42 Feature #1278: Creating global (default) categories.
- +1
This would save so much time! we have new projects entered weekly. Updating the categories when they are the same for each project is very time consuming. -
22:10 Feature #8488: Create an 'Involve' mechanism to private issues
- Bruno Medeiros wrote:
> I guess I could port this patch to the 1.3-stable branch, but couldn't test yet. If someone could give some feedback on it, I would appreciate. :)
Hey Bruno,
i tested it on 1.3 and it seems to work like a ... -
18:02 Feature #1554: Private comments in tickets
- My initial thought is that you might not be running it from your redmine install directory. I occasionally get error like that when I try to apply a patch from ~/
This also might be caused if you've made modifications to redmine your... -
15:10 Feature #1554: Private comments in tickets
- Nice feature you patched, but i am having problems to merge it with 1.3 stable i installed a few days ago. When i run the patch -p0 < private_messages-2011-12-14-v1.3.patch on the root dir of redmine and i get a lot of errors and reject...
-
17:50 Feature #9930 (Closed): Removable Overview / Activity menus
- Closed as duplicate of #2585.
-
17:15 Feature #9930 (Closed): Removable Overview / Activity menus
- Many aspects of a project menu is removable through modules settings (like news, wiki, etc).
However Overview and Activity cannot be removed. It could be nice if these two were removable too. -
17:42 Feature #1091: Disabling default ticket fields per tracker
- +1
-
17:24 Feature #9194: Issues default list view layout configurable per project
- +1
-
17:23 Feature #9931 (Closed): In user roles news viewing can also be configurable
- When editing a user role, we have news management and news commenting, however there isn't a privilege for news viewing.
It could be nice if we could also make some user roles who couldn't view the news at all (like wiki or files modu... -
17:21 Feature #9565: Gantt graph grouped by "assigned to"
- +1
-
17:16 Feature #6118: Filter by parent task or subtasks
- +1
-
17:15 Feature #5487: Allow subtasks to cross projects
- +1
-
17:14 Feature #3452: Per project email notifications settings panel
- +1
-
17:14 Feature #2161: Time tracking code should respect weekends as "no work" days
- +1
-
17:13 Feature #1248: New Permission: Edit own issues
- +1
-
17:12 Feature #582: Make fields mandatory/unmandatory based on role
- +1
-
17:12 Feature #703: Configurable required fields per tracker/status/role
- +1
-
17:06 Feature #9929 (Closed): Category names could be longer
- Current the categories in each project cannot be more than 30 characters long.
It would be nice if this length were configurable. In some cases longer categories can be needed. -
17:02 Feature #9928 (New): Custom ext auth source password change message
- When using LDAP authentication, user passwords cannot be changed and an error message appears: "This account uses an external authentication source. Impossible to change the password."
It could be nice if this error message were custo... -
16:57 Feature #9927 (Closed): Limiting e-mail subject header length
- Some defective e-mail servers can't handle e-mails with subjects longer than 60-70 characters. They cut off the rest of the line. With UTF-8 this causes the subject header to break down, causing the entire subject line unreadable.
It ... -
14:56 Feature #6721: Allow setting issue assignment by username via REST interface
- I was wondering if the @Project@ model way could be applied: source:/trunk/app/models/project.rb#L253
-
14:18 Feature #6721: Allow setting issue assignment by username via REST interface
- More functions are available with the login name now.
show, edit, update, destroy, edit_membership and destroy_membership of the users controller are available with the login name now.
@GET /users/[username]
GET /users/[username]/ed... -
10:57 Feature #6721: Allow setting issue assignment by username via REST interface
- For consistency this could include @GET /users/[username].:format@, @GET /issues.:format?assigned_to_id=[username]@, @POST/PUT news@, etc.
-
10:22 Feature #6721: Allow setting issue assignment by username via REST interface
- Etienne Massip wrote:
> The problem with this patch is that it only works for issue creation/update.
> ...
Etienne: What are the other methods that need the assigned_to_name feature? While creating the feature, Ian Epperson wrote that ... -
09:25 Feature #6721: Allow setting issue assignment by username via REST interface
- Alexey Skor wrote:
> Thank you, Sridhar. I really hope this will be accepted by Redmine guys...
The problem with this patch is that it only works for issue creation/update.
Maybe there should be a more specific solution; doesn't t... -
09:07 Feature #6721: Allow setting issue assignment by username via REST interface
- This will work only when the "assigned_to_id" is NOT set and "assigned_to_name" is set. To be more specific, this will work only when params[:issue][:assigned_to_id] is NOT set and params[:issue][:assigned_to_name] is set.
-
09:06 Feature #6721: Allow setting issue assignment by username via REST interface
- Thank you, Sridhar. I really hope this will be accepted by Redmine guys...
-
09:04 Feature #6721: Allow setting issue assignment by username via REST interface
- I have created a patch for this feature against the trunk (at revision 8513). Attached is the diff file.
-
12:20 Defect #9132: Filtering by "Assignee's Group" doesn't show issues assigned to the group
- Etienne Massip wrote:
> * Assignee's group IS "GROUP1"
> ...
I do agree that redmine needs OR queries, but that is far more complicated to implement than my request.
To avoid any semantic discussions, why don't we just create a new... -
11:21 Defect #9132: Filtering by "Assignee's Group" doesn't show issues assigned to the group
- I do agreed with Ariel Scarpinelli.
A group is a dummy user in user table, if a ticket assigned to this group, it should be listed by criteria specified as Assignee's group equal to this group. -
12:11 Defect #9926: export issues to csv fails
- Yes, it's an accessor method to a DB column value.
Try to remove all the 'formatted_questions' you might find in the @column_names@ column of the @queries@ table? -
11:31 Defect #9926: export issues to csv fails
- Etienne Massip wrote:
> What's the "formatted_questions" referring to?
> ...
dont have such column, from the error it seems like formatted_questions is a method.
#grep -rn formatted_questions *
question_plugin/spec/lib/question_q... -
10:49 Defect #9926: export issues to csv fails
- What's the "formatted_questions" referring to?
Do you have such a column selected in the query columns? -
10:27 Defect #9926 (Closed): export issues to csv fails
- Processing IssuesController#index to csv (for 10.220.3.218 at 2012-01-05 11:26:04) [GET]
Parameters: {"format"=>"csv", "project_id"=>"fca", "action"=>"index", "controller"=>"issues", "columns"=>"all"}
NoMethodError (undefined metho... -
09:34 Feature #8058: Separation of content language from UI language
- FTR: https://github.com/svenfuchs/globalize3 would be a great solution.
-
02:30 Patch #9922 (Closed): Spanish translation updated
- Committed in trunk r8508, r8509, r8510 and 1.3-stable r8511, r8512.
Thanks. -
02:04 Patch #9922: Spanish translation updated
-
02:26 Feature #4179: Link to user in wiki syntax
- +1
2012-01-04
-
23:20 Defect #9815: Release 1.3.0 does not detect rubytree with rubgems 1.8
- According to [[RedmineInstall]], 1.3.x requires Rails 2.3.14. but there's no note about needing a specific version of RubyGems for Rails 2.3.14, only for Rails 2.3.11.
-
20:40 Defect #9924 (Closed): Custom field not filter option at global scope
- I created a custom field of type User, all Trackers and checked, "For all projects" and "Used as filter" are checked. The problem is the custom field can't be used to filter at the global scope (View All Issues) and can't be used in a cu...
-
20:36 Feature #2799: Support for Bazaar's shared reposetories (created with init-repo)
- Michael Trausch wrote:
> I am stuck on this. From what I can tell, this cannot be done efficiently, if at all, because Bazaar uses a different model from what Redmine expects.
Why don't you just use the command @bzr branches /path/t... -
20:20 Feature #9923 (Closed): User type custom fields should be filterable by "Me".
- The "Assignee" filter has a <<Me>> option, but custom fields of type "User" do not. I want to add an "Attention" custom field and a global/shared filter that shows all issues with "Attention" set to <<Me>> but cannot currently do this si...
-
17:49 Defect #9921: New issue validation error
- Looks a lot like a plugin issue, could you please try without any plugin?
-
17:03 Defect #9921 (Closed): New issue validation error
- Hi
If I want to create a new issue, and i don't fill the required field, and click crete I got an error page (http 500)
Here is the log:
Processing IssuesController#create (for 192.168.0.155 at 2012-01-04 16:47:18) [POST]
Par... -
17:20 Patch #9922: Spanish translation updated
- New Patch. Diff was against my own SVN.
-
17:17 Patch #9922 (Closed): Spanish translation updated
- Updated some strings. Most of them from English. The other, a better (IMO) translation for subject.
-
17:17 Feature #9898 (Closed): Wiki translation
- Closed as duplicate of #9601 (which might already be a duplicate).
-
16:07
Feature #9898: Wiki translation
- 1+
-
16:42 Feature #1189: Multiselect custom fields
- Leif Lange wrote:
> Thanks for the reply, I had indeed forgotten issue a 'sudo rake db:migrate' command. But even after successful completion of the migration, I still get the NoMethodError complaining about the missing 'allow_multi' me... -
15:49 Feature #703: Configurable required fields per tracker/status/role
- +1
this is something very useful to me -
14:49 Defect #9920 (Closed): Custom fields of type "User" can't be ordered and used in custom queries for all projects
- The fields of type user don't allow me to sort by them in the issue list, and this fields also can't be used in custom queries when "For all projects" is checked, even if i check then as for all projects in custom field creation. I have ...
-
14:40 Defect #9895: Default value of custom field is empty despite of it is saved.
- Ok.
-
13:55 Defect #9895 (Closed): Default value of custom field is empty despite of it is saved.
- There is no "Link" custom field in Redmine core, please contact the plugin author.
-
14:37 Defect #9894: Issue category is not created for the project if we try to create it via ajax on adding new issue page.
- Found a cause. There is a plugin called "fields permissions" http://www.redmine.org/plugins/redmine_fields_permissions, it breaks almost all features designed through _attributes view.
-
13:52 Defect #9894 (Closed): Issue category is not created for the project if we try to create it via ajax on adding new issue page.
- Can't reproduce on "m.redmine.org":http://m.redmine.org with 1.3.0 stable, could be a setup issue (can you add a related issue to an issue?) or a plugin issue?
You should also check your @production.log@ file.
-
14:17 Feature #9919 (Closed): Filter issue by project custom field
-
14:10 Feature #9919: Filter issue by project custom field
- just realised it duplicates #8161
-
14:08 Feature #9919 (Closed): Filter issue by project custom field
- Issue related to message#28294
It would be good to be able to use project custom fields in the filtering options within the issue lists.
Let me explain :
I want to use custom fields to qualify projects, for example :
- project t... -
14:17 Defect #9879: Redmine 1.2.2, Mercurial, LDAP
- Marco Battistoni wrote:
> No I mean that with LDAP the password is not stored in the database
I got that, but this is normal, Redmine don't have to store the LDAP password.
> ...
I don't get that, how do you push what?
If you'r... -
14:11 Feature #8161: Ability to filter issues on project custom fields
- +1 and is duplicated by #9919
-
13:28 Defect #9821 (Closed): Rake db fails updating from 1.2.1 to 1.3.0
-
12:46 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- Etienne Massip wrote:
> No, it is not.
Then we can close it as invalid because redmine works as expected -
12:19 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- No, it is not.
Now I understand why the table existed before:
* you created a fresh bare 1.3 DB with its schema which is useless since it should be overwritten by the DB import
* you made a full DB import over an existing base witho... -
11:22 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- pasquale [:dedalus] wrote:
> This table isn't created by plugin (see my comment 4)
To be more explicit:
# redmine db 1.2.1 haven't table changeset_parents;
# install new redmine 1.3.0 release with an empty new db;
# restoring db 1... -
08:48 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- Etienne Massip wrote:
> But if this table was created by a plugin
This table isn't created by plugin (see my comment 4): before I restore my database from 1.2.1 to 1.3.0, browsing into him tho find this table produce 0 results: the t... -
12:18 Feature #5490: Option for independent subtask priority/start date/due date/done ratio
- I have tried my hand at this. What it does:
- Creating/updating the sub task doesn't update the start_date, due_date and priority_id
- Allows editing of priority_id, start_date and due_date of an issue even when all of the sub-tasks ar... -
11:35 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- Etienne Massip wrote:
> Mike Dubman wrote:
> ...
yes
-
10:11 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- Mike Dubman wrote:
> tried - still happens, it seems that question_plugin uses a right API for sql_for_field.
Did you restart Redmine server instance? -
09:59 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- Etienne Massip wrote:
> Try to uninstall the plugin then?
tried - still happens, it seems that question_plugin uses a right API for sql_for_field.
Is that possible that number of arguments to pass into sql_for_field is taken from ... -
09:39 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- Try to uninstall the plugin then?
-
09:29 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- $grep -rHn sql_for_field *
question_plugin/lib/question_query_patch.rb:18: alias_method :sql_for_field_before_question, :sql_for_field
question_plugin/lib/question_query_patch.rb:19: alias_method :sql_for_field, :question_sql... -
09:28 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- attached.
Also, I have many plugins installed, maybe some of them overloading sql_for_field func?
thanks -
08:20 Defect #9904: 500 Internal Server Error when Issues->filter by custom field of type list.
- You can attach your app/models/query.rb here.
-
06:17 Defect #9904 (Reopened): 500 Internal Server Error when Issues->filter by custom field of type list.
What do you suggest to trace this issue? It is always reproducible on our fresh setup.
Please suggest-
10:48 Defect #9901: NoMethodError Updating Ticket
- Any one help me
-
10:38 Feature #9918 (New): Ability to add roles as watchers
- It will be very helpful if we can assign roles as watchers.
-
10:20 Defect #9916: 500 error on project settings page
- Sorry, here is details
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.7.2
Rack version 1.1.2
Rails version 2.3.14
Active Record version 2.3.14
Active Resource version 2.3... -
09:42 Defect #9916: 500 error on project settings page
- Please give details according to [[SubmittingBugs]].
-
09:29 Defect #9916 (Closed): 500 error on project settings page
- After updating to version 1.3.0 I can't edit project settings. I get the 500 error. Here is the error in the log file:
-
10:10 Feature #9917 (New): Permit to switch to source from the diff
- When viewing a diff, it could be usefull to have access to the source.
* One option could be to expand the "triple dot" when double clicking on them
* Another could be to switch to full source at a specific place when clicking on the... -
09:21 Defect #9762: Closing issues with commit should be cross project
- Mischa The Evil wrote:
> It already works cross-project. See r3357 for issue #4674, which was included first in Redmine version#16.
It works genealogically, between a parent and a child.
But not between "brothers", nor "cousins".
... -
06:59 Feature #9915 (New): View hook just after top-menu.
- I hope to add a view hook just after top-menu.
(E.g. Using view hook just after top-menu is enabled to show all users site-wide message, such as maintenance information.)
-
01:23 Feature #3058: Show issue history using tabs
- +1
There is an "Issue History Tab":https://github.com/tastapod/redmine_issue_history_tabs plugin that works with 1.2.2. But the comment feature is buggy. Of course if anyone wants to take a shot a fixing it...
Here is a link to the...