Activity
From 2011-10-12 to 2011-10-14
2011-10-14
-
19:20 Feature #2870: Recursive download from the repository
- Bump! I'd really like it!
-
17:15 Feature #8900: Restful Web service: generate WADL
- +1
-
14:44 Defect #9425 (New): Attachment links fail when the file names contain the syntax pattern "_-_"'
- After uploading a file whose name contains ''_-_'' and creating a link to the file using the "@attachment:@" syntax, no html link is generated after saving.
-
12:41 Defect #9424 (Closed): rake/rdoctask is deprecated. Use rdoc/task instead (in RDoc 2.4.2+)
- Please do search for existing issues before posting, this one was obvious.
-
12:23 Defect #9424 (Closed): rake/rdoctask is deprecated. Use rdoc/task instead (in RDoc 2.4.2+)
- Getting this Warninfg when executing " rake db:migrate_plugins RAILS_ENV=production "
rake/rdoctask is deprecated. Use rdoc/task instead (in RDoc 2.4.2+)
WARNING: 'task :t, arg, :needs => [deps]' is deprecated. Please use 'task :t... -
11:53 Feature #2849: Drag and Drop Calendar Support
- +1
-
11:43 Feature #8559: Sum columns in reports
- There is a plugin providing this feature: https://github.com/planio/redmine_spent_time_column
-
09:58 Feature #8559: Sum columns in reports
- +1 this would make reporting much more powerfull.
-
10:32 Patch #1671: Show a breakdown of estimated/spent/remaining time for a version
- +1 for core integration
or at least a patch file for redmine 1.2.1
Is anyone working on this? -
10:24 Feature #2636: Feature Request: Wiki ACLs (Access control for individual pages)
- +1
-
10:16 Feature #7956: Show Roadmap tab when subprojects have defined versions
- We are using hierarchical project organization heavily, but some of our parent "project" just implement departments under which real projects with planned version are configured. In the departments parent projects we activated issue modu...
-
09:49 Defect #9234 (Closed): Versions of subprojects are / Roadmap) is - only visible if at least one version is defined
-
09:44 Defect #9234: Versions of subprojects are / Roadmap) is - only visible if at least one version is defined
- Confirmed.
This is dupe of #7956 -
01:48 Defect #9234: Versions of subprojects are / Roadmap) is - only visible if at least one version is defined
- Isn't this the same as #7956?
-
09:27 Feature #9330: Watchers can not see the ticket status, if their role is set to only own or assigned tickets.
- Holger Baumhaus wrote:
> Thank you.
> ...
-
09:26 Feature #9330: Watchers can not see the ticket status, if their role is set to only own or assigned tickets.
- Thank you.
Issue #8448 sounds promising and would also solve some problems beyond adding watchers. -
09:10 Defect #5419: Issues with shared versions from different projects do not show up in Roadmap summary
- I almost thought this issue had got lost :) I will set up and try a clean, recent checkout beginning of next week, and then let you know whether the issue still occurs.
-
02:00 Defect #5419: Issues with shared versions from different projects do not show up in Roadmap summary
- I just came around this issue, and wasn't able to reproduce this (any more) on a clean checkout of source:/trunk@7623.
Issue-author: could you please give feedback on this? -
06:32 Feature #9422 (New): Show the real progress of subproject in roadmap view
- My project hierarchy is one TopProject with two sub-projects: SubProject1 and SubProject2.
A version named "2011-release" is created in TopProject and shared to all sub-projects.
Then SubProject1 contains one task of which % DONE i... -
04:03 Feature #9421: Prevent attribute changes once an issue is assigned to a closed version
- I noticed that, as you said, Redmine already prevents the reopening of closed tickets associated to already closed versions. However, it is still possible to change the ticket's version and this would mess the history of the project in t...
-
02:34 Feature #9421: Prevent attribute changes once an issue is assigned to a closed version
- Luiz Carlos Junior wrote:
> I would like to suggest a role that prevents unauthorized users reopen or change the attributes of tickets associated to closed versions. Comments, in principle, would be normally allowed.
As far as reopen...
2011-10-13
-
21:04 Feature #3816: Allow pasting screenshots from clipboard
- I've soled my problem and it seems it was only problem with OpenJDK. The change had to be made in the Uploader class in the uploader_applet.jar file. If it is okay with axmor (I'll write them an email) I release the change on "my github ...
-
18:11 Feature #5386: Branch/Tags in Changeset Description
- I understand that git branches are not "stable" but I don't understand why that would preclude this feature. If a new branch is added, all of the commits will be updated with the new list of branches. If a branch is deleted, the branch w...
-
10:03 Feature #5386: Branch/Tags in Changeset Description
- As I described at https://www.chiliproject.org/issues/268#note-2 ,
Git branch is not stable. Git branch is the pointer to the specific revision. So, Git branch cannot be stored in database.
Mercurial *named branch* is stable.
Please... -
06:41 Feature #5386: Branch/Tags in Changeset Description
- I implemented the recording of branches per revision using "git branch --contains" and listing the branches next to each associated revision as links to the branch browser. Patch and screenshot attached.
!2011-10-13_0039.png! -
00:40 Feature #5386: Branch/Tags in Changeset Description
- Yes, there is no easy way to find which branch someone committed their code to using Redmine. I propose the names of the branches containing a commit also go in the Associated Revisions section:
!2011-10-12_1834.png!
There are othe... -
17:32 Defect #8707: Reposman: wrong constant name
- Someone here investigated a bit @reposman.rb@. I don't know if it can help but here's what he found.
@reposman.rb@ defines a @Project@ class which inherits from @ActiveResource::Base@ (line 183). On line 196, the call @Project.find(:a... -
11:59 Defect #8707: Reposman: wrong constant name
- Could someone with a working instance of 1.2.1 post the output of "gem list" and "RAILS_ENV=production script/about", please? Maybe we can isolate the working vs. non-working versions.
We just upgraded to 1.2.1 and the problem is stil... -
17:20 Feature #9421 (Closed): Prevent attribute changes once an issue is assigned to a closed version
- Sometimes it is desirable to reopen a closed ticket in order to adjust/correct its implementation.
However, if this ticket has already been "published" as part of an official closed version it would be awkward to change its characteri... -
15:41 Feature #2024: gantt chart editing
- +1 too
This feature working for new version would be very nice! -
14:03 Feature #9420 (Closed): Migration d'une BDD redmine 1.1 vers redmine 1.2
- D'abord, ce n'est pas un forum mais l'ITS de Redmine, vous devriez en effet poster cette question dans l'onglet "Forum".
Et puis, veuillez svp poster en anglais, cf. [[SubmittingBugs]], merci. -
13:58 Feature #9420 (Closed): Migration d'une BDD redmine 1.1 vers redmine 1.2
- Bonjour à tous,
En premier lieu je suis très ravi d'être dans ce forum.
Après des recherches sur un sujet, ressemblant à ma demande, je n'ai pas pu vraiment trouver une piste.
Je vous expose mon souci:
J'ai installé la dernière... -
14:00 Feature #9413: Soft start and due dates of an issue
- Did you know that dates were actually modified depending upon issue relations (see [[RedmineIssues#Related-issues]])?
-
10:00 Feature #9413 (New): Soft start and due dates of an issue
- Now, start and due dates of an issue are hard. It doesn't allow to reschedule its project based on dependencies and durations.
I suggest to take the dates as soft ones (to allow their reschedule) unless checkboxs at field Start date a... -
13:58 Feature #9414: To add field Duration to an issue
- Actually, estimated duration of an issue treatment is filled in hours in Estimated time field.
Kind of duplicates #2687 and #1953?
-
10:05 Feature #9414: To add field Duration to an issue
- Sorry if I submitted a duplicated issue. It is very hard to search in those 2.000+ feature requests.
-
10:04 Feature #9414 (New): To add field Duration to an issue
- In days.
To allow reschedule of issues based on the duration and dependencies. -
13:42 Feature #9417: Start and due dates of a project
- Looks very similar to #5451?
-
10:38 Feature #9417 (New): Start and due dates of a project
- Now, issues have start and due dates. A project has start and due dates derived from its earliest and latest issues.
I suggest to add extra start and due date fields to parent project. It should be shown in project overview and eg. in... -
12:36 Feature #9292: "Data has been updated by another user." - Allow this to be clicked through
- I think this issue is very serious problem, too.
-
12:11 Feature #9418 (Closed): More assigned people to an issue
- This has been resolved with #2964 for version:1.3.0 with the ability to assign an issue to a group.
If you want to be able to assign issues to more than one person instead of a group, please reopen #408. -
10:39 Feature #9418 (Closed): More assigned people to an issue
- Now, only 1 person can be assigned to an issue.
I suggest to allow to choose more than 1 person there.
Sorry if I submitted a duplicated issue. It is very hard to search in those 2.000+ feature requests. -
12:07 Feature #8138 (New): Assign Priority based on Category
-
12:07 Feature #8153 (New): List assigned issues in user profile page
-
11:59 Feature #4178 (Closed): Optimize Redmine for any project, not just software dev (Change "Version" > "Milestone")
- Closed as duplicate of #724.
-
11:58 Feature #9416 (Closed): Support for a milestone
- Closed as duplicate of #374.
-
10:32 Feature #9416 (Closed): Support for a milestone
- Now, we can get the milestone functionality either by
a) versions
or
b) issues
Versions are more related to programming. Their meaning is: Which issues should be included in a version?
Issues are closer to what I desire: I can c... -
11:54 Feature #9419 (Closed): Group/sort the issue list by user/version-format custom fields
- I'm using 1.2.1 and I wonder why I cannot get issue search results grouped by user/version-format custom fields.
Is there any restriction to have such grouping features? Or I'm simply missing some configuration needed?
Any suggest... -
11:02 Defect #9331: Status list is sometimes missing values
- Mischa The Evil wrote:
> You're right. The "related to" relationship should not trigger *any* restrictions AFAIK.
OK - good to know that we're on the same line ...
> ...
I've just tried it and I were not able to reproduce it ...... -
10:20 Feature #9415 (New): More fine dependencies between issues
- Now, only dependecies "precedes" and "follows" exists to order 2 issues time schedule.
I suggest to add more dependencies according project management:
- FS: end A - start B
- SS: start A - start B
- FF: end A - end B
- SF: start ... -
10:09 Feature #1189: Multiselect custom fields
- Leif Lange wrote:
> I have applied your patch to the exact same setup. However, when I try to edit or create a new custom field, I get the error:
> ...
have you migrated the DB? it seems that you are lacking that. -
08:56 Feature #1189: Multiselect custom fields
- Reattached the PDF as the previous contained errors
-
08:53 Feature #1189: Multiselect custom fields
- I have applied your patch to the exact same setup. However, when I try to edit or create a new custom field, I get the error:
-
09:38 Defect #8371: MySQL error when filtering a custom field using the REST api
- BTW I'm not sure it's worth it to maintain such complexity in request arguments processing as there is another way to do so (via f[], o[], and v[] arguments), maybe should we stick to handling equality.
I'm Ok with reverting these cha... -
09:27 Feature #1567: Make author column sortable and groupable
- I hope that author-column not only sortable but also groupable.
Such as:
@QueryColumn.new(:author, :sortable => "#{Issue.table_name}.author_id", :groupable => true),@ -
08:16 Feature #5490: Option for independent subtask priority/start date/due date/done ratio
- +1 to this (the whole discussion), I find this feature so counterproductive that I end up not using subtasks, and instead organize them by category, version or even subprojects.
2011-10-12
-
20:32
Feature #9412: Drag and Drop Issues to Set Parent-Child Relationships
- related to: #8016, #9183
-
20:31
Feature #9412 (New): Drag and Drop Issues to Set Parent-Child Relationships
- This is similar to some of the other drag-and-drop feature requests on here, but I wanted to put in my vote for this use of drag-and-drop functionality.
What would be really nice is, when you're looking at a list of issues, dragging o... -
17:23 Feature #9410 (Closed): To add features of a project planning tool
- Some of these features already exist in this tracker; if you need something specific, please first check that this hasn't already been requested and eventually create a ticket for each need with a precise description.
Thanks. -
16:46 Feature #9410 (Closed): To add features of a project planning tool
- I miss those features:
1. "softer" start and due dates of an issue (plus checkbox at them to make them "hard")
2. duration of an issue
3. more fine dependencies between issues
4. milestones (special issue type with no duration)
5. e... -
17:05 Defect #9411 (Closed): Number of issues closed / open in Roadmap include private even on restricted accounts
- The roadmap of one of our software indicates 20 closed / 0 open (cool everything is ready for delivery !). Among the 20 closed :
* 10 are private,
* 10 are public,
If I connect with a public user (the client) :
* the detailed list ... -
16:38 Feature #5168: Preview option when editing issues and notes
- This was raised again as #5520 and subsequently fixed.
-
16:31 Defect #9389: repository commits time messages are not applied
- Excellent - thanks - I have updated the wiki.
I have made the mappings on my project.
I'll be experimentating today and will update this ticket accordingly. -
14:33 Defect #4725: Error displaying Project's Settings when repository configured
- Terence suggested it might be a plugin interference, could you please try without any?
-
13:17 Defect #4725: Error displaying Project's Settings when repository configured
- I'm having the same issue on Remine version 1.2 ("stable" branch from subversion). Applying the patch from comment #10 fixes it.
-
14:30 Defect #9406: Email was sent to myemail@office.com but i am not receiveing them
- Check your @log/production.log@ file and please give any details required as specified in [[SubmittingBugs]].
-
06:49 Defect #9406 (Closed): Email was sent to myemail@office.com but i am not receiveing them
- If i changed my mail id to mymaild@gmail.com i ma receiving emails for gmail and hotmail.
my email.yml file
development:
delivery_method: :sendmail
sendmail_settings:
location: /usr/sbin/sendmail
arguments: -i -t
... -
13:49 Defect #9409 (Closed): Filtering issues on estimated time with decimals
- I am using the current stable release (1.2.1). When trying to filter a list of issues based on the estimated time the results seem to ignore the decimal point. For example if you try to filter issues that are estimated to take less than ...
-
11:08 Feature #3511: Ability to sort issues by grouped column
- +1
This is an important feature, so you can view the full Issue list like a roadmap. Please give it high priority so it can be included soon. -
09:25 Feature #8171: Adding attachments through the REST API
- Can u provide an patch for redmine 1.2.1 and a curl example how you test the attachment upload?
Tx for help!
+1 for this feature -
01:49 Defect #9405: Any user with :log_time permission can edit time entries via context menu
- Ahh, I see... Thanks for your clarification on this Toshi. I was testing with an account that did not had the @:log_time@ permission at all :-/