Activity
From 2013-10-29 to 2013-10-31
2013-10-31
-
20:55 Feature #15237 (New): Threaded discussion in forums
Many of my users would like threading in the discussion forums -- i.e a comment can be a reply to another comment, and discussions are listed in thread order, like an email thread list.
It seems this would require one field added in...-
20:14 Feature #15236 (Closed): Propose diff view for long text custom fields
- When changing a custom field, the diff in the History view and in the mail sent looks like :
* *My Custom field* changed from _previous text that can be quite long_ to _new text that can be even longer, where it can be difficult to sp... -
19:03 Patch #15234: A popup message after session timeout
- I guess that the patch won't work if redmine is installed with a sub-URI.
Also, won't the heartbeat request reactivate the session?
-
17:30 Patch #15234 (New): A popup message after session timeout
- When the session timeout is set and a user leaves an unsaved form for a while so their session expires and clicks on the _Save_ button, they is redirected to the login page and all unsaved data from the form just being edited are lost.
... -
18:13 Defect #15235 (Closed): Wiki Pages REST API with version returns wrong comments
- When I requested an old version wiki-page using REST API with version, Redmine respond contents with wrong comments.
see below:
# http://www.redmine.org/projects/redmine/wiki/Logo/24.json
# http://www.redmine.org/projects/redmine/... -
16:44 Feature #1565: Custom query on My page
- Ralph Twele wrote:
> +1 I could not get https://github.com/Undev/redmine_my_page_queries to work on my Redmine 2.3.0 Bitnami native stack for Windows.
It works fine on my redmine 2.3.3 Bitnami stack for linux. Great works!!! -
16:12 Defect #10931: Session does not stay logged in
- Hello.
I have the same problem.
Have any solution over the last year? -
14:39 Feature #11300 (New): Update issue - form position
- I don't think this should be done using JavaScript?
-
14:37 Patch #12524: Update issue - form position
- Please don't assign issues.
-
14:24 Defect #15226 (Confirmed): Searching for issues with "updated = none" always returns zero results
- Ketki Vahalia wrote:
> I agree that it is not necessarily incorrect to have "update time = creation time". The gap is that the query feature has the option of selecting "none" for updated_on field, but it will never be "none".
That's... -
08:22 Defect #15226: Searching for issues with "updated = none" always returns zero results
- I agree that it is not necessarily incorrect to have "update time = creation time". The gap is that the query feature has the option of selecting "none" for updated_on field, but it will never be "none".
Either we allow a query where ... -
14:18 Defect #15208 (Closed): Time issues when log spend time manual
-
08:30 Defect #15208: Time issues when log spend time manual
- oh you use Decimal time for Calculating.
thx for explanation. -
04:50 Defect #15208 (Needs feedback): Time issues when log spend time manual
- Please explain what error you are experiencing and where it happens. But be aware of [[FAQ#The-time-calculations-in-Spent-time-Reports-are-wrong|FAQ#The-time-calculations-in-Spent-time-Reports-are-wrong]].
-
14:15 Defect #15233 (Needs feedback): 500 in POST to /Users.xml
-
14:12 Defect #15233: 500 in POST to /Users.xml
- Please have a look in @production.log@ file, you should find the error stack trace in it.
-
13:10 Defect #15233 (Closed): 500 in POST to /Users.xml
- In an attempt to integrate redmine more tightly with my own applications, I'm trying to create users through the API.
I managed to get authenticated and get a list of current users, but on posting to /Users.xml, I get a 500.
I post... -
14:05 Defect #15211 (Closed): Progress line is pulled back to past by finished tickets
-
12:29 Defect #15211: Progress line is pulled back to past by finished tickets
- As Mischa pointed, original gantt chart does not have the problem I posted.
We are using an enhanced gantt chart for Redmine which purely inherit - according to them - the original progress line feature.
Please close this issue as an w... -
04:55 Defect #15211 (Needs feedback): Progress line is pulled back to past by finished tickets
- AFAICT closed issues aren't pulling back the progress line.
Please explain what you mean with finished/finalized/delaying issues (as in status being closed, %-done 100%, due date overdue, etc?). -
09:40 Feature #7907: Display Issues in a hierarchy (tree)
- +1
-
09:33 Feature #1266: Feature: Allow setting multiple target-milestones
- +1
In our case, we track issues by customer versions and also by server patch versions. Making a copy and remembering the relations is needless overhead for developers. There should be a clean way to accomplish the need of associating a... -
05:24 Defect #15231 (Closed): def calendar_for can't exactly displayed time
- This is more of a support request. Please continue on the forums.
-
03:37 Defect #15231 (Closed): def calendar_for can't exactly displayed time
- i have define a field(type:datetime).Now i want to call the def calendar_for to diaplay a calendar for selecting time,but the calendar only display date,no time by default.if i hope the calendar also displayed time ,how can i do?thank you
2013-10-30
-
19:50 Feature #15225: Need to be able to have separate markup formats for bugs and wiki pages
- That is a good example right there :-)
-
19:50 Feature #15225: Need to be able to have separate markup formats for bugs and wiki pages
- Stopping formatting would mean never pasting source code into a bug report, or always remembering to encapsulate it with
-
19:37 Feature #15225: Need to be able to have separate markup formats for bugs and wiki pages
- > In our case, for wiki pages it would be "reStructuredTex" (using a plugin) and for bugs it would be "none".
IHMO this use case only affects very few users.
> ...
Err, why don't your users just stop using formatting? -
06:54 Feature #15225 (Closed): Need to be able to have separate markup formats for bugs and wiki pages
- On our setup we are finding it problematic to have bugs formatted in textile (or any other markup text format) since people don't really pay attention to formatting when entering bugs.
On the other hand, we heavily use markup for wiki... -
19:35 Defect #15229 (Closed): Disable All Email Notifications
- Please ask questions in the forums.
That said, take a look at your youser preferences and set email notifications to "no events". -
13:44 Defect #15229 (Closed): Disable All Email Notifications
- I have tried to disable all email notifications going to my colleagues and myself, but I have been unable to do this.
Please see attached image. What else do I need to do?
Environment:
Redmine version 2... -
17:48 Feature #7907: Display Issues in a hierarchy (tree)
- +1
-
17:27 Feature #3224: Better project list
- I revised serval lines code in 2.3.3 to get this effect. It works for me to manage around 30+ projects without much scrolling.
> Parent Project A
> ...
Revision:
1) edit /2.3/app/helpers/projects_helper.rb, remove line 58~61 to hide... -
16:41 Patch #12524: Update issue - form position
- Actually, it's fixed by me and I used it on production Redmine version. Redmine develovers only need to apply the given patch.
-
05:12 Patch #12524: Update issue - form position
- +1 here. It would be great to have the position of the update form configurable (top/bottom) or correspond to the order of the comments.
-
16:15 Patch #11684: Truncate incoming emails
- +1 exactly what I was searching for, Thank you!
Just had to edit it for german mails.
The method of redmine works fine, but incase the email client adds something with a date or something like that it doesnt work, because you cant use ... -
14:26 Feature #2647: Repository browsing shall respect ACLs in repository
- Daniel Hger wrote:
> Hi Robert,
> ...
Hi Daniel,
My patch is specific to the official Redmine version as at 2.3 r12119. Once the official version moves on the patch may no longer work. You may however be able to update back to r1211... -
14:21 Feature #15228: Custom field - provide link custom field
- Did you have a look at :
http://projects.andriylesyuk.com/projects/extended-fields/wiki -
11:55 Feature #15228 (Closed): Custom field - provide link custom field
- Custom field - provide link custom field
like
User Add only value like- "01" in custom field when create issue
Admin side have default link - www.link.com \"@value@" which define in Custom field
After save it; When click on ... -
14:10 Defect #14953: Intermittent AJAX Atttachement Upload Failure in Firefox
- Is there any easy way to more to fallback to the none ajax method whilst I investigate ?
-
11:50
Feature #1448: Add tags to issues
- +1
-
11:28 Defect #15227 (Closed): Custom fields in issue form - splitting is incorrect
- I think there is a bug in the custom fields rendering:
app/views/issues/_form_custom_fields.html.erb -
10:58 Defect #15226: Searching for issues with "updated = none" always returns zero results
- I would not say having "updated"="created" set at issue creation is incorrect, it is a question of how you see things :)
There can be other queries where I want to see the recent issue activity, I will query "updated today" and get also... -
09:28 Defect #15226 (Closed): Searching for issues with "updated = none" always returns zero results
- I am using Redmine 2.2.4. Thanks for the great open source tool.
I would like to find new issues that have been added, but not updated. I tried to use the filter "updated" set to "none". I know there are issues without any update, but...
2013-10-29
-
10:03 Defect #15221 (Needs feedback): Issue title disapearing
- - Version 1.3.1 is very, very old and it is out of support.
- You have not read [[Submissions]]! Please read it and report back within a week, thank you. -
09:35 Defect #15221 (Closed): Issue title disapearing
- Like you can see in the attachment, The issue title doesn't appear in this project. Don't know what can happened.
Redmine version: Redmine 1.3.1.stable (MySQL)
Thanks in advance.
Diego -
05:35 Defect #15142 (Closed): Wrong project name in email notification subject after moving issue to other project
- Thank you for your feedback.