Activity
From 2012-10-27 to 2012-10-29
2012-10-29
-
23:03 Defect #12253 (Closed): config.plugins setting does not works
- I tryed to set plugins load order via
config.plugins = [ :plugin_name_b, :plugin_name_a ]
in application.rb (how it pointed inside at comments), also i've tryed to do this in additional_enviroment.rb
Load order does not works :(... -
22:17 Feature #6836: Sort project list by Name instead of identifier
- Ken Zalewski wrote:
> I don't think your solution will keep projects ordered alphabetically as new projects are added.
Yes, it will keep them ordered. New projects are inserted in the proper lft/rgt position according to their names.... -
22:00 Feature #6836: Sort project list by Name instead of identifier
- Jean-Philippe,
I don't think your solution will keep projects ordered alphabetically as new projects are added. My fix outlined above in http://www.redmine.org/issues/6836#note-12 modifies the actual the left/right rebuilder, which w... -
19:03 Feature #6836: Sort project list by Name instead of identifier
- This was fixed in 2.1.0 (#11508). Ordering the project tree cannot be done using a simple @ORDER BY projects.name@ statement and would require some computation that is not required if lft and rgt values are properly set in the database. ...
-
15:34 Feature #6836: Sort project list by Name instead of identifier
- Florian,
See my comment above (http://www.redmine.org/issues/6836#note-12).
I explained exactly how you can sort projects alphabetically.
We also created an "Archive" project. We named it "~Archive", since the tilde is further ... -
14:25 Feature #6836: Sort project list by Name instead of identifier
- we have only a very limited number of projects. we love to create some sort of "archive"-root-project where closed projects are moved to and move the archive-project to the end of the list. simplest solution is to name it "zArchive". But...
-
20:37 Feature #3511: Ability to sort issues by grouped column
- Thanks!
-
19:33 Feature #3511 (Closed): Ability to sort issues by grouped column
- Implemented in r10765. You can sort issues by the grouped column in order to display groups in reverse order.
-
15:10 Feature #3511: Ability to sort issues by grouped column
- Jean-Philippe Lang wrote:
> The sort order when grouping by version is fixed in 2.1.0, it's now ascending.
But currently there is no way to define (by click) a descending order on some grouped field, or? -
20:37 Feature #6375: Last updated by colum in issue list
- +1
-
20:32 Defect #12252 (Closed): All Integration API Tests fail
- I'm probably doing something wrong, but I followed the instructions and common sense steps to run Integration tests for the API, and got the following result:
-
20:04 Feature #12251 (Closed): Custom fields: 'Multiple values' should be able to be checked and then unchecked
- In Administration --> Custom Fields --> Issues:
# Click on one of the custom fields that you have set up as a list.
# Select the "Multiple values" checkbox and click Save.
# Click into the same custom field again.
The "Multiple v... -
19:36 Defect #12241: Error creating tasks in crontab (Redmine 1.3)
- Thank you all! Problem was solved, prescribed path
-
19:05 Defect #12241 (Closed): Error creating tasks in crontab (Redmine 1.3)
- Please, no technical support in the issue tracker.
-
07:27 Defect #12241: Error creating tasks in crontab (Redmine 1.3)
- Ilya Levy wrote:
> No, i did not. In the console, without the crontab, the script works correctly.
Well i will try it on a testserver later. But, I think, that my current installation uses this feature too.
Some tipps:
# Check y... -
07:03 Defect #12241: Error creating tasks in crontab (Redmine 1.3)
- Toshi MARUYAMA wrote:
> ruby 1.8.7 (2010-04-19 patchlevel 253) is too old.
Yes, but in the console, without the crontab, the script works correctly. On the same Ruby 1.8.7.
-
07:02 Defect #12241: Error creating tasks in crontab (Redmine 1.3)
- Daniel Felix wrote:
> Have you tried this with a more recent version of Redmine (1.4.4 or 2.1.2) ?
No, i did not. In the console, without the crontab, the script works correctly. -
00:20 Defect #12241: Error creating tasks in crontab (Redmine 1.3)
- ruby 1.8.7 (2010-04-19 patchlevel 253) is too old.
-
18:32 Feature #12247 (Closed): How to import excel file to Redmine
- Same request as #7884.
-
16:30 Feature #12247 (Closed): How to import excel file to Redmine
- I create a document as excel file. In excel file, I create WBS and now I need import WBS to Redmine to track.
How to import from excel file?
Please help me.
-
18:23 Feature #12248: Grouped Filters
- Agreed.
-
16:40 Feature #12248 (Closed): Grouped Filters
- Hi,
it would be great to have those issue filters (for example) grouped.
In some case, especially in the new Version of Redmine, there are many many filters.
It would be great to have them grouped for a faster navigation and a b... -
17:29 Patch #7444 (Resolved): Patch for improved issue edit permissions
- Resolved, more or less, in #8050.
-
17:22 Feature #12249: Configurable required fields per tracker/role with 'Not visible'
- You are right, this tracker can be cancelled.
-
17:16 Feature #12249: Configurable required fields per tracker/role with 'Not visible'
- Seems to be a duplicate of: #12005
-
16:55 Feature #12249 (Closed): Configurable required fields per tracker/role with 'Not visible'
- As discussed in Feature #703, could it be possible to add 'Not visible' in new 'fields permissions' form of workflows ?
This will have many impacts on :
* issue form,
* notifications. They will be different per role. That will happen ... -
17:20 Patch #12237: Added German Translation
- Thanks for implementation. I think this could be closed. :-)
-
15:44 Patch #12237 (Reopened): Added German Translation
-
15:08 Patch #12237: Added German Translation
- Jean-Philippe Lang wrote:
> They are used in issue filters. Say you have a "Client" custom field on your projects, you can now filter issues by "Project's client" (issues that belong to all projects of a given client).
> ...
Thank you ... -
13:14 Patch #12237: Added German Translation
- Daniel Felix wrote:
> By the way... where can i find these labels to translate them to the right context?
> ...
They are used in issue filters. Say you have a "Client" custom field on your projects, you can now filter issues by "Projec... -
13:12 Patch #12237 (Closed): Added German Translation
- Committed, thanks.
-
17:18 Feature #12250: Configure order custom fields
- This could be enhanced by an project specific order for all ticket fields.
This way you could implement some things like
1. field = custom field, 2. field = Assign to, 3. field = custom field, 4. field = target version
etc. etc...
... -
17:05 Feature #12250 (New): Configure order custom fields
- I think a nice feature is add the possibility to modify the order inside the project of the custom fields.
-
15:11 Defect #6182: Localized decimal numbers
- +1
-
14:45 Feature #1263: Dokuwiki importer.
- +1
-
14:27 Defect #11918: Official git / github mirror of redmine repository is broken
- Confirming the issue. And I agree that such a mirror should be stopped if nobody feels responsible for it.
Besides this, I was wondering anyway why the mirror by Eric Davis was not used as a basis for the "official" mirror? Why did it... -
14:24 Patch #12246 (Closed): Japanese translation update (r10748)
- Committed in trunk r10762, thanks.
-
13:15 Patch #12246 (Closed): Japanese translation update (r10748)
- Translated @setting_non_working_week_days@.
-
14:03 Feature #2161: Time tracking code should respect weekends as "no work" days
- Jean-Philippe Lang wrote:
> Yes, it is already discussed in #7079.
Thx @ JPL, but I am not sure if the above mentioned ticket covers the whole topic. It seems that ticket #7079 describes only a subset of features: support for holiday... -
11:32 Feature #2161 (Closed): Time tracking code should respect weekends as "no work" days
- > 2.2.0 will implement the basic feature as requested by the author of this ticket: a global setting to define non working week days (eg: saturday, sunday). The issue planning code will be aware of that, eg. rescheduling an issue will ta...
-
13:11 Patch #12245 (Closed): German Translation for #2161
- Committed, thanks.
-
12:13 Patch #12245 (Closed): German Translation for #2161
- Please translate
setting_non_working_week_days: Non-working days
to:
setting_non_working_week_days: Arbeitsfreie Tage
Sry for the missing patch, but i haven't any Sourcecodesystem currently available.
Maybe #12237 could be im... -
12:53 Feature #3265 (Closed): Filter on issue relations
-
12:03 Feature #3265: Filter on issue relations
- I tested the current implementation. Seems to work as expected. Maybe this one could be closed. :-)
-
12:03 Defect #12244 (Closed): Preview Layout breaks on large images
- I noticed some misbehaviour on IE9.
I seen this on Freature request #12243.
If the window is too small to display the whole image, the ticket display gets many pagebreaks.
Adding "overflow: scroll" or "overflow: hidden" solve th... -
11:35 Feature #12216 (Closed): Textual CSS class for priorities
-
11:34 Feature #7082 (Closed): Rest API for wiki
- Wiki pages can now be retrieved, created, updated and deleted through the REST API. See [[Rest_WikiPages]].
Any additional features should be requested in a separate issue. -
10:56 Defect #12243 (Closed): Ordering forum replies by last reply date is broken
- Would be very nice allow to sort by last reply date in forums. I think is not possible now.
Something like this:
!http://s7.postimage.org/zdb325mh7/forum_replies.png!
Thanks!! -
10:44 Feature #12005: Mightful workflow field enhancement: hide
- Most recent version of my patch is 0.03, sorry I did not put any versioning in my first pulication.
-
10:08 Feature #2024: gantt chart editing
- +1, changing due dates for many tickets (e.g. in case of sickness or some new, prioritized customer requirements) is a huge pain in the current version.
It is definately a "must have" feature! A perfect complement to the excludation o... -
10:02 Defect #11752: Internal error when view the diff when using the redmine with git
- h2. Solution
*Upgrade Ruby version to 1.9.3*
2012-10-28
-
22:50 Defect #12241: Error creating tasks in crontab (Redmine 1.3)
- Have you tried this with a more recent version of Redmine (1.4.4 or 2.1.2) ?
-
22:34 Defect #12241 (Closed): Error creating tasks in crontab (Redmine 1.3)
- Hello!
Redmine Version 1.3
Please help.
I'm trying to set up a crontab tasks are received by mail.
run crontab -
22:11 Feature #12240 (Closed): Check for duplicate/related tickets before submitting
- Same as #5840.
http://www.redmine.org/projects/redmine/search?utf8=%E2%9C%93&issues=1&q=%22Did+You+Mean%22 -
22:06 Feature #12240 (Closed): Check for duplicate/related tickets before submitting
- *Everyone* makes an effort to do a search before submitting a new entry to check and see if it has already been submitted before but when you have a large user base this can be hard to enforce.
It would be nice to show some possible r... -
22:03 Feature #2208 (Closed): Workflow: only Issue Reporter can close
-
19:24 Feature #2208: Workflow: only Issue Reporter can close
- This ticket could also be closed. The workflow system could handle this too. This is implemented by #8050
-
22:00 Feature #12239 (Closed): Translateable Notifications
- Hi,
it would be great to have translateable notifications.
Even if I changed my preferences to german, I still get notified in english.
Example:
Issue #1798 has been updated by Jean-Philippe Lang.
Status changed from New to Clos... -
21:51 Feature #1798 (Closed): Permission control for issue due date
-
19:10 Feature #1798: Permission control for issue due date
- This ticket could be closed too.
The request could be solved by using worflow with read only fields. -
21:49 Feature #2051 (Closed): Code view/pre div width
- Indeed.
-
19:04 Feature #2051: Code view/pre div width
- Well i think, this ticket could be closed too. Doesn't it?
-
21:48 Feature #2098 (Closed): Role issues
- Indeed.
-
18:52 Feature #2098: Role issues
- Well i think this could be closed since there is the possibility to assign tickets to groups which contains multiple users. Each user gets notified about the new ticket. The administrator just needs to enable "assign tickets to groups".
-
21:42 Defect #12231 (Closed): Hardcoded "Back" in Repository
- Fixed in r10745, thanks.
-
21:28 Defect #12231: Hardcoded "Back" in Repository
- I'm using git as sourcecode repository.
If this repository hasn't any commit in it, an error message will be generated.
The URL, where this error message would appear is something like: http://www.redmine.org/projects/redmine/reposit... -
21:00 Defect #12231: Hardcoded "Back" in Repository
- Which view? Please give an URL where you see that.
-
21:06 Feature #11542: Improve password security and use some standards.
- While you might not call it brute forcing, when using a large dictionary it essentially is. Every second thus gained via the use of bcrypt or scrypt is a real pia for the attacker.
I wonder if this can be made into a plugin, but consid... -
19:46 Defect #1185 (Closed): Login using Mac OS X OpenDirectory (LDAP) not working
-
19:30 Defect #1185: Login using Mac OS X OpenDirectory (LDAP) not working
- Well, it seems that this Ticket could be closed too?
-
19:38 Defect #2736: Links hard to distinguish
- Well i think this could be closed?
If you want, you can define additional styles in a own theme with a application.css. :-) -
19:37 Defect #2511: Overlapping area in Issue entry
- I just tested it with the latest safari. This misbehaviour doesn't appear anymore with current trunk 10742. Maybe this ticket could be closed?
-
19:33 Defect #1662: Issue's custom fields don't appear on some filters and custom queries editor
- I'm still able to reproduce this in current trunk (10742).
-
19:23 Feature #393: Role that can't assign a ticket
- Well this could be also closed. With some changes to the workflow -> field permissions the reporter could be restricted to assign a ticket.
-
19:20 Feature #824: Add "closed_on" issue field (storing time of last closing) & add it as a column and filter on the issue list.
- +1 for core implementation.
-
19:18 Feature #1800: Changelog creator
- +1 from me!
Would be quite useful for bigger projects (like Redmine too). -
19:17 Feature #1358: Link_to for Custom Field
- Well some simple type of custom field format like "link" would be quite useful. This would be quite helpful even if no id replacement would be done.
Linking to tickets and revisions is currently implemented. -
19:08 Feature #1823: Yes/No Vote for "Can replicate issue?"
- This one could be implemented with #11655 and #1011.
This would be something like Atlassian Jira. -
19:06 Feature #2024: gantt chart editing
- +1 from me to add this to the core.
-
19:01 Feature #2033: Role based notification settings
- +1 from me
-
19:00 Feature #2026: Improve E-Mail notification templates
- Well, i like the current format of those report mails. it is short and give the latest informations direct on top of the correspondig mail.
As another suggestion:
Maybe add the possibility to customize those email-reports on a easy w... -
18:54 Feature #2093: Text over the "New Issue" Area
- Hi there,
I don't know if this is still useful?
You can search or categorize tickets by their projects in combination of tracker anyway. So I don't see the use case for this feature?
Best regards,
Daniel -
18:50 Feature #2183: Avoid potential awkwardness in adding custom boolean fields to existing projects
- +1 for this feature.
I currently expected the same behaviour.
With the abbility to "push" those default value to every databasefield which is "null" (just a simple update query) would be great!
existing fields shouldn't be updat... -
18:46 Feature #2039: Generate strong passwords
- Well, it would be quite useful to add a button "generate password" in the userregistration (administration -> users).
This way, the admin has the abbility to generate secure passwords, without knowing the user password. -
18:44 Feature #2045: query work time data of one member
- This thing could be solved with this feature: #10191
-
18:41 Feature #2199: Ability to clear dates and text fields when bulk editing issues
- Those datepicker just need some "unset" button.
Maybe those changefield need always a checkbox like "unset" aside every item. -
18:33 Feature #2214: Autocreate repositories
- This could be useful two for some administrator who don't want to run the repoman every minute or every 15 minutes, but always want to have simple and fast repositories.
Another kind of idea how to implement this:
- Add some checkbox... -
18:30 Feature #2223: Choose which subprojects are include on the activity page
- This would be quite useful for some projects like forge.typo3.org which have a huge count of subprojects (for example: typo3 version 4 - activity). There is a pulldown menu for all of the subprojects.
If you select the project activi... -
18:21 Feature #2272: Redmine on Oracle Database - Windows Installation
- In my opinion, this ticket could be closed, doesn't it?
-
18:13 Defect #11752: Internal error when view the diff when using the redmine with git
- File views* is blank 0 byte files.
Is it ok? -
08:41 Defect #11752: Internal error when view the diff when using the redmine with git
- <% cache(@cache_key, nil) do -%>
Not work. -
18:11 Patch #12237 (Closed): Added German Translation
- Hi,
again a language patch.
By the way... where can i find these labels to translate them to the right context?
label_attribute_of_project: Project's %{name}
label_attribute_of_author: Author's %{name}
label_attribute_of_a... -
18:04 Feature #12182: improvement password security for internal authentication
- Maybe some kind of "Password has to be different to the last x passwords". Something like in the Windows-Authentication, where users can't change their password to some password used 12 changes before.
This could prevent some lazy peop... -
16:38
Feature #12182: improvement password security for internal authentication
- some suggestions for switchable / adjustable rules (additional to the length):
* don't accept the name or parts of the name (switch)
* don't accept sequenced numbers, letters or signs... (switch)
* the password has to contain:
> smal... -
18:00 Feature #12236: Option to make Comment field required
- +1
-
08:26 Feature #12236 (Closed): Option to make Comment field required
- It will be very useful to have an option to have Comment field required
Especially for billing, - it hard for sell time if no description available.
[[RedmineTimeTracking]] -
17:59 Feature #10191: Add Filters For Spent time's Details and Report
- +1 from me!
-
06:47 Feature #10191: Add Filters For Spent time's Details and Report
- It will be essential to add option to add custom attributes to the report columns, similar to issues.
Sorry - last sentence is addressed by #1766 -
06:42 Feature #10191: Add Filters For Spent time's Details and Report
- +1
-
09:01 Patch #12232 (Closed): German translation enhancements
- Committed in trunk r10733, r10734, r10735 and 2.1-stable r10738, thanks.
-
09:00 Patch #12235 (Closed): German translation for 2.1-stable
- Committed in trunk r10733 and 2.1-stable r10738.
-
02:31 Patch #12235 (Closed): German translation for 2.1-stable
- This is a patch from #12232.
-
07:35 Feature #12228: JRuby 1.7.2 support
- CVS tests pass on my Fedora 13.
-
02:42 Feature #976 (Closed): add button
- Daniel Felix wrote:
> This feature seems to be implemented too. If I click on some Ticket in can navigate throw my ticketlist using prev or next.
Indeed. This request is superseded by #2850 (Redmine >= version#40). Closing as such. -
02:29 Feature #583 (Closed): Make "Assign To" field read only or disabled for certain roles.
- Daniel Felix wrote:
> This ticket could be closed.
Indeed.
> ...
This request is superseded by r9977 for #3521 (Redmine >= version#47), reflecting this with a duplicates relation for reference.
2012-10-27
-
23:16 Feature #12234 (Closed): Widget-Links should be translateable per widget.
- Currently, they seem to use all the same translation key.
If a use has 3 Widgets on "My Page". For example: My Tickets, Tickets assigned to me, Tickets watched by me.
He gets 3 Links: "View all Tickets".
Which seems to be syntactica... -
23:13 Feature #895: Add "My tickets" to topmost menu
- Well, those "All Tickets" or "My Tickets" could be already seen on "My Page". If you add the corresponding widgets, you can always see, which tasks are still open for you.
-
23:09 Feature #1137: Project version
- Manual sorting isn't implemented till now, but the Versionlist is implicit sorted by release date.
-
23:06 Feature #976: add button
- This feature seems to be implemented too. If I click on some Ticket in can navigate throw my ticketlist using prev or next.
-
23:04 Feature #683: Cross project reporting
- Well, this could be already made.
Just go to "Projects" and select "All Tickets" and add some Filters like "Projekt" or "Assigned to...".
After defining this, just save those custom report and call it whenever you want. :-) -
23:01 Feature #727: New issue style
- Well, this could be implemented by a simple own style based on the default style for example, doesn't it? :-)
I don't think that this should be declared as new feature. -
22:59 Feature #742: improved admin page navigation
- Well, this could be an interesting enhancement for administrators. Maybe this could speed up the daily configuration work for bigger projects?
-
22:56 Feature #557: Changing user preferrences
- This is now possible. Those default settings could be set in the administration -> configuration -> notifications.
But for some reasons, there is no setting to enable or disable the default behaviour of the checkbox for "notify me for... -
22:53 Feature #571: Configurable "Display project descriptions" in project list
- Maybe this could be implemented with a duplication of this description field.
One type of description field (for project list for example) and one type of "welcome message" or something like this which is displayed on the home page of... -
22:51 Feature #583: Make "Assign To" field read only or disabled for certain roles.
- This ticket could be closed.
You can define on a per role basis that "assigned to" could be read-only. -
22:49 Feature #578: Activity report displays added notes as well
- Most information is already available in ticket history.
Only logged time isn't implemented. This could be solved with #5061. -
22:46 Feature #565: Mark expired tasks
- This is a smaller implementation of #12222.
The first thing "Mark exceed Due Date" could be implemented by adding a css rule like tr.overdue{ background-color:#FF0000; }
All needed information could be found in the sourcecode of your... -
22:40 Feature #546: Assign categories to multiple users
- This can be configured by mapping some category to a usergroup which contains multiple users.
Maybe this Ticket could be closed? -
21:06 Patch #12232 (Closed): German translation enhancements
- Hi there,
in the attached file, you could find some improvements to the current german translation and the translation for the new items.
Best regards,
Daniel -
21:02 Defect #12231 (Closed): Hardcoded "Back" in Repository
- Hi there,
it seems, that this "Back"-Link is hardcoded. I can't find it in the whole translation?
But I can't find it in the sourcefiles. Maybe you have a better idea where I can find it.
button_back would be a better translatio... -
20:32 Feature #12230 (Closed): Make format help translateable
- The redmine text format help (like in new ticket, above the textarea) isn't translateable.
In order that all other things are translateable, this should be handled as all the rest. -
16:01 Defect #12213 (Closed): SVN integration Error with redmine
-
11:01 Defect #12213 (Resolved): SVN integration Error with redmine
-
15:25 Feature #6902: Allow priorities to be associated to Trackers.
- I think this would be a great addition, as we too could use different priorities depending on which tracker.
-
10:55 Defect #12229: Database connection fails with % in password
- Thank you!
Just tested it! -
10:50 Defect #12229 (Closed): Database connection fails with % in password
- Yes, that should work with double quotes:
-
10:41 Defect #12229: Database connection fails with % in password
- No i used the example config and changed the password.
For Example:
production:
password: test%test /* fails */
production:
password: testtest /* works */
Maybe those do quotes should be added in the example, like in the... -
09:15 Defect #12229: Database connection fails with % in password
- Do you use double quotes to wrap your password in database.yml?
-
08:54 Defect #12229 (Closed): Database connection fails with % in password
- Hi,
the database connection fails, if % is defined inside the password. Maybe this isn't automatically escaped?
Best regards,
Daniel -
10:54 Feature #8050 (Closed): Mightful workflow field enhancement: visible, read only and mandatory
- I'm closing it in favour of #12005 now that the read-only/required part of this request is implemented.
-
10:46 Feature #5061: Show time log entries in issue history
- +1
-
10:36 Feature #12211 (Closed): Wrap issue description and its contextual menu in a div
- Done in r10728. Look for @div.description@.
-
10:21 Feature #12198 (Closed): Show related work for a ticket
- Same as #5061.
-
09:29 Feature #12228: JRuby 1.7.2 support
- Toshi, that would be great if you could have a look at the CVS issues with JRuby.
-
09:13 Feature #12228: JRuby 1.7.2 support
- CVS tests fails with JRuby on Windows:
* @@repository.fetch_changesets@ only loads 5 changesets (instead of 7)
* rake test dies on @test\functional\repositories_cvs_controller_test.rb@ -
08:14 Feature #12228 (Closed): JRuby 1.7.2 support
-
09:16 Feature #12182: improvement password security for internal authentication
- > further adjustable rules
Yes, could you list a few examples of the rules you expect? -
08:47 Feature #6154: Save issue as draft
- +1!
I like to have this in the next major release. This would be quite useful for developers which have to switch often between two or more tickets. -
08:45 Feature #9734: Custom field , value list from database query
- +1
-
08:40 Defect #12227: Unable to Login with the Quote " Symbol in Password Using LDAP Authentication
- Works OK with Redmine 2.1 and Openldap. I've tested with quotes and double-quotes in the LDAP password.
-
08:11 Feature #12225 (Closed): (Automatic) Draft Save
- Same as #6154.
http://www.redmine.org/projects/redmine/search?q=draft&scope=&all_words=&all_words=1&titles_only=&titles_only=1&issues=1 -
08:09 Feature #12224 (Closed): Custom Fields with SQL Format
- Same as #9734.
-
08:07 Defect #12226 (Closed): Subject field can be edited by everyone
- Users with "edit issues" privileges can edit the subject and the description. It can be disabled by making some fields read-only for certain stauses. You've got 2 options:
* make the subject and description read-only except for the "New...