Activity
From 2012-03-07 to 2012-03-09
2012-03-09
-
23:06 Feature #9076 (Reopened): Allow to prefill issue form via http url parameter
- We need to prefill description and custom fields of type list, version, text and user. Can't find and example in wiki.
-
22:28 Feature #9076 (Closed): Allow to prefill issue form via http url parameter
- Actually, it's already possible using the following syntax:
http://www.redmine.org/projects/redmine/issues/new?issue[tracker_id]=2&issue[category_id]=1 -
22:14 Defect #10414: Duplicated Message-Id in headers of mails send by Redmine
- > If a modification is made on the same issue the message Id can be the same
How to reproduce? Because when an update is done on an issue, this is the timestamp of the journal that is used, not the issue timestamp. -
19:16 Defect #10414: Duplicated Message-Id in headers of mails send by Redmine
- It's candidate =)
From what I've seen, it seems that @Original-Message-ID@ header is more usable then @References@ which should list all the ids of all the messages of the conversation. -
18:09 Defect #10414: Duplicated Message-Id in headers of mails send by Redmine
- That's it, the conversation id is called *references*.
Thanks to have integrated the patch in the next minor release. -
18:01 Defect #10414: Duplicated Message-Id in headers of mails send by Redmine
- It is not.
-
17:52 Defect #10414: Duplicated Message-Id in headers of mails send by Redmine
- Isn't the message id the conversation id? If yes, it does not seem too weird to have the same id for every update of a specific issue?
-
17:46 Defect #10414: Duplicated Message-Id in headers of mails send by Redmine
- The only case that seems odd is the table wiki_contents that as an updated_on field but no created_on one.
Anyway the patch as the original code always fallback on the existing field.
The patch just finds the more accurate informatio... -
17:27 Defect #10414 (Closed): Duplicated Message-Id in headers of mails send by Redmine
- If a modification is made on the same issue the message Id can be the same :
-
19:41 Feature #7402: REST API - Enumerations
- +1
We need this feature for "RedmineNB":http://kenai.com/projects/redminenb (NetBeans Plugin for integration with Redmine). -
18:55 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
16:52 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
16:34 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
16:32 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
02:37 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
18:19 Defect #9798: Release 1.3.0 does not detect rubytree under ruby 1.9.3p0 / rails 2.3.14
- Re,
Sorry, I followed steps described on the following page http://www.redmine.org/projects/redmine/wiki/HowTo_Install_Redmine_in_a_sub-URI_on_Windows_with_Apache and everything seems to be ok now.
I probably mixed bad versions of ... -
16:34 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- -
-
16:32 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- -
-
16:07 Defect #10413: Creating wiki pages with special characters may be problematic
- There is also a problem when using these characters in a wiki text (may be related with this issue, so I post it here): If I write a percent sign directly followd by a comma, the percent sign isn't shown in the resulting wiki page (only ...
-
15:51 Defect #10413 (Confirmed): Creating wiki pages with special characters may be problematic
-
15:42 Defect #10413 (Closed): Creating wiki pages with special characters may be problematic
- I recently noticed some little quirks when creating wiki pages with certain special characters.
For instance, I can write on a wiki page a link to a new page as ![[M&P]]. As soon as I click on submit, the link to this page is shown in t... -
15:55 Feature #10412: Target version filter shoud group versions by status
- Not specific to Gantt.
-
15:01 Feature #10412 (Closed): Target version filter shoud group versions by status
- ON the Gantt chart, when filtering target versions, the combo showing the possible target versions to be filtered shows all versions. This is annoying if you have lots of closed versions. It would be nice if it showed only opened versions.
-
15:52 Defect #10409 (Closed): Spent Time error cannot log hours
- Thanks.
-
15:49 Defect #10409 (Resolved): Spent Time error cannot log hours
- You can close this case, it wasn't a Redmine issue , just a plugin issue.
-
15:49 Defect #10409: Spent Time error cannot log hours
- I uninstalled CMI and Spent Time now works. There are some serios issues with that Plugin, I highly recommend you remove it until they get it figured out. The Translation is the easy part, The intent is good, It just is not functional.
-
15:48 Defect #10409: Spent Time error cannot log hours
- Did you try without plugins, especially without CMI?
-
15:35 Defect #10409: Spent Time error cannot log hours
- Redmine 1.3.1
- Apache 2.2.22
- ImageMagick 6.5.6-8-Q8
- MySQL 5.0.83
- Subversion 1.7.1
- Ruby 1.8.7-p334-i386-mingw32
- Rails 2.3.14
- RubyGems 1.6.2
Plugins
CMI
Issue Checklist
Better Gannt Chart-
10:21 Defect #10409: Spent Time error cannot log hours
- What Redmine version, any plugins, etc. (see [[SubmittingBugs]])?
-
14:44 Defect #10411 (Closed): no such file to load -- bundler error when loading redmine
-
14:11 Defect #10411: no such file to load -- bundler error when loading redmine
- 1.3 does not use Bundler.
1.4/trunk does and you need to install the Bundler gem (@gem install bundler@), see source:/trunk/doc/INSTALL -
13:11 Defect #10411 (Closed): no such file to load -- bundler error when loading redmine
- I am suddenly failing to load our redmine application from the browser. I get the following error:
Error Message:
no such file to load -- bundler
Exception class:
LoadError
Application root:
/var/www/redmine
Backtrace:
# ... -
12:41 Defect #10410 (Closed): [Localization] Grammar issue of Simplified Chinese in zh.yml
- Committed in trunk r9165, thanks.
-
11:50 Defect #10410 (Closed): [Localization] Grammar issue of Simplified Chinese in zh.yml
- In History section of an issue, "Updated by xxxx *over x years* ago" is translated as "由 xxx 更新于 *x 年以上* 之前".(See ex. here: http://www.redmine.org/issues/263)
A better translation should be "由 xxx 更新于 *超过 x 年* 之前", referring to Tradit... -
10:47 Defect #9824: Visual merge/branch history words are cut off
- Denny Schäfer wrote:
> In the visual merge/branch history the word are cut off. For example the word *master* is cut off after *m*.
I can reproduce the behaviour quite easily. It seems that when there is not enough branches to increa...
2012-03-08
-
22:41 Feature #9601: Multi language wiki
- So, what next?
This feature will be implemented? -
22:32 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- I actually think the batching is a great idea in conjunction with the original git optimizations that eliminate revisions that have already been processed, but all the processing needs to be protected by a transaction, including the last...
-
22:14 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
21:28 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Gergely Fábián wrote:
> Jeremy Bopp wrote:
> ...
In other words, remove the db query grouping.
I made a patch for this version. It applies on top of current trunk/master (where my changes are already committed; git: 036b81abfd552bb9df... -
22:14 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- -
-
09:45 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- Thank you Jean-Philippe for this suggestion as it seems more efficient.
Thank you Brice for the update.
I hope this will get to the next release :) -
09:39 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- sorry i forgot an underscore in show.api.rsb file.
-
09:35 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- It's done in this patch
-
08:09 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- something like this in index.api.rsb ?
api.full_description version.wiki_page.content.text if version.wiki_page
-
22:01 Feature #6833: Spent time in a configurable unit
- Sorry for the long time to update, I haven't got the time with my job...
I have done some change, and right now, that should work! -
21:09 Feature #9076: Allow to prefill issue form via http url parameter
- +1
-
15:03 Feature #9076: Allow to prefill issue form via http url parameter
- Hi, +1 for this feature.
For us, it's really important - we need it for creating a "smart quick links" for our clients.
Thank you. -
20:51 Defect #10409 (Closed): Spent Time error cannot log hours
- Log message as follows:
10.1.4.195 - - [08/Mar/2012:14:49:18 -0500] "GET /redmine/issues/5/time_entries/new HTTP/1.1" 304 -
10.1.4.195 - - [08/Mar/2012:14:49:21 -0500] "POST /redmine/projects/msc/timelog/create HTTP/1.1" 500 674
-
19:02 Feature #10408 (New): Support More Hyperlink Protocols in the Wiki Formatter (textile/formatter.rb)
- The wiki formatter, while awesome, only supports a few protocols for the auto linking (AUTO_LINK_RE).
So, I made this little hack to get it to support almost anything
This in-line patch is against 1.3.0 and hasn't crashed mine (yet!) :0 -
18:20 Defect #7335: Sorting issues in gantt by date, not by id
- +1
-
17:35 Feature #10406: Wiki tree bulk edit
- There is a plugin for Redmine called something like "wiki book" in fact, but it's function is to add another layer, a "book" object that stores an ordered list of wiki pages from the project, rather than actually modifying the stored inh...
-
17:27 Feature #10406: Wiki tree bulk edit
- I was wondering if there already exists some "Wiki book" concept implemented in some wiki dedicated software?
Not only to maintain a structure of pages, but also for their translation and versioning/tagging. -
17:05 Feature #10406 (New): Wiki tree bulk edit
- # The user can navigate to a tree structure editing page.
# On the page, the user sees the list of pages in the wiki.
## The list is dynamically generated.
## The list displays hierarchy to reflect the existing wiki tree structure.
... -
17:11 Feature #10407 (New): Wiki page has a tree weight
- A wiki page can have a weight, and therefore order, that supersedes alphabetical sorting in a family of a tree branch.
-
16:57
Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- +1
Would be very useful for implementing roles like 'product manager'. -
16:51 Feature #10341: Access issue form with a specific role
- Inside a project, a member can have more than one role (eg tester and developer), each of the roles have differents workflows.
As is done so that a member has a task with the developer role and another task with the tester role (only) -
16:37 Feature #10341: Access issue form with a specific role
- What is the interest of it?
As a "workflow" designer, to test the issue form?
-
16:48 Feature #9482: Wiki - minor change without notification
- This would be a very appreciated feature to add.
-
16:47 Feature #10398 (Closed): Add a new custom field type with tags replacements
- Closed as dupe of #5250.
-
16:32 Feature #10352: Preview should already display the freshly attached images
- Agree.
HTML 5 API allow standard loading of images with JavaScript but preview is generated by server so it might still require a file upload. -
16:30 Feature #10362: Show images in repositories inline when clicking the 'View' link
- I like the use of @Redmine::MimeType@.
Side note: maybe it could also be used in the places indicated by Toshi in #9638?
-
16:06 Defect #9798: Release 1.3.0 does not detect rubytree under ruby 1.9.3p0 / rails 2.3.14
- Hello,
I'm on windows with the following versions of the program :
ruby 1.8.7 (2012-02-08 patchlevel 358) [i386-mingw32]
gem 1.8.16
gem list :
actionmailer (2.3.14)
actionpack (2.3.14)
activerecord (2.3.14)
activeresource... -
15:47 Feature #10397 (Closed): Enhancement to use Redmine with existing PVCS Version Manager
- Please have a look into "Plugins repository":/plugins and forum:Plugins forum.
-
15:44 Feature #1757: Immediately send a notify email when a user is added to issue's watcher list
- Note: #10357 also proposes to send an email to the watcher when they are removed from the list.
-
15:43 Feature #10357 (Closed): Send a notification to watcher, when you add or remove his to list of watchers an existing issue.
- Closed as duplicate of #1757.
-
14:57 Feature #10372 (Closed): Impossible to export Story_Points field via API REST
- Please ask the plugin author or post in forum:Plugins, this tracker is for Redmine core bugs/feature requests only.
-
14:55 Defect #10385 (Closed): empty fields in the "issues" array
- The "Description" column is not included in the list of columns to be displayed.
-
14:47 Feature #3037 (Closed): Ability to filter updates in issue history
- Closed as duplicate of #1554.
-
14:06 Feature #3037: Ability to filter updates in issue history
- That would be very helpful.
-
13:17 Defect #10405 (New): TimeZone information lost when import from scm (utc timezone for server)
- Good day, community
*Reproduce*
I have:
* redmine 1.2.1 stable installed
* svn 1.6 installed on same server
* utc timezone for redmine set (config.active_record.default_timezone = :utc)
* one project with associated svn reposit... -
09:43 Defect #10404 (Closed): Inaccurate warning on leaving edited issue page without saving when move a bug
- Np.
-
09:41 Defect #10404: Inaccurate warning on leaving edited issue page without saving when move a bug
- fast test: yes you are right! with fresh install all work fine
=>Invalid, because isn't redmine related bug.
Sorry for the mistake -
09:20 Defect #10404: Inaccurate warning on leaving edited issue page without saving when move a bug
- yes, I have plugins installed but I don't think it's related to him: I attempt to try this behavior with fresh install version and post here the result (I hope in this day)
;-) -
09:12 Defect #10404: Inaccurate warning on leaving edited issue page without saving when move a bug
- Can't reproduce. Any plugins, etc.?
-
08:48 Defect #10404 (Closed): Inaccurate warning on leaving edited issue page without saving when move a bug
- When move a bug between project and add a comment in edit-move page, when click "Move" button, redmine show the warning related to leaving edited issue page without saving (bug #2910). User could be add message while move bug between pro...
-
09:15 Feature #8223: Email all users
- This plugin seems not to work in the sense that I want to notify all users of all projects.
I have to pick a project, to which the mail is going. Even if I multiselect all projects, only the top one's users receive the mail.
Is there a...
2012-03-07
-
21:28 Feature #7849: custom issue relation types
- +1
-
15:12 Feature #7849: custom issue relation types
- +1
Would also like to add custom issue relation types.
-
21:11 Feature #8681: Closed & Archived projects
- +1
For us, daily use of Redmine centers around operations with the current set of active projects. For these use cases, including closed projects adds a large amount of 'noise' to result sets.
Since we have dozens of large, closed... -
20:41 Defect #10374 (Closed): User list is empty when adding users to project / group if remaining users are added late
- Merged in 1.3-stable.
-
20:34 Defect #10390 (Closed): Mass assignment security vulnerability
- Please next time submit security issues to security at redmine dot org as requested on [[SubmittingBugs]].
-
19:52 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- I don't know. I don't like to version/wiki_page mechanism very much and I'd find awkward to put this logic in the API. I'd prefer to add the wiki page content as an attribute of the version in the API (eg. full_description or something)....
-
13:48 Feature #10384 (New): Versions REST API - Please add the WIKI field in the XML output
-
13:46 Feature #10384 (Resolved): Versions REST API - Please add the WIKI field in the XML output
-
09:35 Feature #10384: Versions REST API - Please add the WIKI field in the XML output
- Here is the patch to solve the issue.
-
19:42 Feature #10398: Add a new custom field type with tags replacements
- I don't get it.
-
17:49 Feature #10398 (Closed): Add a new custom field type with tags replacements
- The aim of this new field type is to provide a href string with automatic tags replacements.
Like :
%iid for issue id
%iname for issue name
%iproject for project id
This will help to provide external links with parameterized URLs ... -
19:35 Feature #8842: REST API: Filter issues created/updated before or after specific timestamp
- what about "issues created after", not just "updated on"?
actually, then best approach would be to retrieve "redmine server activity" with all (or some filtered) events within certain time period.
e.g. "show me what happened since Ja... -
15:45 Feature #8842: REST API: Filter issues created/updated before or after specific timestamp
- Hmm... That's not mentioned in the Rest API wiki page for Issues.
http://www.redmine.org/projects/redmine/wiki/Rest_Issues -
14:47 Feature #8842: REST API: Filter issues created/updated before or after specific timestamp
- You can already use
-
19:34 Feature #10402 (New): get server activity through REST API
- could you please introduce REST API to retrieve
"redmine server activity" with all (or some filtered) events within certain time period.
e.g. "show me what happened since Jan 1st" or "show me what happened with issues since Jan 1st".
... -
19:29 Feature #1828: Default target version for new issues
- +1
-
19:23 Feature #4796: Rails 3 support
- Here is a patch to enable wiki editing in Rails 3.2.1 https://github.com/marutosi/redmine/pull/6
-
14:29 Feature #4796: Rails 3 support
- *Update:*
Seems like it is because Redmine doesn't use rake tasks provided by acts_as_versioned: create_versioned_table and drop_versioned_table
So, I should add migration field for versioned_type myself -
02:43 Feature #4796: Rails 3 support
- Did anybody find out how to get wiki working? I've got an error:
can't write unknown attribute `versioned_type'
activerecord (3.2.1) lib/active_record/attribute_methods/write.rb:34:in `write_attribute'
activerecord (3.2.1) lib/activ... -
18:14 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
16:37 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
15:14 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Jeremy Bopp wrote:
> I think the reason they were done individually was in order to avoid races in the case that the repository is being concurrently processed in more than 1 thread or process. Imagine what might happen if two git pushe... -
14:59 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Jeremy Bopp wrote:
> Did you actually test the performance of the trunk of Redmine prior to your changes being committed? I would like to see how the two solutions compare for your repository.
I just did. The trunk version before my... -
13:12 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Gergely Fábián wrote:
> > While the patches I have attached to this issue introduce a simple migration, they work by removing most of the load of revision processing from the DB by making git do the work of eliminating revisions that ha... -
12:47 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Toshi MARUYAMA wrote:
> I dropped r8839, because it generates very log command line if repository has many branches.
It's possible to pass in all of the head revisions to be processed via stdin to git and avoid the long command line.... -
12:22 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
11:00 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- I dropped r8839, because it generates very log command line if repository has many branches.
-
10:39 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Jeremy Bopp wrote:
> Hello, Gergely,
> ...
Sure, however as Toshi Maruyama highlighted previously, he doesn't want to use a solution that contains migrations.
> I believe that the trunk (master branch in git) contains effectively the sa... -
04:57 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Hello, Gergely,
While the patches I have attached to this issue introduce a simple migration, they work by removing most of the load of revision processing from the DB by making git do the work of eliminating revisions that have alrea... -
04:11 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- -
-
18:02 Defect #6422: timetracking: subtasks time is not added to the main task
- + 1 really need to have the total estimates of a version summed correctly. We want to learn what the compliancy of the teams estimates vs. spent time, so we can measure team velocity of Scrum team.
-
17:47 Defect #10395 (Closed): Can't update issue comment
- Fine =)
-
17:35 Defect #10395: Can't update issue comment
- Oh, it's actually working in Chrome. Don't know what happened. Maybe it was a temporary issue.
Edit comment works. -
17:33 Defect #10395: Can't update issue comment
- Etienne Massip wrote:
> Do you have plugins installed that could interfere with normal behaviour?
I'm trying it on this redmine instance.
> ...
I'm using Chrome. I tried in Firefox and it does work. So maybe it's a bug in Chrome.
... -
17:29 Defect #10395: Can't update issue comment
- What is this browser, did you try with another one?
Do you have plugins installed that could interfere with normal behaviour? -
17:20 Defect #10395: Can't update issue comment
- Sure. Here it is
-
17:17 Defect #10395: Can't update issue comment
- Ok, I got it.
Could you please post a screenshot of this textarea? -
17:07 Defect #10395: Can't update issue comment
- Etienne Massip wrote:
> when clicking on "Save" button, what? Nothing happen?
No, like I said:
> ...
This edit should only appear if there is a conflict, right? -
17:03 Defect #10395: Can't update issue comment
- What you're saying is that you can see and click on the "Edit" link but when clicking on "Save" button, what? Nothing happen?
-
16:58 Defect #10395: Can't update issue comment
- Etienne Massip wrote:
> See my previous comment?!
Yes, it's very strange.
Maybe it's because you have "Contributor" rights and I don't?
-
16:55 Defect #10395: Can't update issue comment
- See my previous comment?!
-
16:53 Defect #10395: Can't update issue comment
- The third step is actually "Click submit"
-
16:52 Defect #10395: Can't update issue comment
- Nope, can't edit my comment
-
16:30 Defect #10395: Can't update issue comment
- Well, I don't understand neither can reproduce.
Comment is updated, isn't it?
Just edited mine ?! -
14:33 Defect #10395 (Closed): Can't update issue comment
- Steps to reproduce:
* Add an issue comment
* Edit issue comment
* Click update
Expected behaviour:
Issue comment updated
Actual behaviour:
Additional textarea is added with a label "Updated by User about ... ago"
-
17:05
Feature #421: Impersonate user feature
- +1!
That would be really helpful when adding and defining new roles like a product manager.
A work-around would be having a special test user with internal authentication and assigning him to different roles. But if you need to tes... -
16:15 Defect #10396 (Closed): CMI Plugin
- Please post in forum:Plugins.
-
15:58 Defect #10396 (Closed): CMI Plugin
- Installed CMI Plugin and had to translate fields, (Than you internet translation tool) However, I cannot change Euro to Dollar signs for cost evolution profile.
Also I am getting ane error under Metrics that reads "There is not'report... -
16:08 Feature #10397 (Closed): Enhancement to use Redmine with existing PVCS Version Manager
- Is there a way instead of having to use CVS or Subversion to tie Redmine into an existing CM repository like PVCS Version manager?
-
14:43 Defect #10358 (Closed): REST API: Multiple query fields
-
14:43 Defect #10358: REST API: Multiple query fields
- Sridhar P wrote:
> Updated the documentation, http://www.redmine.org/projects/redmine/wiki/Rest_Issues
Thanks for that.
> ...
No. Use the fully encoded form: http://www.redmine.org/issues.xml?created_on=%3E%3C2012-03-01%7C2012-03-... -
13:57 Defect #10358: REST API: Multiple query fields
- Updated the documentation, http://www.redmine.org/projects/redmine/wiki/Rest_Issues
When I try this url on my machine (with webrick), I am getting this error:
================================================================
Bad Requ... -
13:56 Defect #10358 (Resolved): REST API: Multiple query fields
- Thanks Etienne, this works as expected. Two more questions:
* Is this somewhere in the docs?
* Can we close #8842 too? -
13:45 Defect #10358: REST API: Multiple query fields
- Use @><@ operator for "between": http://www.redmine.org/issues.xml?created_on=><2012-03-01|2012-03-02.
-
13:18 Defect #10358: REST API: Multiple query fields
- Sridhar P wrote:
> I can replicate this on trunk at rev 9245.
Sorry, rev 9145 -
13:17 Defect #10358: REST API: Multiple query fields
- I can replicate this on trunk at rev 9245.
-
11:39 Feature #9929: Category names could be longer
- +1
-
10:40 Feature #10394 (Closed): Implement permission "Assign users to issues".
- In the "Submissions" Wiki page ( http://www.redmine.org/projects/redmine/wiki/Submissions ) there is a point:
* please DON'T assign the feature request to anybody, let the developers deal with it
I have this problem now, because cl... -
10:05 Defect #10381: Redmine 1.3.1 does not start (new installation on Fedora 14)
- You need fcgi gem.
-
09:19 Defect #10381: Redmine 1.3.1 does not start (new installation on Fedora 14)
- Etienne Massip wrote:
> Ok, and now I remember that Rails is no more supporting cgi, there is an issue roaming treating this topic: #4610.
> ...
I removed dispatch.cgi and copied @dispatch.fcgi.example@ to @dispatch.fcgi@.
Output of @di... -
08:30 Feature #1565: Custom query on My page
- +1 We badly need this functionality to provide customized blocks on "My Page" for various cases.
-
08:07
Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- +1
-
07:25 Defect #10387: Color priority on the roadmap
- OK, i'll search who to do this soon.
thanks. -
01:41 Defect #9815: Release 1.3.0 does not detect rubytree with rubgems 1.8
- Jean, that worked. Thank You!