Activity
From 2011-12-20 to 2011-12-22
2011-12-22
-
23:23 Feature #9851: Equalize the way how available shared versions are differentiated in target version drop-downs
- Fixing ugly typo.
-
23:22 Feature #9850: Differentiate shared versions in version-format custom field drop-downs by prepending its project name
- Fixing ugly typos.
-
23:16 Defect #9862 (Closed): Promotere virksomheten
- "Google Translate":http://translate.google.com/#no|en|Hensikten%20er%20%C3%A5%20gjennomg%C3%A5%20elementer%20i%20promoteringen%20av%20en%20ny%20bedrift%20s%C3%A5%20langt%20det%20lar%20seg%20planlegge.%20Kanskje%20vil%20det%20avdekke%20ny...
-
21:43 Defect #9862: Promotere virksomheten
- English, please.
-
21:24 Defect #9862 (Closed): Promotere virksomheten
- Hensikten er å gjennomgå elementer i promoteringen av en ny bedrift så langt det lar seg planlegge. Kanskje vil det avdekke nye behov som kan bidra til å gjøre arbeidet mer kvalitativt og effektivt. I hovedsak forutsettes dette gjennom...
-
21:13 Defect #9788: Revisions not linkified in email notifications anymore
- No plugins...
I needed to re-add a repository to a project today (I changed the svn folder) and, after re-add, for this project, commits are sent linkified again. For all other projects whose repositories I added before I did the upd... -
20:14 Defect #9861: user type custom field not a link in issue display
- Greetings,
Thanks for marking this a dup. I didn't find that issue in the large search results when I looked.
I thought that since the field is rendered as a link in some places and not others that it was a defect rather than by choi... -
19:11 Defect #9861 (Closed): user type custom field not a link in issue display
- This is not a defect, this is a Feature Request ant it has already been reported with #8152.
-
17:31 Defect #9861 (Closed): user type custom field not a link in issue display
- I created a custom field of type user. When I list issues that field is displayed as a link to the appropriate user. However, when I go to the specific issue that field is not a link like it would be if it was the assignee value.
-
18:38 Feature #9477: Show all, cross-project, issues under shared versions in gantt
- Forgot to attach the actual files...
-
18:37 Feature #9477: Show all, cross-project, issues under shared versions in gantt
- Btw: here follows some screenshots of the current behavior.
Scenario: one parent project with two child projects. One version created in the parent project, shared with subprojects. I create one issue in each child project and one issue... -
18:07 Feature #9477: Show all, cross-project, issues under shared versions in gantt
- Currently this is the designed behavior. Each issue in Redmine is scoped to a project, that is what the Gantt actually renders correctly.
I've adjusted this issues attributes to match the above info. -
17:19 Defect #8936 (Confirmed): rescheduling of an issue to an earlier date does not update issues that follow on this issue
- Confirmed on source:/trunk@7970.
-
17:13 Defect #9778 (Closed): No route matches controller knowledgebase
- Issue is not related to the Redmine core; closing as such. Thanks for all the input on this matter.
-
16:37 Defect #9860: Unable to use reposman.rb (XML received instead of JSON)
- Thanks you for your answer !
-
15:56 Defect #9860 (Closed): Unable to use reposman.rb (XML received instead of JSON)
- The @SysController@ is not part of the [[Rest_Projects|Projects REST API]] but only for use by Reposman; if you need to get projects manually in json format for a different use, go with the API.
By the way, the error you get must be d... -
14:04 Defect #9860 (Closed): Unable to use reposman.rb (XML received instead of JSON)
- Hello,
I am getting this error when trying to use reposman.rb :
'<?xml version="1.0" ' not in JSON!
If I try to get data manually from the following URL (used by the script) :
https://my.redmine.site/sys/projects.json?key=XXX
... -
16:18 Defect #9762: Closing issues with commit should be cross project
- It already works cross-project. See r3357 for issue #4674, which was included first in Redmine version#16.
-
16:14 Patch #4905: Redmine.pm: add support for Git's smart HTTP protocol
- Herve Leroux wrote:
> my mistake, you should have read the following :
> ...
Thanks for the information! I have updated the patch according to your instructions. It looks good, but I don't have a Redmine 1.3.0 installation around here ... -
16:10 Defect #4613 (Closed): Done ratio field isn´t displayed anymore
- 旭 張 wrote:
> I have the same issue ...
> ...
Please don't re-open almost 2 year old issues. For these things (upgrade issues) I'd suggest to post to the forums first instead.
Hint: does the issue has subtasks? -
16:03 Feature #9754: Advanced theming with better template engine
- Etienne Massip wrote:
> Redmine supports [[Themes]].
I think that is known to the issue author. I think he/she proposes some more advanced method providing more facilities to alter the core's views without overloading them.
Though, ... -
10:57 Feature #9858 (New): Predefined roles for the assignee
- Imagine that you assign the user to a task. It would be great if you can select his role in this tank. Especially when the task is assigned to multiple users (#408). You assign one user and pick his/her assignment role. You assign anothe...
-
10:44 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- I don't get it, why would this @changeset_parents@ table already be there at the time this migration is ran?
Do you use some plugin that could have created it?
-
09:58 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- Same error when updating from 1.2.1 to 1.3
-
10:34 Defect #9840: Can't log out of 1.3.0 without error
- BTW:
??
Rails version *2.3.11*
Active Record version 2.3.14
Active Resource version 2.3.14
Action Mailer version 2.3.14
Active Support version 2.3.14
??
? -
08:29 Feature #779: Multiple SCM per project
- --1
I'm more in favour of the solution proposed in #9703
I think that it is more flexible and would solve two problems and not only one:
* multiple repositories per project
* multiple projects per repository.
-
08:27 Feature #9703: Define repositories independently from projects
- I like the idea very much. It would make our life simpler and more flexible.
Mainly because our problem is not that we need multiple repositories for a project, but the other way around, i.e. we'd need multiple projects per repository.
... -
06:56 Feature #5487: Allow subtasks to cross projects
- +1
My use case:
I define each form in my application as a subproject.
Some features touch multiple forms, so an issue might be defined as build a new form for feature X and a subtask is add functionality to a different form to support... -
05:44 Defect #9824: Visual merge/branch history words are cut off
- That screenshot link is invalid. Screenshot is attached.
-
05:43 Defect #9824: Visual merge/branch history words are cut off
- Alex Pogodin wrote:
> Had the same effect until I refreshed my changesets. Try to remove and then readd the repo, worked for me
I did and the result was the same. Shouldn't it look like more of a revision graph and less of a bullet p... -
03:19 Feature #3384 (Closed): issue permissions
-
03:19 Feature #3384: issue permissions
- Mischa The Evil wrote:
> Cesar, isn't this superseded by #7414, which itself is implemented in Redmine version#27?
Closed as such (using "duplicates" relation) since no feedback came in. -
03:16 Defect #9749 (Closed): Entering data into the 'Parent Task' field in new or updated issues causes redmine to log out the current user.
2011-12-21
-
21:19 Defect #5586: Closing when marked as duplicate (also: closing model in general)
- I agree that Redmine's handling of duplicates is less than ideal (to put it mildly).
The behavior of duplicate issues is non-obvious. As I understand it, it works as follows.
# Someone enters issue A.
# Someone else enters issue B.
... -
20:22 Feature #1994: LaTEX support in Wiki, Forums and Issues
- Plugin installed and running perfectly.
Thanks for this very nice plugin, Michael Boratko. -
20:10 Feature #9703: Define repositories independently from projects
- I really like this idea, and actually considered writing up something similar myself.
I don't see it as inconsistent with #779. It would be great to have available repositories and associate them with projects as need be.. Multiple... -
19:52 Feature #9703: Define repositories independently from projects
- I'm not convinced. While it does sound 'clean' to refer to repositories separately, I think most projects will still use unique repositories themselves. Ie, the code for each project does not reside in the same place, either because they...
-
16:59 Feature #9703: Define repositories independently from projects
- This sounds like the best all-around solution, better than #779. It solves duplicate commit messages and the whole parent-child-sibling issue. For me the biggest issue is I have multiple git repos by creating dummy projects under the par...
-
20:08 Defect #3087: Revision referring to issues across all projects
- My apologies, I intended to update this months ago..
In app/models/changeset.rb you'll find: -
19:12 Feature #779: Multiple SCM per project
- #779 is needed by many people and it doesn't mean that some kind of repository sharing across projects won't be added later. I think this is the first step in this direction. Even if we don't have independent repositories, we could have ...
-
17:04 Feature #779: Multiple SCM per project
- While this ticket previously had my vote, I now prefer the solution proposed in #9703 since it allows for even more flexibility. When you have projects and sub-projects, one problem is that commits in a repo that reference a ticket in a ...
-
19:00 Feature #3647: Data Import/Export System
- +1
Just built a new server for production and would like to import a project from my old test server. Over 100 issues -
18:36 Defect #9857: Cannot create new tickets
- Ooops. You're right. Everything's fine now. :)
-
17:59 Defect #9857: Cannot create new tickets
- You must have missed the ??VERY IMPORTANT: do NOT overwrite config/settings.yml with the old one.?? part in the Update =).
-
17:57 Defect #9857 (Closed): Cannot create new tickets
- You have replaced your @config/settings.yml@ with your old one when you did the migration so it lost the new ??default_issue_start_date_to_creation_date?? setting.
You can add it manually (see "here":/projects/redmine/repository/revis... -
17:40 Defect #9857 (Closed): Cannot create new tickets
- Steps to reproduce:
# Click on an existing project in the main view
# Click on "new ticket"
Expectation:
The "new ticket" screen opens and a new ticket can be created.
Actual behaviour:
The browser window shows: -
17:40 Defect #6857: git references leaking from subproject to project
- Etienne Massip wrote:
> Yet to be confirmed.
I haven't looked into this issue deeply but considering r3357 for issue #4674, which was included first in Redmine version#16, it looks like it is logical behavior. -
17:34 Feature #2255 (Closed): Repository commits in subprojects won't reference tickets in parent projects
- Feature already implemented with r3357 for issue #4674, which was included first in Redmine version#16.
-
17:33 Patch #2256 (Closed): Allow commit messages to refer to issues in project ancestor tree, not just project
- Feature already implemented with r3357 for issue #4674, which was included first in Redmine version#16.
-
17:32 Patch #2256: Allow commit messages to refer to issues in project ancestor tree, not just project
- Colin Mollenhour wrote:
> Bruno, a commit in A1 cannot fix an issue in A2.
Colin, starting from Redmine version#16 commits are able/allowed to reference (and fix) issues of parent projects and subprojects. Just as Bruno already said.... -
17:08 Patch #2256: Allow commit messages to refer to issues in project ancestor tree, not just project
- Bruno, a commit in A1 cannot fix an issue in A2. In my case this is a problem, mainly due to restrictions caused by the strict 1-1 relation between repos and projects. #9703 would allow for fuller control over this though.
-
17:24 Patch #9359: invert project <-> repository relationship
- Also related to #9703.
-
16:40 Patch #4905: Redmine.pm: add support for Git's smart HTTP protocol
- my mistake, you should have read the following :
*for information :* line 441
my $access_mode = defined $read_only_methods{$r->method} ? "R" : "W";
*I would suggest to update this line to :*
my $access_mode = $request_is_read_only(... -
16:34 Patch #4905: Redmine.pm: add support for Git's smart HTTP protocol
- Hi,
The last version of the patch :
0001-merged-LeeF-s-patch-with-Michael-Fox-s-security-fix-redminetrunk.patch
doesn't work on the 1.3.0 version of Redmine :
@patch < ~/0001-merged-LeeF-s-patch-with-Michael-Fox-s-security-fi... -
15:12 Feature #572: My projects (or favourite projects)
- Not the same, but http://www.redmine.org/plugins/gsc_my_projects (https://github.com/generaldesoftware/RedMine-My-Projects-Plugin) is a plugin I've created to better projects lists.
Suggestions and comments are welcome -
13:45 Feature #9856 (Closed): Issues version base plugin
- Please ask your questions in forum, this tracker if for bugs or feature requests only.
-
12:36 Feature #9856 (Closed): Issues version base plugin
- Dear i need help for the plugin that i can import on redmine. i need a plugin that facilitate the issues versions. like i have created an issue it will assign it 0.1 version. and we are three people working on the same issue. another use...
-
13:19 Feature #7837: Filters should generate a bookmarkable/shareable URL
- @Etienne - no this has not been fixed by the issue/fix you mentioned. (In fact I would argue that the correct fix for that feature would be this.)
Issue #1965 is related to queries being kept in session - and the fixes for that, which... -
11:58 Defect #9821: Rake db fails updating from 1.2.1 to 1.3.0
- I have same issue upgrading DB 1.2.1 (bitnami stack) in test environment.
Nevertheless, as Hannes, I can start new version withoout problems.
So I ask the same question: can I go with that? -
09:23 Feature #9853: As a code inspector/reviewer, I would like to be able to review the checkins ignoring white-space changes
- Versions of libraries installed:
* "rake": version => "0.8.7"
* "i18n": version => "0.4.2"
* "rack": version => "1.1.1"
* "rails": version => "2.3.11"
Redmine at: SVN r6446 (http://redmine.rubyforge.org/svn/branches/1.2-stable)
S... -
09:18 Feature #9853: As a code inspector/reviewer, I would like to be able to review the checkins ignoring white-space changes
- Related issue: #1476
Forum post: [[/boards/2/topics/27797]] -
09:17 Feature #9853 (New): As a code inspector/reviewer, I would like to be able to review the checkins ignoring white-space changes
- This due to the fact that not all developers code according to the standard coding-style that keeps the white-space how it should be.
(NB note sure if this is really an SCM issue, if could also be called a UI issue)
-
08:01 Defect #8753: PDF export for Hebrew is reversed
- Orgad Shaneh wrote:
> Duplicate of...?
Got it. It was marked as duplicate by mistake, and now you deleted it. Ignore my comment... -
07:50 Defect #8753: PDF export for Hebrew is reversed
- Duplicate of...?
-
03:38 Feature #9851 (New): Equalize the way how available shared versions are differentiated in target version drop-downs
- I'd suggest to equalize the way how available shared versions are differentiated in target version drop-downs since they differ between issues/new and issues/index. See the following screenshots:
| issues/new | !tv_issues-new.jpg! |
... -
03:32 Feature #9850 (Closed): Differentiate shared versions in version-format custom field drop-downs by prepending its project name
- Like the subject already implies, I'd suggest to differentiate available shared versions in version-format custom field drop-downs by prepending its project name like it is already done for the target version attribute drop-downs. This w...
-
03:05 Defect #9849 (New): Custom field values of several issue custom field formats don't get set/updated properly during email issue creation/reply
- As of r4394 we can set/update custom field values using email issue creation/reply. Though currently custom field values of version/user/boolean issue custom field formats don't get set/updated properly during email issue creation/reply....
-
02:05 Defect #9815: Release 1.3.0 does not detect rubytree with rubgems 1.8
- mathew murphy wrote:
> Well, separately from this issue I also had to install the 'tree' gem, as well as 'coderay', both undocumented dependencies that caused runtime errors.
These are shipped with the Redmine core and does not have ... -
01:22 Feature #4796: Rails 3 support
- I rebased on r8304.
Git:
https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-git
* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-git/changeset/10734937ddd8
* Rails 3.2.0.rc1
**...
2011-12-20
-
23:51 Feature #1422: Date selection for Activity Page
- +1
-
23:26 Defect #8753: PDF export for Hebrew is reversed
- Redmine is useing RFPDF (TCPDF) library.
But RFPDF is not supporting RTL (Right-To-LeftRTF) now.
I think that RFPDF library needs to add RTL function, and if I am possible, I would like to challenge it. -
21:48 Defect #8753: PDF export for Hebrew is reversed
- I can confirm that this is still an issue in 1.3.0
-
23:18 Feature #9846: Provide the way for theme developers to set the row height in SCM history view
- Try #9832 patch.
-
15:15 Feature #9846: Provide the way for theme developers to set the row height in SCM history view
- As seen on the screenshot attached, graph nodes are not aligned with table rows
-
15:01 Feature #9846 (Closed): Provide the way for theme developers to set the row height in SCM history view
- It's not correct to rely on the row height 20px set in source:branches/1.3-stable/public/stylesheets/application.css#L165, cause, for example on my system (using Gnome/Linux) only checkbox takes 15px, plus cell padding etc. yields 26px t...
-
23:03 Defect #9845 (Closed): Changes to Wiki content are lost when using Back button
-
22:36 Defect #9845: Changes to Wiki content are lost when using Back button
- Thanks, I see we're running 1.0.1.stable so you can mark this bug as invalid. :)
-
09:00 Defect #9845: Changes to Wiki content are lost when using Back button
- In Administration > Informations screen.
The warning you're talking about has been implemented with #2910 for version:1.2.0.
-
02:06 Defect #9845: Changes to Wiki content are lost when using Back button
- I see that this is similar to issue #8468, which also fails on my install. How would I find out my current Redmine version?
-
01:56 Defect #9845 (Closed): Changes to Wiki content are lost when using Back button
- When editing a Wiki page, it is far too easy to accidentally click on the Back button in the browser and lose all changes to the page.
Normally this is solved by adding an onUnload handler to the page, that asks the user to confirm th... -
23:01 Feature #2477: mail reminder for watchers
- +1
-
19:23 Feature #9848 (Closed): Implementation of Marketing for Reynolds Defense Firm
-
17:50 Feature #9848 (Closed): Implementation of Marketing for Reynolds Defense Firm
- Social Media
Adwords
Analytics
Web Design
-
19:22 Feature #9847 (Closed): Database Implementation Reynolds Defense Firm
- Please use http://demo.redmine.org for testing purposes.
-
17:49 Feature #9847 (Closed): Database Implementation Reynolds Defense Firm
- Begin implementation of CLIO Database
-
15:41
Feature #1554: Private comments in tickets
- Alter Way wrote:
> I am a newby on ruby: How do you run 20110820092133_add_private_to_journals.rb migration script ?
> ...
Please don't randomly assign tickets to people. -
14:38 Defect #9842: {{toc}} is not replaced by table of content when exporting wiki page to pdf
- +1
-
14:24 Defect #9824: Visual merge/branch history words are cut off
- Had the same effect until I refreshed my changesets. Try to remove and then readd the repo, worked for me
-
10:28 Feature #2751: Support for plain HTML code in Wiki
- upto now you have 2 possibilities to use HTML in redmine's wiki:
Plugin 'Redmine Wiki HTML Util'
Allows you to embedd RAW HTML into your wiki, load stylesheets and javascript.
Made for html/css/js by Arlo Carreon (http://www.arloc... -
10:17 Defect #5723 (Closed): Error db:migrate with rails=2.3.8
- Rails issue fixed with 2.3.10 (https://github.com/rails/rails/commit/8b8730e1390963a8bb3a231ed1a324862d3dc4cf).
-
08:56 Defect #4243 (Closed): {{include}} macro mangles HTML entities in <pre> blocks
-
05:22 Defect #4243: {{include}} macro mangles HTML entities in <pre> blocks
- Etienne Massip wrote:
> Seems that it has been fixed, I can't reproduce?
Me neither... -
06:35 Defect #9811: SaveFileDialog popsup on various links
- A collegue uses Firefox and experiences the same issue on the same installation.
I guess i was not accurately capturing the correct response header in the word document.
I will try to reproduce and re-capture the response header.
Actu... -
04:43
Feature #5605: Subprojects should (optionally) inherit Members from their parent
- +1