Activity
From 2012-11-20 to 2012-11-22
2012-11-22
-
21:30 Patch #4274: Use Issue status for percent done
- I want to use this setting, but I have to reluctantly because it affects all projects.
Can this be "fixed", such that it can be implemented at the project, tracker, [other?] levels setting vs. just at the application level settings?
... -
21:29 Feature #4015: Make app settings overridable at project level
- +1 and +1 Matthew Burton.
It seems the burden is mainly due to the "project-y" settings being mixed with the "application-y" settings. For example, configuring "Default columns displayed on the issue list" in the application level se... -
17:27 Defect #12424 (Closed): Impossible to create a new issue : Display Problem in IE 8
- Hello
My issue is that I can't create an issue under IE, because a part of the UI is missing !!
and I have a warning message in IE (see attached files)!!
-------------
Message: HTML Parsing Error: Unable to modify the parent contai... -
17:05 Feature #12423 (New): Buffertime should be changeable
- Hi,
if I define some following or preceding ticket relation, there is no way to edit the buffer time after creating these relation.
I always need to delete and recreate those ticket relation, which always tempted to make some error... -
17:00 Defect #5803: Precedes/Follows Relationships Broke
- evandro bubiak wrote:
> still occurs on version 2.x
I can confirm this with the current trunk (r10864).
JiuG Neiva wrote:
> ...
This still seems to apply. Changes which sets the due date to an earlier date are ignored, only chang... -
16:25 Defect #5803: Precedes/Follows Relationships Broke
- still occurs on version 2.x
-
14:17 Feature #7842: Creation new users by non-admin user
- +1
It would be great :) -
11:29 Feature #11329: Private custom fields
- Well, this one seems to be solved by #8050 and #12005.
You can define some workflow, where some role has write or just read rights, even for custome fields (#8050). Additionally, you can define if these custom field is visible or just... -
10:35 Feature #11329: Private custom fields
- +1 This feature is really useful.
-
11:29 Feature #4707: private fields
- Well, this one seems to be solved by #8050 and #12005.
You can define some workflow, where some role has write or just read rights, even for custome fields (#8050). Additionally, you can define if these custom field is visible or just... -
09:50 Defect #12400: Validation fails when receiving an email with list custom fields
- Hi,
Sorry for my very bad english.
For custom field of example provided, those are valid values:
ADMINISTRACION
COMERCIAL
COMPRAS
CG
DIRECCION
DISEÑO
DISTRIBUCION
FABRICACION
I+C
INFORMATICA
INVENTARIOS
LOGISTICA
RRHH
RSC... -
04:56 Patch #5886: bash scanner for Coderay/ Redmine
- zeerd emneg wrote:
> I am sorry , but the last url 1 year ago was invalid , too.
> ...
You can download it from http://dragula.org/attachments/download/421/bash.rb , or you can download from the attachment of this post.
Thank you. -
04:21 Patch #5886: bash scanner for Coderay/ Redmine
- I am sorry , but the last url 1 year ago was invalid , too.
It return "403 Forbidden".
Could you just upload it here? -
04:44 Feature #12416: Comment change notification
- As we need quick communications, I think, it's better to make a checkbox "Notify about changes" under the editing field to let user choose to send the notification or not. Also, for us it would be better if the checkbox is set by default.
2012-11-21
-
21:46 Feature #12393 (Closed): Upgrade to Rails 3.2.9
-
21:45 Defect #12396 (Closed): Error when receiving an email without subject header
- Merged in 2.1-stable.
-
21:27 Defect #12396: Error when receiving an email without subject header
- Thanks for the feedback.
-
21:33 Defect #12336 (Closed): SVN repository is down
-
21:31 Feature #5215: Automatically notify project managers for unassigned tickets
- +1
-
21:28 Feature #5262: Different priority levels for different trackers
- +1
-
21:21 Feature #12416: Comment change notification
- This shall be optionaly configureable by user, because if you correct some grammar in the comment, it will send to many emails for nearly the same information.
Other solution: Wait 15 minutes witout chnaange again or so, and then send "... -
11:17 Feature #12416 (New): Comment change notification
- Now, when someone changes his comment in an issue, no notification is sent about it. So, if a user comments an issue, then changes his comment, then other users get notification with first version of the comment, and don't get its change...
-
21:19 Feature #1248: New Permission: Edit own issues
- +1 - very useful for redmine.org itself
-
17:44 Feature #1248: New Permission: Edit own issues
- This would be an excellent feature to allow our client to edit the mistakes on its own created issues without having us to deal with it through a note left on this same issue by him. +1
-
21:18 Defect #12400: Validation fails when receiving an email with list custom fields
- What are the exact valid values for this custom field?
-
10:10 Defect #12400: Validation fails when receiving an email with list custom fields
- Sorry for my very bad english.
More data to problem:
Validation of custom fields only fail with custom field type "list".
All others custom fields are validated fine.
Thanks for any help. -
21:15 Defect #12412 (Closed): Add/Edit Trackers
- Open a Rails console with @`ruby script\rails c production`@ then run the following command:
-
21:14 Feature #12228: JRuby 1.7.2 support
- +1
-
18:30 Feature #12421 (Closed): JRuby 1.7 support
- Dupe of #12228.
-
17:40 Feature #12421 (Closed): JRuby 1.7 support
- Please expand testing for JRuby 1.7
-
16:59 Defect #12420 (Closed): URLs in notification emails do not include the sub-URI
- I have Redmine working as configured in #11881, #12102, etc. Everything seems to be working except that issue URLs in the notification emails generated by Redmine do not include the sub-URI. For example... @http://my.domain.com/issues/71...
-
16:59 Defect #9842: {{toc}} is not replaced by table of content when exporting wiki page to pdf
- +1
Macro in general -
15:09 Feature #12404: User can view limited attached docs as per the defined duration by administartor.
- Please help me anyone.
-
11:25 Defect #12399 (Closed): Non ASCII attachment filename encoding broken (MOJIBAKE) in receiving mail on Ruby 1.8
- Committed in trunk r10852, r10853 and 2.1-stable r10854, r10855.
-
06:40 Feature #2356: SSO Authentication (CAS Jasig)
- "Same question as Thomas", will this patch work with Redmine 2.x (esspecially 2.1)?
And next question is if this can be implemented as the plugin? -
01:21 Feature #3207: Better Breadcrumbs
- +1
2012-11-20
-
22:55 Feature #8991: Nested versions for projects with sub-projects
- Asaf, what you describe would be the perfect match to the needs of our Redmine.
And I guess the needs of other people too.
Now the question is what does it mean regarding the code ? Is it a heavy change ? Is anyone familiar with this... -
21:25 Feature #12413 (Closed): Support per-language email footer/header
- Current email header/footer in notifications is only one block (default in English).
It would be useful to be able to localize it to match the user's preferences. -
20:28 Feature #5754: Allow addition of watchers via bulk edit context menu
- +1
-
19:43 Defect #12412 (Closed): Add/Edit Trackers
- When adding a new tracker or editing an existing tracker from within the administration screen, an internal 500 error is returned. Note that an existing tracker can successfully be deleted or sorted.
*Environment:*++ -
19:35 Feature #5262: Different priority levels for different trackers
- this is very usefull. could you say status of this feature?
-
18:09 Defect #10808 (Resolved): Update time zones for Russia
- I wrote about it 7 month ago and then it was actually. After some time, this has been corrected. This task can be closed. Thank you.
-
15:02 Defect #12409 (New): Git: changesets aren't read after clear_changesets call
-
14:57 Defect #12409: Git: changesets aren't read after clear_changesets call
- How has it been solved?
-
14:48
Defect #12409 (Resolved): Git: changesets aren't read after clear_changesets call
-
13:07 Defect #12409 (Closed): Git: changesets aren't read after clear_changesets call
- Changesets aren't read after clear_changesets call at least in case of Git. The method clear_changesets clears all changesets but leaves extra_info in repositories table and therefore changesets aren't read after clear_changesets call.
... -
12:21 Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- btw, the above only applies to the "New issue" form. The issues display itself seems to work as expected.
-
12:07 Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- Hello,
first of all thanks alot for this patch, helps alot to cover our usecases!
I just applied workflow_hidden_field_v0.03.diff to Redmine 2.1.3. It seems that the field permissions are screwed up somehow. Here are the results of... -
11:44 Feature #11724: Prevent users from seeing other users based on their project membership
- You should check out http://www.redmine.org/boards/1/topics/4143
They post a solution to manually change some files to change what certain members can see.
I still think this should remain a feature for a future version so we don't h... -
11:26 Feature #12401: Split "Manage documents" permission into create, edit and delete permissions
- It worked perfectly!
However, I'm also a need permission by document type. Very difficult? -
00:26 Feature #12401: Split "Manage documents" permission into create, edit and delete permissions
- Perfect!
+1
-
00:03 Feature #12401: Split "Manage documents" permission into create, edit and delete permissions
- Instead of "Manage Documents" which was too abstract for our purposes, I separated the permissions into "Add Documents", "Edit Documents", and "Delete Documents". I also left the "View Documents" permission in place.
-
00:01 Feature #12401: Split "Manage documents" permission into create, edit and delete permissions
- Sound intesting.
So which new rights did you add? -
11:20 Feature #12362: Sharing Issue categories
- You already have a ticket for this at:
http://www.redmine.org/issues/5358
With a great patch available that I use.
Should be closed as duplicate. -
10:15 Feature #5215: Automatically notify project managers for unassigned tickets
- I would be also glad to have this feature - is it going to be implemented?
-
09:49 Feature #3413: Exclude attachments from incoming emails based on file name
- Sorry, previous file included patch to .gitignore file :)
This one only includes small patch to mail_handler.rb model.
-
09:46 Feature #3413: Exclude attachments from incoming emails based on file name
- Please check this patch which skips inline attachments, mostly signatures.
Patch made to current trunk version. -
08:07 Feature #12404 (New): User can view limited attached docs as per the defined duration by administartor.
- As per my project requirement,the user can view only for particular duration(ie last 7 days,last 15 days etc) attached docs.It is based on user profile where administrator can define the cutoff date(days).Please do the needful.
regrds... -
01:30 Feature #4179: Link to user in wiki syntax
- Just wanted to let you know, that it has been implemented in "WikiNG":http://projects.andriylesyuk.com/projects/wiking...
-
00:50 Feature #11619: Ability To Have Redmine Issue Update Notifications Send Full Ticket History
- related/dupe of "Advanced notification: per user, per project configurable schedule, event filter and notification format" #8241
-
00:22 Feature #8417: per tracker configurable issue form layout with preview
- Ping! Hopefully this issue form layout designer gets some attention.
-
00:21 Defect #11918: Official git / github mirror of redmine repository is broken
- Alexander Oryol wrote:
> Guys, "rubyforge mirror":http://svn.redmine.org/redmine/ is alive! Please, sync http://github/redmine/redmine
> ...
It's not alive through "svn": -
00:10 Feature #12005: Mightful workflow field enhancement: hide
- Please release with 2.2.0 it will make "Mightful workflow field enhancement" complete! ;)
-
00:05 Feature #5037: Role-based issue custom field visibility
- related (dupe) of Mightful workflow field enhancement: hide #12005