Activity
From 2013-03-26 to 2013-03-28
2013-03-28
-
23:00 Patch #13629 (Closed): Add 'method' option for submitPreview() js
- Might be related to #12642.
-
19:32 Patch #13629 (Resolved): Add 'method' option for submitPreview() js
- Etienne Massip wrote:
> What for?
Actually, nevermind. I've had to use a GET method in one of the plugins because POST route didn't work (I don't recall all the details right now,) but now that I check again, it seems to works with ... -
16:51 Patch #13629: Add 'method' option for submitPreview() js
- What for?
-
15:05 Patch #13629 (Closed): Add 'method' option for submitPreview() js
- The submitPreview() JavaScript function uses 'POST' HTTP method by default. Make this configurable via options to preview_link helper.
-
22:25 Defect #13632: Empty page attached when exporting PDF
- Sorry, forgot:
-
22:24 Defect #13632 (Closed): Empty page attached when exporting PDF
- When exporting a PDF file, regardless whether from a ticket, ticket listing or wiki page, an empty page is added as last page of the export.
-
22:03 Defect #5126: Associated revision shown multiple times
- The same thing happens with redmine 2+ where you can associate multiple repositories with a project.
Scenario is similar:
* Project A
** Repository1 URL/ProjectA
** Repository2 URL/ProjectB
* Project B is subproject of ProjectA
... -
20:19 Defect #13631: Git 1.8.1.5: Permission denied
- I guess this could be in relation to #13592.
-
20:14 Defect #13631 (Closed): Git 1.8.1.5: Permission denied
- After upgrading Git from 1.7.12.4 to 1.8.1.5, I got the following error message:
_log/production.scm.stderr.log_ -
19:33 Defect #13630 (Closed): PDF export generates the issue id twice
- The pdf export generates the issue id twice:
!double_issueID.png!
I added a patch that fixes this bug. -
15:56 Feature #1675: Add 'affected version' as a standard field
- After reading this and other issues i was happy to find the new type "Version" for custom fields,
but there is one big problem if you want to use this type for "found in version".
In my case the custom field of type version only show... -
15:16 Feature #1712: add custom fields that are calculations of other fields
- +1
-
14:55 Defect #13617: Internal error on custum queries after Upgrade 2.2 -> 2.3
- Not confirmed yet but I remember a commit going this way in Query refactoring so it's worth digging into this for next minor release.
-
00:21 Defect #13617: Internal error on custum queries after Upgrade 2.2 -> 2.3
- The only problem for all custom issue queries was, that it had to be
-
00:05 Defect #13617 (Closed): Internal error on custum queries after Upgrade 2.2 -> 2.3
- After upgrading redmine from 2.2 to 2.3 I get a internal error on custom queries. I created the same query on 2.3 and compared the database column "filter" from table "queries":
-
14:17
Patch #9317: Admin users should be always authorized when no context is given
- To further elaborate on what Alex already explained: Even if one wants to use :global=>true, this fails as soon as one wants to use link_to_if_authorize() -- there seems to be no way to tell that to pass :global=>true. So one ends up wit...
-
13:34
Patch #9317: Admin users should be always authorized when no context is given
- On a somewhat tangential note, there is also a function allowed_to_globally define in app/models/user.rb -- however, nothing uses it, indeed its name occurs only once in the complete redmine sources. It was added in SVN revision 4164 by ...
-
01:03
Patch #9317: Admin users should be always authorized when no context is given
- Hmm, indeed, it seems odd to allow the manager of a project to create new top-level projects... Might be OK to leave this setting in, but it should be disabled by default for all roles, shouldn't it?
Also, I wonder about the patch tha... -
13:50 Feature #13627 (New): Allow displaying custom field value in Gantt issue quick information tooltip
- How to add a custom field for note and when I go gantt -->move mouse to the due date ,it can show the comment I add
-
12:09 Defect #13626: Spent time report. Details: Week
- I've forgotten to write, that this bug appears in both systems (old 1.4.4 and new 2.3.0)
-
10:58 Defect #13626 (Closed): Spent time report. Details: Week
- Hello, team!
h2. The 1st system, where this bug appear.
We use:
* Redmine 1.4.4.stable.10658 (version 2.3.0)
* Ruby 1.8.7
* Rails 2.3.14
* RubyGems 1.8.24
* MySQL 5.1.63
h2. The 1st system, where this bug appear.
But we ... -
08:27 Defect #13622 (Closed): "Clear" button in Spent Time Report tab also clears global filters
- *Steps to reproduce:*
1. Go to Projects -> Overall spent time -> Report.
2. Add some filters or just choose "Date is today".
3. Click Clear in Details area.
*Expected result:*
Only report itself is cleared.
*Actual result:*
Fi... -
04:30 Feature #5506: Make it easier to select multiple issues via checkboxes
- Shift-click selects issues between a range when clicking outside the checkbox, but not when clicking on the checkbox(es) for either click. So, range selection is now possible (i.e. this issue could be resolved) but it has some usability ...
-
02:35 Feature #13619 (New): Automatically pass issues to the next defined team member after issue status updated
- just like this:
when i change issue status from new to resolved or other customized status i will never need to assign this issue to the member who working on it manually,redmine can do it automatically according to the customization i... -
01:11 Defect #13618 (Closed): CSV export of spent time ignores filters and columns selection
- When you do a CSV export of spent time, it opens a dialog that lets you choose which columns you want to include in that export.
The problem is that the dialog is a form, and the form's action holds all the filter parameters. By desi...
2013-03-27
-
21:39 Feature #12814 (Reopened): Ability to specify target version sort order
- I know it has changed. I do not think it is a duplicate.
I am asking for a way to have the same order as 1.0.3.
Specifically issues that have no target version to be at the bottom of the list. -
05:38 Feature #12814 (Closed): Ability to specify target version sort order
- Duplicate with #6974.
-
05:37 Feature #12814: Ability to specify target version sort order
- Ivan Kanis wrote:
> The target version is now showing the oldest version on top which is not very convenient.
It changed by #11153. -
21:02 Feature #13615 (New): Back (or HEAD) link in Wiki history page.
- When displayed Wiki page, one can press History link to view wiki revisions. In this revisions page, there is no link back to the wiki page. Yes, there are links to all of the revisions but they go to URLs that include revision number. I...
-
20:09 Patch #1587: Simple Phone Number and Address List for Users
- Updating Old Issues:
Already Implemented as Custom fields. An administrator can add any number of fields to the user screen. -
20:05 Patch #1475: Sort by subproject then by subject in issue tracker
- Updating old issues:
Already implemented. Under the options section, the issues can be grouped by "Project". Then afterward the user can sort by subject.
You can also create a custom query that sets all this up and can also add seco... -
19:53
Feature #13600: Allows specifying "canned responses"
- Unfortunately, trying your plugin with my Redmine test installation results in an error 500. I'll file a bug report on github.
(In addition, the installation instructions in your README are still for Redmine 1.x. I submitted a pull requ... -
19:37
Feature #13600: Allows specifying "canned responses"
- Thanks, your plugin indeed looks useful! At first I was a bit worried, because that page said it was only tested with Redmine 2.0.x, but looking at the git repos, there are some commits for compatibility with 2.2.x. Could you perhaps get...
-
18:06 Feature #13600: Allows specifying "canned responses"
- Check this plugin out: http://www.redmine.org/plugins/canned_responses
-
19:43 Feature #1016: Global Gant chart for all projects
- Updating old issues:
This feature exists in the current version (possibly for years) of redmine. When viewing all issues, there's the gantt button on the sidebar. Any project then can be clicked on and edited to adjust it's settings. -
19:23 Feature #13613: Fix Gantt - Sponsored Fix
- In a project, you have issues.
When you assign a issue you can set the *Estimated Time*, Start Date, End Date.
In the Gantt chart, it would use the *Estimated Time* to create the chart. This way when you assign an Issue for the sam... -
17:14 Feature #13613: Fix Gantt - Sponsored Fix
- Charles Gomes wrote:
> The idea is to specify hours for the issues and the gantt will lay the project as defined on "precedes / folows".
Guess it already does, could you give more details please? -
15:34 Feature #13613 (Closed): Fix Gantt - Sponsored Fix
- Hello guys,
My company is looking to sponsor the fix of the Gantt charts. The boss is looking to get the chart to work without having to specify begin and end dates. The idea is to specify hours for the issues and the gantt will lay t... -
17:56 Patch #13612: Members roles : display group of role
- Example :
!group_roles.png! -
14:31 Patch #13612: Members roles : display group of role
- This patch was done on an old Redmine V1.2.1.
-
14:28 Patch #13612 (New): Members roles : display group of role
-
16:45 Feature #7907: Display Issues in a hierarchy (tree)
- +1 vote for it
-
16:44 Defect #10048: Secondary sorting after sorting by parent task
- +1 vote for it
-
15:33 Feature #11647: Create Issue Structure Templates
- Hey,
we would be very happy about such a feature, too.
For exactly the same use-cases, as Christophe already described. Is there already a solution existing?
The current issue copy mechanism unfortunately breaks the relations within t... -
15:21 Defect #12477: Internal server error after migrate from Trac 0.12.3 ro Redmine 2
- Hey everyone,
I found out what the problem is: dates in trac 0.12.3 are stored as microseconds from epoch. Function Time.at signature is Time.at(seconds[, microseconds]).
As attachment, you can find a svn diff that correct this bug... -
14:59 Defect #11839: Text overlay when exporting issues to pdf files
- Exactly the same behaviour seen with Redmine 2.3.0stable (Ruby 1.9.3 (i386-mingw32), Rails 3.2.13). I'm long time user of Redmine, but ths PDF issue with long custom fields makes pdf export totally useless :-( Please help!
-
14:24 Defect #13549: migrate database from Redmine 1.4.3.stable (MySQL) to Redmine 2.3.0.stable (MySQL).
- Adapter mysql, couse Ruby 1.8.
New projects works good.
Problem only with migration from one server.
I tried migration from another server. All ok.
I think that MySQL table has bug.
Ideas?
-
14:23 Defect #11089 (Confirmed): UTF-8 encoding not showing correctly when looking highlighted php file contents
- Upgrade dep to 1.0.9 or 1.1.
-
10:45 Defect #11089: UTF-8 encoding not showing correctly when looking highlighted php file contents
- coderay php encoding issue has been solved:
https://github.com/rubychan/coderay/issues/40
checked, works fine with updated coderay/scanners/php.rb file -
13:55 Feature #13378: Custom fields Type Auto Number Increasing
- Hi,
It will get the largest number in project and plus one.
I think it just a default value and it can be change
or
if some one move a issue to another project, it will default get a newest number.
Sorry for my English -
12:54 Feature #7057: Send email notification on subtask and parent updates
- +1 + #11177 (Alert when a sub-task has the status changed )
-
12:49 Patch #3358: Advanced LDAP authentication
- I think that "redmine_ldap_sync":http://www.redmine.org/plugins/redmine_ldap_sync should serve as a model how this should get implemented. Actually, why not merging code of the plugin (after review) to the Redmine, as it works like a cha...
-
10:20 Feature #7037: CSV export encoding and excel. UTF-8 and BOM
- hi,
i have the exactly same issue, with the plugin https://github.com/sprosin/redmine_csv_with_bom now the csv export works as expected.
but i think this patch should be merge into the redmine core, not in form of a plugin with mo... -
10:05 Feature #9909: Search in project and its subprojects by default
- A quick and dirty way to change this Redmine behaviour is to edit apps/controller/search_controller.rb and edit in @class SearchController < ApplicationController@ the various statements (for example, if you want to change the default se...
-
09:37 Feature #13560: Force status transition on issue update
- Here is use case. We are planning to create new statuses "Feedback to customer" and "Feedback from customer". We want to have simple mechanism of forcing change of issue status from "Feedback to customer" to "Feedback from customer" if c...
-
08:58 Defect #2493 (Confirmed): Subversion: Error message for some of view differences
-
08:12 Feature #13595 (Closed): Add text to Redmine links
- Duplicate with #10248.
-
08:10 Defect #11360 (Needs feedback): Text formating issue
-
07:35 Defect #13231: Can't Delete Watcher On Current Trunk 2.3.x
- Dipan Mehta wrote:
> Which target version will this be available?
AFAIK, stable releases were not affected. The fix is commited in trunk already. -
07:29 Defect #13605 (Closed): Please delete spam wiki
- Deleted.
-
03:13 Defect #13605 (Closed): Please delete spam wiki
- [[Watch_Mexico_vs_USA_Live_Streaming_Free_Online]]
-
06:26 Defect #12648 (Closed): Multiple levels of nested subtasks not displayed correctly in issue list
- Duplicate with #7907.
-
06:16 Defect #7417 (Closed): parent issue display problem
- Duplicate with #7907.
#7907 has many watchers. -
06:05 Defect #13608 (Closed): Parent column in CSV export should include issue id only
- If you export issues list to CSV with all columns, then you get parent task column with: parent task tracker, ID and subject in a single cell.
Could it be only parent task ID? By the ID I can get all necessary info about the parent t... -
05:43 Feature #8080 (Closed): Option for alphabetical only sorting of versions (date ignored)
- Duplicate with #6974.
-
05:41 Feature #7269 (Closed): Sort versions by version numbers x.y.z{z} instead of alphabetically
- Duplicate with #6881.
-
05:06 Feature #1936: Moving tasks between versions on the roadmap screen
- Dipan Mehta wrote:
> Yes indeed - #1936 looks like a duplicate of #488
I close #488 because #1936 has more notes. -
05:05 Feature #488 (Closed): Change issue "fixed version" on roadmap screen
- Duplicate with #1936.
-
05:03 Defect #13566 (Closed): SystemStackError (stack level too deep) - Ruby 1.8.7
- Thank you for your feedback.
-
05:02 Defect #13566: SystemStackError (stack level too deep) - Ruby 1.8.7
- Please disregard. I removed plugins and project insert succeeded. Thanks for looking into it.
-
05:03 Feature #3529: Deleting a tracker does not allow you to reassign issues to a different tracker
- Let me ask the other way, if yo have a large number of issues under a tracker X which all needs to move to say tracker Y. (tracker Y is not empty) What other way _can_ be made without violating field permissions set in the workflow?
I... -
04:06 Defect #8936 (Needs feedback): rescheduling of an issue to an earlier date does not update issues that follow on this issue
- Can't test it at the moment but I think this is implemented already via #4590 in Redmine version#56.
-
03:54 Defect #13606 (New): PDF and PNG export of Gantt loses issue numbers
- The PDF and PNG export of Gantt chart loses issue numbers, which makes it difficult to find and update issues when someone comments on a pdf or png copy of the gantt chart (Redmine 2.2.X, 2.3.0).
Also in the latest release (2.3.0), th... -
03:21 Feature #7627: journal for changing custom version status
- Dipan Mehta wrote:
> This functionality is now possible out-of-the-box using custom field of type "version".
As note-1, there are no journal entries showing the changes.
-
02:55 Feature #5733 (Closed): Subtasks: inheritance of time needs to be clear, either way we choose
- Duplicate with #5875.
-
02:52 Feature #9972 (Closed): Subtasks assigned to same version by default
- Duplicate with #6117.
-
02:51 Feature #9991: Estate parent task vs subtask
- And duplicate with #7450.
-
02:43 Feature #9991 (Closed): Estate parent task vs subtask
- Duplicate with #5734.
-
02:49 Feature #5734 (Closed): Subtasks: inheritance of status needs to be clear, either way we choose
- Duplicate with #7450.
-
02:47 Feature #11177 (Closed): Email notification for subtasks status changes to watchers of the parent task
- Duplicate with #7057.
-
00:20 Defect #13592: ActiveRecord::RecordNotUnique for git repository
- Are these really the same hash values?
It is very rare case on Mercurial *valid* repository.
http://mercurial.selenic.com/wiki/FAQ/TechnicalDetails
Redmine checks hash before inserting database.
source:tags/2.3.0/app/models/repos... -
00:01 Defect #3285 (Closed): Renamed SVN Project/Folder :: problem when try to view difference.
- Duplicate with #2493.
2013-03-26
-
23:59 Defect #9679 (Closed): Subversion: 404 on diff of renamed files
- Duplicate with #2493.
-
23:56 Defect #7324 (Closed): Subversion diff gives an error.
-
23:56 Defect #7324: Subversion diff gives an error.
- Duplicate with #2493.
-
23:54 Defect #13601 (Closed): Repository history problems following svn mv
- Duplicate with #2493.
-
19:27 Defect #13601 (Closed): Repository history problems following svn mv
- When viewing history of an svn repository in the Repository/ tab, "svn mv"'d files don't behave well.
The view shows all the previous revisions of the file, including under its old name, as expected. But diffs between some versions do... -
22:31 Defect #13586 (Resolved): Circular loop testing prevents precedes/follows relation between subtasks
- Fixed in r11692, thanks for pointing this out.
-
22:24 Feature #5996 (Closed): Affected version feature
- Indeed, a custom field should be used.
-
22:11 Defect #13522: Private field is shown as required
- Daniel Felix wrote:
> But requiring a checkbox is a wrong behaviour in my opinion. :-)
Well it actually implies no specific behavior, it's just inaccurate information.
Not sure it's worth changing it.
-
21:58 Defect #13522: Private field is shown as required
- Yes this is right. This will be wrong too.
What do you think? would it be a better solution to prepare that no checkbox could be set to required?
Or change the way a required is applied on checkboxes?
For example:
Require on che... -
21:26 Defect #13522: Private field is shown as required
- With this patch applied, the private flag can then be configured as required in the workflow permission configuration screen. Not sure that it's a better option.
-
22:05 Defect #13566: SystemStackError (stack level too deep) - Ruby 1.8.7
- We have projects like this:
-
21:27 Defect #13566 (Needs feedback): SystemStackError (stack level too deep) - Ruby 1.8.7
- Tests pass with ruby1.8.7. Can you give the exact steps to reproduce?
-
21:31 Feature #13560: Force status transition on issue update
- Updating an issue without changing its status is allowed by design. That would mean that the user is not even allowed to add a note without changing the status. What is the use case behind this?
-
18:31 Defect #13592: ActiveRecord::RecordNotUnique for git repository
- Scratch that, it actually looks like it's trying to overwrite the same revisions, so somewhere the check to see if a revision has already been inserted is failing.
-
17:12 Defect #13592: ActiveRecord::RecordNotUnique for git repository
- SHA-1 is collision-resistant, but mathematically speaking there's no way it can be collision proof. In especially large datasets it's entirely possible for two checksums to be the same-look up the birthday problem.
-
11:29 Defect #13592: ActiveRecord::RecordNotUnique for git repository
- You're not supposed to have a duplicate SHA-1, do you know why you have this?
-
17:35 Defect #13001: Sending Mail on emails hosted on google email app problem.
- You can try a few things to debug:
For the gmail (or google apps) - the username / password and the sender's email must be strictly valid and authenticated. The tracker@mysite.com account must be activated. Also, google has an extreme... -
17:28 Defect #12648: Multiple levels of nested subtasks not displayed correctly in issue list
- Is this related to #10048 and/or #7417 ?
-
16:22
Feature #11313: Automatic closing of resolved issues
- For me it would also be useful to have such a feature. For me, the inspiration is the (old / classic-style) SourceForge.net tracker. There, a status "Pending" exists for issues. If an issue is put into status "Pending", then if no change...
-
16:11
Feature #13600 (New): Allows specifying "canned responses"
- I used to use the (old / classic) SourceForge.net trackers a lot (out of lack of alternatives, not of choice ;-). Overall, Redmine is a big win compared to it, but there are a handful of features I am missing.
One is the ability to sp... -
16:00
Feature #978: Different trackers on different projects?
- I already did that at the same time as commenting here :-). It is now up to somebody with the right access levels to work through the tickets we accumulated there... BTW, kudos for your impressive list there ;-)
-
15:53 Feature #13419: Scheduled vs. Actual issue time
- I was almost going to file this issue as well.
Now, as the Redmine has transformed from merely being a bug trackers to a full fledge software project mangement tool. It is important to note that while we can note actual start and due... -
15:33 Feature #13378: Custom fields Type Auto Number Increasing
- Interesting, but how/when will the custom field number get incremented?
-
15:31 Feature #13347: Filtering by issue subject with wildcard
- +1. This would be great to have.
-
15:29 Feature #13497: Document all available Redmine links properly
- Recently I came across issue #11056 which enlightend me that paragraph color and other such properties are actually possible in wiki texts. I still don't know which other such properties would be available.
Looks like many aspects ar... -
15:16 Feature #13595: Add text to Redmine links
- Aaah understood. This would be a good addition.
-
14:12 Feature #13595: Add text to Redmine links
- I think Miodrag is talking about changing the link label.
-
13:43 Feature #13595: Add text to Redmine links
- This works exactly as you are pointing out. Check this out :
-
12:09 Feature #13595 (Closed): Add text to Redmine links
- It would be useful to have url tekst when using Redmine internal links such as #124-6.
For example: -
14:46 Feature #1565: Custom query on My page
- Dipan Mehta wrote:
> This is a great plugin and works! This really transforms the "my page" experience. However, I saw one limitation. The regular query page allows you to sort the issue list based on different fields where as here they... -
14:08 Feature #1565: Custom query on My page
- Leos Prikryl wrote:
> This plugin https://github.com/Undev/redmine_my_page_queries works fine with Redmine 2.3.0.
This is a great plugin and works! This really transforms the "my page" experience. However, I saw one limitation. The r... -
07:33 Feature #1565: Custom query on My page
- This plugin https://github.com/Undev/redmine_my_page_queries works fine with Redmine 2.3.0.
-
14:34 Feature #5358: Share Issues Categories for sub-projects
- h2. +1
-
14:31 Defect #13231: Can't Delete Watcher On Current Trunk 2.3.x
- Which target version will this be available?
-
14:27 Defect #13597 (New): Redmine.pm and dots in username
- The Redmine.pm does not work with "." in the username, if you try to open
a repos with username included in the url like: https://firstname.lastname@redmine.org/git/project.git
This problems comes from the parsing of the "." in the p... -
14:26 Feature #7836: Ability to save Gantt query filters
- +1. Great feature.
-
13:59 Feature #13596 (Closed): Add setting to allow/deny time logging on closed issues
- Time logging should be only possible for issues which are open. May an options is added to the time tracking rights for a role.
-
13:53 Feature #3012: version field request
- The same applies to issues #5996 - is a duplicates of #2096 as well.
-
05:41 Feature #3012 (Needs feedback): version field request
- Dipan Mehta wrote:
> This functionality is now possible out-of-the-box using custom field of type "version".
> ...
I have set due date. -
12:19 Feature #3848: Permission to log time for another user
- Agreed. This is definitely something I need (my co-workers are very lazy on logging their times).
-
10:48 Feature #13593 (Closed): Restore deleted user info
- Please post in forum, this tracker is for Redmine core bugs and feature requests only.
-
07:58 Feature #13593 (Closed): Restore deleted user info
- I have accidentally deleted the user,wish to restore the same user I have the previous day db backup,
I want to restore only the user level information like bug assigned to the particular user etc..import to the current running latest... -
09:24 Patch #7443: Found-in-version patch
- Dipan Mehta wrote:
> How is this issue any different from #2096, which is already in the release?
It tracks released versions so you cannot choose a version which is not yet released and also which is closed (unsupported).
I see it ... -
08:01 Defect #7417: parent issue display problem
- Add related #10048 and #7907
-
08:00 Defect #7417: parent issue display problem
- +1. This is very important. Can we solved this in Redmine in 2.4 without having to use the plugin?
-
07:59 Feature #7907: Display Issues in a hierarchy (tree)
- +1. This is very important. Can we have it in 2.4?
-
07:58 Defect #10048: Secondary sorting after sorting by parent task
- +1. This is indeed very essential to be in Redmine.
-
07:39 Patch #11898: Inheritable issue categories
- Hi Serge, eventually I managed to test the patch. Now it works fine and I also validated against 2.2.4-stable. Thanks for the efficient support, Ruedi
-
07:19 Feature #2637 (Closed): Multiple email notification per issue
- Dipan Mehta wrote:
> This works as stated now. Watchers for every issue exist for a longtime now in the Redmine. This issue can be closed.
Thank you for your feedback. -
07:10 Feature #4015: Make app settings overridable at project level
- Dipan Mehta wrote:
> Also add #850 as a related issue.
Done.
-
07:08 Feature #2076 (Closed): Individual Permissions for Each Project
- Duplicate with #850.
-
07:06 Feature #4049 (Closed): Permission management on a per project basis
- yac yac wrote:
> +1
> ...
Thank you for your feedback. -
06:46 Feature #2974 (Closed): Hirarchical Issue tracking
- Dipan Mehta wrote:
> This can now be easily achieved through sub-task and issue relations. Hence this issue can now be closed.
Thank you for your feedback.