Activity
From 2012-09-21 to 2012-09-23
2012-09-23
-
21:21 Feature #11655: Implementation of a Issue Voting
- What do you think, is this a good idea for an implementation?
-
21:21 Defect #11904: Projects with many members are very slow in Redmine 2.0.3
- Jean-Philippe Lang wrote:
> FTR, the "New issue" page in a project with 200 members now loads in ~250ms on my dev machine and Redmine 2.1.
I tried it with the current Revision 10463, and it loads much faster! Thanks! -
16:41 Feature #1554: Private comments in tickets
- Jean-Philippe Lang wrote:
> Deoren Moor wrote:
> ...
That's awesome. I'm really excited about this feature. -
11:37 Feature #4244: Multiple email addresses for each user
- Jean-Philippe Lang wrote:
> Felix Schäfer wrote:
> ...
Hello,
I'm wondering if the needs explained by other users (issues marked as duplicate, latest comment above) are indeed the same.
In the meantime, plugins have been created to... -
09:40 Feature #4244: Multiple email addresses for each user
- This is unbelievable. So if I have different email addresses and I reply from a different email address that is not associated with my redmine account, the reply will get lost? Atleast redmine should bounce back and tell me of this. It s...
-
04:54 Feature #11911 (New): Considering users belonging to a group in "Issues/Report/Assigned to" Visualization
- When we have issues assigned to groups rather than to particular users, the report/assigned_to table only consider those issues for group accounting. I think they must be considered for the users - belonging to the group - too. This fac...
-
04:33 Patch #4905: Redmine.pm: add support for Git's smart HTTP protocol
- I have tested again and works.
It seems the patch was fine from the start, I just misunderstood and tried to access the repositories using the identifier, not the url :-/
Thanks for the fast response!
-
02:40 Defect #11880: Alternate theme colors by issue priority in issue list is wrong
- Working good for me (I'm using basecamp theme)
2012-09-22
-
23:57 Feature #1554: Private comments in tickets
- This one would be very helpful! We're thinking about a implementation of redmine in our current workflow and have many tasks where private comments would solve our problems!
-
18:20 Feature #1554: Private comments in tickets
- Deoren Moor wrote:
> When you say _a flag_, are you referring to a flag on the ticket or on each individual comment? My apologies if you've already answered this.
On each comment. -
17:17 Feature #1554: Private comments in tickets
- Jean-Philippe Lang wrote:
> this feature will be implemented as a simple flag in 2.2 and visibility configured on each role.
When you say _a flag_, are you referring to a flag on the ticket or on each individual comment? My apologies... -
16:16 Feature #1554: Private comments in tickets
- Jean-Philippe Lang wrote:
> Martin S. wrote:
> ...
I agree. Let's make the basic functionality a standard feature, and provide the rest (which only a few will need) through a plugin... -
12:04 Feature #1554: Private comments in tickets
- Martin S. wrote:
> +1 for a feature to be able to set the "visibility/viewing-restriction" of a comment to all users/a role/a group or even selected users.
This is overkill IMO. I'm not saying that it would be useless but still, this... -
19:00 Defect #11909 (Closed): Autocomplete results not reset after clearing search field
- h2. Explain for the defect
There are several autocomplete UI's for searching a specific field in redmine;
for example, *searching for user* (in a modal dialog when adding issue watchers) and *for user or group* (in the member tab of ... -
17:12 Defect #11888 (Resolved): No e-mail notification for non-members who are watchers
- Jean-Philippe, there is a patch at #8488#change-41085 that resolved this.
It also resolved watchers not able to view issues in non-public repository if the visibility type is issue that you are assigned or involved in.
Can this patch b... -
11:51 Defect #11888: No e-mail notification for non-members who are watchers
- If watchers are not allowed to view the issue (eg. issue from a private project), they won't be notified.
-
14:41 Feature #4052: Cross-project redmine links with alternate link text for source and export links.
- Still no plans to include this in near future? Wikis look awful without th ability to display a homan readable text for repository links.
-
11:54 Feature #11858 (Closed): Next issue number after deleting an issue
- Having to reset database sequences is not something I'd like to implement. Sorry but this is a no.
-
11:41 Defect #11904: Projects with many members are very slow in Redmine 2.0.3
- FTR, the "New issue" page in a project with 200 members now loads in ~250ms on my dev machine and Redmine 2.1.
-
11:34 Defect #11904: Projects with many members are very slow in Redmine 2.0.3
- Kristoffer Renholm wrote:
> This seems to be due to that each and every Principal is queried one by one
Fixed in r10440. The patch is pretty simple, you can try it out to see if it solves your performance issue. -
11:15 Defect #11905: Potential "can't dup NilClass" error in UserPreference
- Still, something is wrong with your new database. A safer process would be to create a blank postgres database then create the structure using db:migrate then import only the data from your old database. To solve the last error you've po...
-
10:41 Defect #11905: Potential "can't dup NilClass" error in UserPreference
- Just to be on the safe side, i've re-transfered all the redmine data from our old server (mysql) to the new one (postgresql) using NaviCat Data Transfer and all went well:
-
10:14 Defect #11905: Potential "can't dup NilClass" error in UserPreference
- I'm sorry but there's something seriously wrong with your database:
-
09:40 Defect #11905: Potential "can't dup NilClass" error in UserPreference
- Hi Jean-Philippe,
Applied the patch and now get a different set of errors.
First time I tried to login: -
08:20 Defect #11905 (Resolved): Potential "can't dup NilClass" error in UserPreference
- I never experienced this error when using 2.1.0. But I was able to write a test that triggers this error. It's fixed in r10438. The patch is pretty simple, you can apply it to your 2.1.0 instance then restart:
-
11:04 Defect #11880: Alternate theme colors by issue priority in issue list is wrong
- If it can be of use to someone, i've patched the css. It works on my installation with the same table that amree woot is sharing here.
-
09:47 Defect #11290 (Resolved): ParseDate missing in Ruby 1.9x
- Patch committed in r10439.
-
03:38 Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- I have upgraded to 2.1. Isn't the attributes hidden when you set it to read only?
2012-09-21
-
22:32 Defect #11612: Revision graph sometimes broken due to raphael.js error
- I am seeing this problem on 1.4 stable branch as well.
Any chance of a back-ported fix? -
21:51 Defect #11290: ParseDate missing in Ruby 1.9x
- This issue affects RedmineGraphsPlugin (which can be found at: https://github.com/hdgarrood/redmine-graphs-plugin/network
Here is a patch for 2.1.0: -
21:04 Feature #11907 (Closed): Custom Field Version (Locked/Open)
- I'd like to have custom fields that specifically only allow locked versions, and open versions.
For example, for affected/target versions should only be allowed to select locked (released) versions. Otherwise, the user who files an is... -
16:49 Feature #5487: Allow subtasks to cross projects
- Would be nice but please, kill two birds with one stone: fix defect #5490 "subtask priority/start date/due date" at the same time.
Thanks for your work, -
16:38 Feature #5358: Share Issues Categories for sub-projects
- Patch (against trunk r10433) proposed as issue #11898.
Should be portable with little work on versions 2.1 or 2.0.x
Should be portable with some more work on version 1.4.x
I do not know how much work would be necessary for versions 1.... -
14:45 Defect #11905 (Closed): Potential "can't dup NilClass" error in UserPreference
- Hello, we've recently upgraded from 1.4.4 to 2.1.0 and now we get the following error 500 when trying to open up any page:
-
12:48 Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- Gurvan Le Dromaguet wrote:
> For now, I am trying to code a patch for the hidden attribute capability
Any news on this? I would be happy to help you test it :-)
And it would be really great if it could make it into 2.2.0. Toge... -
12:46 Feature #1011 (Reopened): Add voting to tickets
- Since the "vote plugin" referenced as reason for closing this issue hasn't been maintained in over 3 years. I strongly urge this feature be reopened and reconsidered as part of redmine core. This is a essential feature, trac even has it ...
-
12:33 Feature #1011: Add voting to tickets
- +1
-
12:42 Feature #8392: Grant access to particular Wiki page
- Are there any news on this feature?
-
11:16 Feature #11150: order "Jumpo to Project" select and "Projects page" by Project name
- Anyone can confirm this issue, it is really annoying
-
09:47 Defect #11904 (Closed): Projects with many members are very slow in Redmine 2.0.3
- When having a project with ~100 members (many of them are reporters) Redmine slows down and new issue and show issue takes up to 6 seconds to load. This seems to be due to that each and every Principal is queried one by one, see log belo...
-
08:49 Feature #8488: Create an 'Involve' mechanism to private issues
- Attached is the patch for version 2.1.
The original patch resolve not only watchers for private issue.
It is also resolve, watchers not able to view non-public projects issues when they are path of the watchers list.
I am wonderin...