Activity
From 2012-01-05 to 2012-01-07
2012-01-07
-
20:08 Feature #3382: Ability to select only source code without line numbers
- Fixed with r8541, requires a browser supporting the @user-select@ CSS3 rule.
From what I know and see, FF supports... -
17:23 Defect #9940 (Closed): Branch names are truncated
- In the repository view, branch names are truncated and there are two empty cells without a column title. I'm using Ru...
-
17:07 Feature #9807: Add link in diff view to point to revision
- Hello could you please check my patch?
-
- Hi, Please find patch attached.
-
13:35 Feature #9803 (Closed): Change project through REST API issue update
- Added in r8531.
-
- Added in r8531.
-
- You'd better ask questions in the forums, thanks.
-
04:37 Feature #9939 (Closed): How SEO Works in Redmine
- Hi all,
Sorryfor my ignorance but I am just curious how Redmine site can help in SEO of a certain site.Anybody can...
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 eith... -
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 sh...
-
- I tried to do it but it is interfering with other methods:
* Create issue with group assignment
* Update issues wit... -
- Etienne Massip wrote:
> Actually you should remove the changes in @IssueController@ and use the @assigned_to_id=<use... -
- Sridhar P wrote:
> Here you go. User.find works the same way that Project.find does; you can get user by User.find([... -
- Here you go. User.find works the same way that Project.find does; you can get user by User.find([username]) and User....
-
- Etienne Massip wrote:
> I was wondering if the @Project@ model way could be applied: source:/trunk/app/models/projec... -
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 implementati...
-
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 ...
-
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 whi...
-
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
-
- 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 ...
-
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 sa... -
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 ... -
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...
-
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...
-
- 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 ... -
17:42 Feature #1091: Disabling default ticket fields per tracker
- +1
-
- +1
-
- When editing a user role, we have news management and news commenting, however there isn't a privilege for news viewi...
-
- +1
-
- +1
-
- +1
-
- +1
-
- +1
-
- +1
-
- +1
-
- +1
-
- Current the categories in each project cannot be more than 30 characters long.
It would be nice if this length wer... -
- When using LDAP authentication, user passwords cannot be changed and an error message appears: "This account uses an ...
-
- Some defective e-mail servers can't handle e-mails with subjects longer than 60-70 characters. They cut off the rest ...
-
- I was wondering if the @Project@ model way could be applied: source:/trunk/app/models/project.rb#L253
-
- More functions are available with the login name now.
show, edit, update, destroy, edit_membership and destroy_memb... -
- For consistency this could include @GET /users/[username].:format@, @GET /issues.:format?assigned_to_id=[username]@, ...
-
- Etienne Massip wrote:
> The problem with this patch is that it only works for issue creation/update.
>
> Maybe th... -
- Alexey Skor wrote:
> Thank you, Sridhar. I really hope this will be accepted by Redmine guys...
The problem with ... -
- This will work only when the "assigned_to_id" is NOT set and "assigned_to_name" is set. To be more specific, this wil...
-
- Thank you, Sridhar. I really hope this will be accepted by Redmine guys...
-
- 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"
> +OR+
> * Assignee IS "GROUP1"
>
> Which is admittedly ... -
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 ... -
- Yes, it's an accessor method to a DB column value.
Try to remove all the 'formatted_questions' you might find in t... -
11:31 Defect #9926: export issues to csv fails
- Etienne Massip wrote:
> What's the "formatted_questions" referring to?
>
> Do you have such a column selected in ... -
- What's the "formatted_questions" referring to?
Do you have such a column selected in the query columns? -
- Processing IssuesController#index to csv (for 10.220.3.218 at 2012-01-05 11:26:04) [GET]
Parameters: {"format"=>"c... -
- 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:26 Feature #4179: Link to user in wiki syntax
- +1
Also available in: Atom