Activity
From 2011-07-21 to 2011-07-23
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... -
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, th... -
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 fee...
-
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...
-
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...
-
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/is... -
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 fu... -
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...
-
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* ... -
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 repre... -
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 a... -
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 scr... -
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 ... -
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 f...
2011-07-22
-
22:58 Feature #1091: Disabling default ticket fields per tracker
- +1
-
22:43 Defect #8885 (Closed): Comenzemos a usar redmine para nuestro emprendimiento
-
17:36 Defect #8885 (Closed): Comenzemos a usar redmine para nuestro emprendimiento
- Para que estemos conectados, organizemos reuniones y subamos toda la informacion sobre los diferentes proyectos.
-
22:43 Defect #8886 (Closed): getting core dump while pushing above 400 connection
-
19:17 Defect #8886 (Closed): getting core dump while pushing above 400 connection
- Hi team,
I am using openchange client Version 0.11 (Transporter).While sending above 400 emails via opencghang... -
22:42 Defect #8887 (Closed): getting core dump while pushing above 400 connection
-
19:18 Defect #8887 (Closed): getting core dump while pushing above 400 connection
-
19:58 Feature #8488: Create an 'Involve' mechanism to private issues
- While I've read the commentary about how watchers are the wrong mechanism for this, I needed this functionality to up...
-
17:06 Defect #8884 (Closed): Assignee is cleared when updating issue with locked assignee
- h3. Steps to reproduce
# Assign issue to John Doe;
# Lock John Doe account;
# Update issue (e.g. change the stat... -
16:15 Feature #5272: Allow multiple target versions
- +1
Also see #219, #5510 and #1266. -
16:10 Patch #219: Issues fixed in multiple versions
- Any progress on this?
-
15:20 Defect #8883: Issues Rest API returns HTML instead of xml or json payload
- Sorry, in the Steps To Reproduce section there is an inconsistency with the logs.
It should stated : ... -
15:16 Defect #8883 (Closed): Issues Rest API returns HTML instead of xml or json payload
- Hi,
Seems that the issues Rest API is somehow broken in 1.2.1 version.
Hitting the appropriate url on both xm... -
14:55 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Etienne Massip wrote:
> Sure. But it would be illogical to give read-only access to these lists by API and not by ap... -
13:59 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Sure. But it would be illogical to give read-only access to these lists by API and not by application screens, wouldn...
-
13:05 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Indeed. But if the goal is to let users retrieve trackers and statuses in order to fill an issue form or set filters,...
-
12:47 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Jean-Philippe Lang wrote:
> * your patch makes the tracker and status lists accessible to administrators only
Act... -
12:07 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- Bevan Rudge wrote:
> It would be great to get this reviewed and committed.
Quick review:
* your patch makes the ... -
13:01 Feature #8881: Comprehensive Statistics - Contact Information Required
- Done - http://www.redmine.org/boards/1/topics/25293. Sorry for misposting.
-
12:20 Feature #8881 (Closed): Comprehensive Statistics - Contact Information Required
- Well, can you make it a RM plugin ?
I close the issue since this is not a feature nor a bug, you should post in fo... -
11:06 Feature #8881 (Closed): Comprehensive Statistics - Contact Information Required
- Sorry if this is an unusual way to approach one of the project admins. I'm working at a private company and we use Re...
-
12:17 Defect #8882 (Closed): my fone is off due to shortage of steamer!
-
11:31 Defect #8882 (Closed): my fone is off due to shortage of steamer!
- Dear All!
please note that i wont be available with my airtel number coz my fone has charge shortage due to electric... -
11:06 Feature #4267: <code> block improvements
- Generally +1
> For me, the inability to cut and paste code without the line numbers is a deal-breaker.
+10 on t... -
10:41 Defect #8880 (Closed): Error deleting issue with grandchild
- If I have three task level and I try to delete the parent task Redmine fails.
Task
|---> Sub Task Level two
... -
10:31 Defect #3087: Revision referring to issues across all projects
- +1
-
10:27 Feature #779: Multiple SCM per project
- Which patch works fine with current stable redmine release (1.2.11) ? Does any?
-
10:22 Feature #779: Multiple SCM per project
- +1
-
09:49 Defect #8877: empty page is shown after I use "group issue delete" operation
- Can't reproduce.
Plugin issue ? Log ? [[SubmittingBugs]]. -
03:19 Defect #8877 (Closed): empty page is shown after I use "group issue delete" operation
- select all issues in the list, right click, -> delete.
empty page is shown in version 1.2.1
the issues are not de... -
08:54 Feature #8879 (New): Update option for documents and files
- It would be very useful the possibility of *updating* documents or files in Redmine.
Beside the delete action could ... -
08:38 Feature #339: perforce SCM support
- Hi,
are there any news on Perforce support for redmine?
cheers
Markus
-
07:21 Feature #8878 (New): Different format for Dates in incoming emails
- We have changed the Date format to be 'DD/MM/YYYY'.
However when trying to set dates in incoming emails (i.e. Due ... -
05:22 Feature #7366: REST API for Issue Relations
- http://mushroom:3030/issues.xml?limit=25&project_id=test&offset=0&include=relations
- does NOT include relations.... -
03:53 Feature #8215: Allow plugins to register as a search provider without a project association
- Me too I'd like to have this feature for my plugins. +1
May you have a look, please, Toshi? -
01:13 Feature #7180: List of statuses in REST API
- in some cases I need to retrieve "*what are the available statuses for this issue*",
but sometimes I need to get "*w...
2011-07-21
-
23:52 Feature #7180: List of statuses in REST API
- Or maybe a way to include optionnaly all this information in the response to /issues/:id.
-
23:48 Feature #7180: List of statuses in REST API
- Ewan Makepeace wrote:
> Clearly populating menus with the values seen in a small sample of records is no way to be w... -
23:26 Feature #2770: Display of inline attached images in email notification
- And now I see why it was done that way: The same code is needed in app/models/mail_handler.rb, and the same probably ...
-
20:38 Feature #2770: Display of inline attached images in email notification
- This patch fixes the issue, but in a hackish way.
-
19:23 Feature #2770: Display of inline attached images in email notification
- Figured it out. The mailer is sending out the message as soon as the issue is created, which is before attachments ar...
-
17:17 Feature #2770: Display of inline attached images in email notification
- The problem is that the issues.attachment attribute doesn't have anything in it by the time it reaches parse_inline_a...
-
22:56 Feature #2964: Ability to assign issues to groups
- Jean-Philippe Lang wrote:
> I think it shouldn't. Because otherwise a user wouldn't be able to see the issues that a... -
00:05 Feature #2964: Ability to assign issues to groups
- Etienne Massip wrote:
> Well, if you configure assignable groups at project level, then you don't need this setting, ... -
22:50 Feature #1460: Project Plan import/export utility
- Fabián Varietti wrote:
> I need a plugin to import from a MS Project (XML format) to Redmine.
> In order to this, a... -
22:45 Feature #8876 (New): Activity commits improvement - display branch
- Hi all,
an activity message when somebody commits to the project's repository looks like this:
19:04 Myproject Revi... -
22:42 Defect #8874 (Resolved): Issue Updates without a journal details entry do not appear to users.
- Wow, my bad. I didn't think about that. I have the advanced roadmap plugin installed and it must be the root cause of...
-
22:35 Defect #8874: Issue Updates without a journal details entry do not appear to users.
- Do you have plugins installed ?
-
20:25 Defect #8874 (Closed): Issue Updates without a journal details entry do not appear to users.
- Env:
- MySQL 5.0.92
- Redmine 1.2.0
- Ruby 1.8.7
- Rails 2.3.11
When a user is looking at an issue (e.g. r... -
22:30 Defect #8857 (Closed): Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
-
12:04 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> Our redmine host machine is also the git repositories host and the path to the repository is lo... -
11:37 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- I think you can't with the rake way ?
Check [[RedmineRepositories#Attaching-an-existing-repository-to-a-project wi... -
11:36 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> So, how do I identify the specific project in the hooks call to script/runner? Is the project i... -
11:34 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- So, how do I identify the specific project in the hooks call to script/runner? Is the project identifier passed as a ...
-
11:19 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> Once the upgrade has been completed, can I reinstate the Autofetch function or does this change... -
10:39 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- One more thing I need to clarify that prefaces my last questions:
Once the upgrade has been completed, can I reins... -
10:27 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Felix Schäfer wrote:
> The better solution for you would probably be to use either a cron or a post-commit (svn) or ... -
09:11 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> Git hasn't changed, only the redmine git adapter has. What is the intended pay-back of the chan... -
08:58 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Perhaps I am overlooking something:
Using my staging environment with it's own separate database, I managed to get... -
08:56 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> Sorry Toshi but please clarify. It appears you are recommending to *de-select* Autofetch commit... -
05:28 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> Sorry Toshi but please clarify. It appears you are recommending to *de-select* Autofetch commit... -
05:14 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Sorry Toshi but please clarify. It appears you are recommending to *de-select* Autofetch commits but must I then manu...
-
04:34 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Paul Wilson wrote:
> Can this be done offline?
!repo-setting.png!... -
04:00 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- I believe I can confirm your conclusions. In my staging environment on a project with a small number of commits in it...
-
22:23 Defect #8873 (Closed): not able to Retrieve all projects
- Not a defect but a intended behavior.
-
22:22 Defect #8873: not able to Retrieve all projects
- Indeed, documentation states exactly, see [[Rest_api#Collection-resources-and-pagination|Rest_api#Collection-resource...
-
19:59 Defect #8873 (Closed): not able to Retrieve all projects
- When i try to get all the project using this
https://radar.twu.ca/projects.xml?limit=112
but it only return top 100... -
20:58 Feature #8875 (Closed): Allow manually fetching changesets
- I have Redmine installed on a local, virtual server. Most of my projects are on the same server, but one particular p...
-
19:40 Feature #7403: REST API for Versions
- I'll add support to Redmine Java API: http://code.google.com/p/redmine-java-api/issues/detail?id=56
-
19:39 Feature #7671: REST API for reading attachments
- Thanks! The more functionality is exposed through REST API - the better. I'll add support to Redmine Java API.
-
18:56 Feature #1011: Add voting to tickets
- Are someone using this plugin with Redmine 1.2.0, where is it available to download ?
I Found only a updated up to 2... -
17:09 Feature #1011: Add voting to tickets
- +1 This should be in Redmine basic features !
-
17:06 Defect #8546: Can't Delete Project - StaleObjectError
- +1
To delete the project I had to delete all issues in the project, then the delete worked.
Detail ... When I t... -
15:44 Defect #8546: Can't Delete Project - StaleObjectError
- I have the same problem too. Using redmine 1.2.1....
-
16:40 Feature #6220: Named action on ticket status change.
- what about this... would this be easier? To have e-mail notifications setup on queries, so when the result of the que...
-
15:09 Feature #8869 (Closed): London LEC
-
12:55 Feature #8869 (Closed): London LEC
-
14:02 Defect #8870 (New): Table in wiki is too long
- The problem attachment:wiki_table_bug.PNG
The fix attachment:wiki_table_fix.PNG needs a <div> around the table.
F... -
13:15 Feature #6833: Spent time in a configurable unit
- My plugin will be ready.
I put some screenshots to have an idea of what that looks like.
configuration screen:
... -
11:27 Defect #8868 (Closed): No Inventory Data
-
10:26 Defect #8868 (Resolved): No Inventory Data
-
10:26 Defect #8868: No Inventory Data
- wrong site ;) hehe
-
10:17 Defect #8868 (Closed): No Inventory Data
- Hello,
I've configured the foreman server and installed one client. The client is well sendint facts to server (I ... -
09:41 Feature #4527: plugin for Bugshooting
- +1
-
08:42 Feature #8867 (Closed): Per user themes
- Hi,
There is a "patch":http://www.redmine.org/issues/233 that allows per-project themes. Is it compatible with cur... -
07:10 Defect #3087: Revision referring to issues across all projects
- Felix Schäfer wrote:
> As far as I can tell, something similar (or that exactly) exists in currrent trunk, probably ... -
03:33 Feature #8817: Attachments/Plugin assets directory writable errors
- Agreed, this is pretty confusing for a new Redmine user. The messages should be much more specific about what directo...
-
01:02 Feature #6116: Group sub-tasks with parent on issue list
- +1
arthur me wrote:
> Patch applies correctly for me. This is an extremely handy feature.
Also available in: Atom