Activity
From 2011-07-20 to 2011-07-22
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 opencghange client getting the following error with core dump.For sending multiple mails using for loop logic in shell script.
... -
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 upgrade my company to v1.2.1 and meet our privacy needs. We'd previously been using the 'view own issues' patch in an old ...
-
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 status to @Closed@).
h3. Result
* *Status* changed from _New_ to _Closed_
* *Assignee* deleted (-John Doe-)
h3. Ex... -
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 xml or json entry points returns a HTML page instead of xml or json payload.
Note that the projects API does not have t... -
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 application screens, wouldn't it be?
Not so illogical if you consider that, unlike API users, web users _do not need_ t... -
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't it be?
I mean, to keep some consistency, this might be the concern of a second patch which would add a new ??read ... -
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, it doesn't work.
-
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
Actually, lists are already accessible to administrators only (in admin screens) ?
-
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 tracker and status lists accessible to administrators only
* no tests -
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 forum a full description of the product so you could get some help. -
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 Redmine for our daily bug tracking. Out of personal need we wrote a quite comprehensive statistics application that connec...
-
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 electricity shortage since on monday!
I will be available via 0713 937 823 though by the end of this day it may also run short ... -
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 this
-
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
|---> Sub Task level three
But if I delete the sub task Level two and after the parent Redmine works
I te... -
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 deleted. -
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 be a new update one.
By doing this, the attachment number will remain the same, and all references in wiki pages or iss... -
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 Date) it will only work if we use 'YYYY-MM-DD'.
Is it possible to extend it so that it can match our chosen date form... -
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. this only works for a particular issue, not for "get issues" request.
which means if I have 100 issues to load from Re... -
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 "*what are all possible statuses in this project*" - that is if I'm building a search form for issues in some application...
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 writing a UI but until REST provides enumeration of Status (and other fields) all developers of plugins and desktop softw... -
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 needed for issue updates after their attachments are... attached.
-
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 are added: source:trunk/app/models/issue_observer.rb.
Now-- how to fix it? Delay the mailer until later in the creation... -
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_attachments (source:trunk/app/helpers/application_helper.rb#L504). (The attachments are saved in source:trunk/app/control...
-
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 are assigned to _him_ and not to its groups.
From a assignee pov, I can't see the difference between being assigned di... -
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, do you ?
Actually, it will be usefull to adjust the UI for people who don't want to see anything about issue assignment... -
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.
> ...
Task Adapter does exactly this: export data from MSP to Redmine (and vice-versa): http://taskadapter.com -
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 Revision 505:ea8b0f632816: done something
John Doe
(I use Mercurial, but I think that this may apply to other SCMs, too... -
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 the issue since if I disable that it all works fine. Now that it's narrowed down I should be able to fix that or just d...
-
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. redminepath/issues/##), any update with no journal_details entry (just a notes update) does not show up for non-admin use... -
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 local and references the actual repository, not a Git bare repository. I am thinking of a hook calling 'ruby $RedmineEnvir... -
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 wiki]] for details.
-
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 identifier passed as a parameter?
Just give me minute, pretty swamped here :-) -
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 parameter?
-
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 to the redmine Git adapter necessitate leaving it disabled and fetching commits by other means?
If you add the post-... -
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 reinstate the Autofetch function or does this change to the redmine Git adapter necessitate leaving it disabled and fetching ... -
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 post-receive (git) hook to call the rake task or the runner as described in the FAQ. Those can also be adapted to fetch ... -
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 changes to the git adapter? As it stands now using git as the repository, the hit we are taking with the useability is unacc... -
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 one project's changesets updated and was finally able to normally browse this project's repository metadata after the u... -
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 commits but must I then manually fetch commits somehow using cron or a hook?
If you have only one web process, that will be... -
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 commits but must I then manually fetch commits somehow using cron or a hook?
Yes. -
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 manually fetch commits somehow using cron or a hook?
-
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 its repository, I was finally patient enough to wait for the process to complete.
Our usage load permits it so I run ou... -
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-resources-and-pagination]]:
the number of items to be present in the response (default is 25, maximum is 100) -
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 projects Doesn't matter what I set my limit to, it will only return 100 projects.
Can you please help me with this. -
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 project uses an external SVN repository.
I've noticed that automatically fetching the change sets on every page refres... -
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 2009 in https://github.com/Ubik/redmine_vote !!
Is it abandoned ?
If so, we need to reopen this ticket ! -
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 tried to delete the tasks i had to delete first the subtasks, when I tried to delete all tasks in one delete I received 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 query changes and e-mail is sent? That would provide more flexibility and probably and easier user experience. That's of c...
-
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.
File /{redmine_root}/lib/redcloth3.rb -
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:
!config.JPG!
issue detail:
!issue_details.JPG!
Update 1:
!update1_1.JPG!
!update1_2.JPG!
Update 2:
!update... -
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 can see them in /var/lib/puppet/yaml/facts) but when I import them to foreman I still see the "No Inventory Data" for th... -
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 current Redmine (1.2.1)? Also why not this to be widened to support per-user themes? I think this patch could be incorporat... -
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 0.9-stable too, closing this issue.
I tested in 1.2.0, using commit messages, you can indeed create references to iss... -
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 directories aren't accessible.
Also, in my case its because the directories don't appear to exist (though I can't be certain... -
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.
2011-07-20
-
23:59 Defect #8863 (Closed): Task copy bug
- Closed as duplicate of #6056.
-
17:06 Defect #8863: Task copy bug
- My system information
About your application's environment
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.3.7
Rack version 1.1
Rails version 2.3.11
Active Record version 2.3.11
Active Resource version 2.3.11
Action Mailer... -
17:06 Defect #8863 (Closed): Task copy bug
- When I copy two related tasks is not copied the relationship between them
-
23:58 Defect #6056: Bulk copying of issues does not preserve relations
- More like a feature to me.
-
23:56 Defect #949: Style not applied to wiki image
- +1
Is this ever going to be fixed?? -
23:56 Defect #8633: Pagination counts non visible issues
- @Query#issue_count@ (source:/trunk/app/models/query.rb#L504) returns:
-
10:08 Defect #8633: Pagination counts non visible issues
- #8848 tell us it is due to archived projects.
-
23:45 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- > Selecting on the 'repository' tab spawns a process:
> ...
This is intended behavior.
Redmine Git adapter had big problems in fetching revisions.
* From 0.9.0 to 0.9.2: #4547, #4716
* From 0.9.3 to 1.1: #7146
To resolve these... -
14:53 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- dedalus - wrote:
> I suppose that I should change some things in config/configuration.yml
I suppose is the path to mercurial binary and python libary
-
14:49 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- I have similar problem upgrading to 1.2.1: my mercurial repros are unreachable (error 500): maybe it's related to new default utf-8 encoding? I suppose that I should change some things in config/configuration.yml because in administratio...
-
11:42 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Ok, sorry for misreading.
-
11:36 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- I wrote above:
> "The git repository is local to this machine and I can execute the command interactively as the user that owns the redmine deamon and results are nearly immediate."
The daemon is normally as the machine's apache user... -
11:23 Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Did you try to run the git command line in a shell ?
-
10:53 Defect #8857 (Closed): Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first time
- Our installation has been stable and using git repositories for well over one year now. Four months ago the upgrade from 1.1 (r5184) to 1.1.2 went without a hitch but this upgrade from 1.1.2 to 1.2.0 or 1.2.1 (I tried both revs with the ...
-
23:14 Feature #2964: Ability to assign issues to groups
- Jean-Philippe Lang wrote:
> Jan Wedekind wrote:
> ...
Well, if you configure assignable groups at project level, then you don't need this setting, do you ?
> Feedback is welcome.
Looks like a very good idea.
> ...
I revised my positio... -
20:10 Defect #8866 (New): BugTraq references in commit message breaks revision references
- We use BugTraq properties to relate our commits to Redmine issues. This can cause issues when referencing a revision in a wiki page.
When you add a revision reference in a wiki page such as -
19:05 Defect #8836 (Resolved): Additional workflow transitions not available when set to both author and assignee
- Confirmed and fixed in r6300.
-
18:29 Defect #8865 (Resolved): Custom field regular expression is not validated
- Fixed in r6298.
-
18:27 Defect #8865 (Closed): Custom field regular expression is not validated
- Entering an invalid regexp for a custom field triggers an error on custom value validation.
-
17:00 Defect #3512: can't use 'Target Version' field in custom query when 'For All Projects' checked
- +1 for getting this fixed. Anyone?
-
16:36 Defect #8861: Wrong render of bold text
- No, part of text was just copied from web page directli to wiki text editor.
Sorry for wrong ticket, but how to find such spaces in text? There is no way except a looking for symbol codes in external editor.
It seems to me, one of the... -
15:55 Defect #8861 (Closed): Wrong render of bold text
- You have a non-breaking space HTML entity located right after both ending asterisks, maybe written down here by some WYSIWYG editor ?
-
15:20 Defect #8861 (Closed): Wrong render of bold text
- Following text do not render words as bold. If you see asterisk symbols in text below - it's still not fixed yet. It's very stupid problem.
When prepare data to create new item in DB, it must set fileds *Type* and specify file name in... -
16:21 Feature #643: Issue description templates
- +1
-
16:00 Feature #6116: Group sub-tasks with parent on issue list
- Patch applies correctly for me. This is an extremely handy feature.
-
15:47 Defect #8860 (Closed): solicito um login
- Use http://demo.redmine.org for testing purposes.
-
15:14 Defect #8860 (Closed): solicito um login
- solicito um login para acessar os programas do hu e desenvolver os meus serviços.
-
15:47 Defect #8862 (Closed): solicito login
- Use http://demo.redmine.org for testing purposes.
-
15:32 Defect #8862 (Closed): solicito login
- solicito uma senha para abrir o meu computador e estar ultilizando os programas do HU e desenvolver meus deveres.
-
11:10 Feature #8858 (Closed): Extend new issue visibility criteria: issues created by or assigned to the user
- ...including clause "or watched by the user" (if I want that a lower user see some bug for reply to a question)
-
10:32 Feature #2850: Add next/previous navigation to issue
- +1 this is a real issue for me moving from JIRA, I really don't mind how it is implemented (whether it updates the list when issues are amended or whether the list is static from your results) but just having to go back using the browser...
-
10:08 Defect #8848 (Closed): Custom queries count, count also issue of archived projects
- Closed as duplicate of #8633, thanks for the explanation.
-
08:53 Defect #8848: Custom queries count, count also issue of archived projects
- As show in attachment:bug-in-action.png, the custom query show the right number of bugs (excludes tha bugs related to hidden project). The count of total numbers of bugs assigned to me is wrong, because include also the "hidden" bugs
-
09:43 Defect #8849: Defaults aren't honored in release 1.2.1 (regression)
- Etienne Massip wrote:
> Yes ?
Ok?
attachment:old-behavior.png
attachment:new-behavior.png
-
09:27 Defect #8849: Defaults aren't honored in release 1.2.1 (regression)
- dedalus - wrote:
> Etienne Massip wrote:
> ...
Yes ? -
08:41 Defect #8849: Defaults aren't honored in release 1.2.1 (regression)
- Jean-Philippe Lang wrote:
> Can not reproduce. The default value for an integer custom field is present on the new issue form.
The issue isn't related to new issue form; for example, if I have an issue that was submitted before that ...