Activity
From 2011-07-23 to 2011-07-25
2011-07-25
-
23:38 Patch #7443: Found-in-version patch
- + for this as issue custom field type
-
00:06 Patch #7443: Found-in-version patch
- Hello!
Very needed patch!
Is this going to be ported to 1.2 version? -
23:19 Feature #8417: per tracker configurable issue form layout with preview
- "new wireframe url":http://gotiggr.com/preview/12656/
-
23:14 Feature #7784: Ordering/Placement of Custom Fields
- I create a issue #8417 with solution propsal which covers that request also.
-
19:05 Defect #8886: getting core dump while pushing above 400 connection
- This tracker is for Redmine core, not openexchange, you posted in the wrong place.
-
18:18 Defect #8886: getting core dump while pushing above 400 connection
- Hi etienne,
I am new for this openchange tool.Could you update me why the defect was invalid. is it know issue? -
17:39 Defect #8898 (Closed): Bug -Fix
-
16:53 Defect #8898 (Resolved): Bug -Fix
- Fixed this issue..
-
16:51 Defect #8898 (Closed): Bug -Fix
-
17:39 Defect #8544 (Closed): Issue Filter is being reset to Status = open
-
15:56 Defect #8544 (Resolved): Issue Filter is being reset to Status = open
-
15:56 Defect #8544: Issue Filter is being reset to Status = open
- This issue was resolved by migrating to version 1.2.1
-
17:23 Feature #482: Default assignee on each project
- +1
This is really a necessary feature. For us, issues tend to get lost sometimes until someone goes back and assigns issues without an assignee.
Etienne Massip wrote:
> I think it's a plugin, I don't have such setting.
Does any... -
15:53 Feature #8577: "Private" column and filter on the issue list
- Etienne Massip wrote:
> Please don't assign issues.
This implies another feature request ;-) -
13:31 Feature #8577: "Private" column and filter on the issue list
- Please don't assign issues.
-
10:05 Feature #8577: "Private" column and filter on the issue list
- +1
VERY important for our setup! -
14:44 Feature #8897 (New): Be able to reorder tasks/issues in the Gantt chart
- Issues are sorted by ID in the Gantt chart.
It would be nice to be able to change and save the display order of the issues in Gantt.
Today, a workaround is to duplicate the current issue to make it the last one, but this is not conveni... -
13:53 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- Well I do have a number of plugins, however I'm unable to indicate whenever they can interfere with the Rest API.
Here is the list of installed plugins :
* Redmine Charts v0.1.0
* Redmine Extended Spent Time plugin v0.0.2
... -
13:03 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- Are you sure you don't have any plugins which may affect the normal behavior ?
-
11:53 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- Hi, I've tried to patch the 1.2.1 according to the commit in trunk, but the issue persists.
I've attached the responses obtained with and without the patch, and they are both quite the same ( a couple of velues differ, but the result ... -
13:01 Defect #8896 (Closed): test
-
09:16 Defect #8896: test
- tian tian wrote:
> !1.jpg!
-
09:15 Defect #8896 (Closed): test
- !1.jpg!
-
10:17 Feature #5541: Project Status "Closed"
- +1 I use Redmine to manage all our student and research projects - currently there are over 300 and changing role permissions takes ages with so many projects.
-
03:18 Feature #7366: REST API for Issue Relations
- here's a sample XML file to illustrate the problem
-
03:16 Feature #7366: REST API for Issue Relations
- I see 1 problem with the implementation: both "forward" and "Reverse" relations are the same:
e.g. I have issues 1 and 2, 1 precedes 2.
I'd expect relations on 1 to say:
> "id=.. issue_id=1 issue_to_id=2 type=precedes"
and the re...
2011-07-24
-
23:58 Feature #3921: Google Wave + Twitter = Commie Plugin
- Looks like u missing the gem "twitter_oauth". Try to isatll that first.
-
23:53 Feature #3921: Google Wave + Twitter = Commie Plugin
- Moved here https://github.com/patrix/redmine_commie ?
Terence Mill wrote:
> I would like to look into it, but the git repository does not exist!
-
23:48 Feature #3921: Google Wave + Twitter = Commie Plugin
- I would like to look into it, but the git repository does not exist!
-
22:42
Defect #949: Style not applied to wiki image
- +1
-
19:38 Defect #8895: redmine.org changelog page pre formatting
- actually previous changelogs were done in this way - [[Changelog_1_0#v103-2010-10-31]]
-
19:35 Defect #8895 (Closed): redmine.org changelog page pre formatting
- Hi,
I think you should change formatting on [[Changelog]] page - putting list of changes into "pre" blocks makes ticket numbers not clickable.
It's way better to have changelog with clickable ticket #numbers - i've done the same in m... -
18:49 Defect #8633 (Resolved): Pagination counts non visible issues
- Patch applied in r6314, thanks.
-
18:00 Defect #8889: Activity page not refreshed correctly on updates which are not events
- Etienne Massip wrote:
> It does not prevent the events to be fetched from db and the activity report can be _big_, but maybe not that big (about 61k for current Redmine activity).
Indeed but it prevents the view rendering which is ab... -
17:36 Feature #7366: REST API for Issue Relations
- Added in r6313. You can now use @/issues?include=relations@.
-
16:29 Defect #7969: Redmine dosn't work with sqlite3-ruby 1.3.3
- > the problem occurs because with sqlite3-ruby 1.3.3, "settings_updated_on = Setting.maximum(:updated_on)" is a String.
Do you have some incompatible plugins installed, by any chance? In my case, stuff_to_do_plugin produces this probl... -
15:05 Feature #8891: Ability to manage Role assignments by individual Group Member.
- Agree with Terence.
-
09:38 Feature #8891: Ability to manage Role assignments by individual Group Member.
- I think that "problem" should be solved by proper groups and not using groups a container for people of same role. In user mangament system like ldap you have organizational groups or project groups and if u use roles you would would hav...
-
14:22 Defect #8894 (Closed): Private issues - make it more obvious in the UI?
- Intro: Redmine is used at my organization (a consortium of hospitals) in the IT department ... and we are going to start rolling out to other departments. If it fails to scale to thousands of users, well, I'm fired. :-)
But the point ... -
14:06 Defect #8892: Unused fonts in rfpdf plugin folder
- Jean-Philippe Lang wrote:
> There are many fonts in source:/trunk/vendor/plugins/rfpdf/lib/fonts@6030 that doesn't seem to be used (eg. DejaVuSerif, DejaVuCondensed, DejaVuMono, FreeMono, vera, times...). Could we remove them?
Yes, I... -
10:48 Defect #8892 (Closed): Unused fonts in rfpdf plugin folder
- There are many fonts in source:/trunk/vendor/plugins/rfpdf/lib/fonts@6030 that doesn't seem to be used (eg. DejaVuSerif, DejaVuCondensed, DejaVuMono, FreeMono, vera, times...). Could we remove them?
-
13:17 Feature #8893 (New): General sharing among projects
- The basic problem is sharing elements of information among projects in the tree. Such elements include members (#5605), but also issue categories and other items. I noticed a simple and elegant implementation of this in the versions sett...
-
11:34 Defect #7966 (Closed): MailHandler does not include JournalDetail for attached files
- Fixed in r6312.
-
10:36 Defect #8880 (Resolved): Error deleting issue with grandchild
- Fixed in r6311.
-
09:46 Feature #2964: Ability to assign issues to groups
- I didn't request that feature, but assigning issues dependent on role touches a feature request i made some time ago.
#8050 proposes to be able to set visibility, read-only or mandatory property of every field (also of assignee) depend...
2011-07-23
-
22:53 Feature #2964: Ability to assign issues to groups
- Jean-Philippe Lang wrote:
> The baheviour of assigned to <<me>> is unchanged for now.
If <<me>> does not include <<<my groups>>, users could easily miss issues assigned to their groups. If <<me>> includes their groups, one could st... -
20:24 Feature #2964: Ability to assign issues to groups
- Etienne Massip wrote:
> This may be true only if you don't consider this feature as a way to "pre-assign" issues, that is assign an issue to a group of which one chosen / random person will eventually be directly assigned to work on it.... -
20:20 Feature #2964: Ability to assign issues to groups
- Feature committed in r6306. The baheviour of assigned to <<me>> is unchanged for now. I'd really like to get some feedback from people who requested this feature.
-
22:49 Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory
- +1
-
22:28 Feature #8891 (New): Ability to manage Role assignments by individual Group Member.
- Currently, assigning a Group to a Project and Role is an all-or-nothing proposition, as one can only assign an entire Group to a Project Role, and once assigned, individual Group members cannot be removed from that role.
We have group... -
21:54 Defect #7136: assign admin account to all bugs
- Can't reproduce. BUT note that an issue can always be assigned to its author (even if he is not a project member). So for example, say I'm an admin, I create an issue in a project I do not belong to => I see my name in the assignee drop ...
-
21:26 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- I think you're getting html because something goes wrong with your issue query.
See source:/trunk/app/controllers/issues_controller.rb@6210#L99
I have to fix this behaviour. -
18:39 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- Jean-Philippe Lang wrote:
> Can you attach the full html response please?
Not before monday, but I'll post the full response as soon as I get my hands on it.
Also note that only the index/list returns the html rendering. Getting a... -
16:10 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- Can you attach the full html response please?
-
21:24 Defect #8884 (Resolved): Assignee is cleared when updating issue with locked assignee
- Fixed in r6308.
-
16:08 Defect #8884: Assignee is cleared when updating issue with locked assignee
- Confirmed on trunk.
-
20:54 Feature #8867: Per user themes
- Hi,
there is "redmine_theme_changer":http://www.redmine.org/plugins/themechanger -- this is what searched for. -
17:42 Defect #8889 (New): Activity page not refreshed correctly on updates which are not events
- Since of r2982, any updates made to issues (among others, see #5425 or #5749) which are not handled as @events@, like Description update or even move to a different Tracker, won't be seen in the activity report if you refresh the page.
... -
17:05 Defect #8874 (Closed): Issue Updates without a journal details entry do not appear to users.
-
16:28 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Not 405, 406 is right.
-
15:58 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Jean-Philippe Lang wrote:
> Not matter which issues or projects they can see, they can always see the list of *all* statuses and trackers in the filters.
Oh, sorry, I thought they could only see statuses used in workflows tied to tra... -
15:32 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Etienne Massip wrote:
> Except that they can view issues of visible projects only, that's not exactly the same representation.
Not matter which issues or projects they can see, they can always see the list of *all* statuses and track... -
14:38 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Jean-Philippe Lang wrote:
> Users with a @view_issues@ permission already have access to ids/names of all trackers and statuses at /issues (look at the filters). Having a permission to give access to a different _representation_ of the ... -
16:10 Feature #8888: Add a link / button to get back to the Issue/Time tracking screen from the "Log time" screen
- Yes, works, but unintuitive, could we add a "Cancel" button aside the "Save" button ?
-
16:06 Feature #8888: Add a link / button to get back to the Issue/Time tracking screen from the "Log time" screen
- Browser back button?
-
07:34 Feature #8888 (Closed): Add a link / button to get back to the Issue/Time tracking screen from the "Log time" screen
- I opened "log time" screen to record time on the issue and then changed my mind.
how can I get back to the issue screen? there's no link for that. -
16:02 Defect #8633: Pagination counts non visible issues
- Same with tests @issues_count@ and @issues_count_with_archived_issues@.
Please note that default test data includes issues which are not visible, so both tests would fail without the @Query@ fix. -
13:28 Defect #8633: Pagination counts non visible issues
- proposed patch
-
15:49 Defect #8880: Error deleting issue with grandchild
- Confirmed with pg on trunk and exact same stack trace.
-
15:08
Feature #1005: Add the addition/removal/change of related issues to the history
- +1
-
15:07
Feature #7892: Issue relationships history and notification on delete
- duplicate of #1005
-
13:34 Feature #582: Make fields mandatory/unmandatory based on role
- +1
-
11:22 Feature #5272: Allow multiple target versions
- In general multiselect switch feature should be possible for all fields, also custom fields of type list or enumeration.
-
11:22 Feature #1266: Feature: Allow setting multiple target-milestones
- In general multiselect switch feature should be possible for all fields, also custom fields of type list or enumeration.
-
11:21 Patch #5510: Enable Mutliple Versions Per Issue
- In general multiselect switch feature should be possible for all fields, also custom fields of type list or enumeration.
-
11:21 Patch #219: Issues fixed in multiple versions
- In general multiselect switch feature should be possible for all fields, also custom fields of type list or enumeration.
-
07:19 Defect #8641: Subissues is not created by REST API
- I switched Redmine Java API to be tested with Redmine 1.2.1 (with every auto-build).
-
07:16 Feature #7366: REST API for Issue Relations
- at least the issues list should include number of relations for every task, so that if it's not == 0, I'd load them for that particular task (instead of trying to query every single task).
This is an important feature for data import-ex...