Activity
From 2013-10-31 to 2013-11-02
2013-11-02
-
23:51 Defect #15248 (Closed): Ticket count in roadmap view wrong
- One issue is marked as private, and because of that, is not shown in the roadmap. This is by design...
-
19:39 Defect #15248 (Closed): Ticket count in roadmap view wrong
- The issue statistic on the homepage for the coming version 2.3.4 is not consistent. It counts 15 issues but the list has only 14. Seems like 1 open feature issue is missing. Searching the issue list does only show 1 closed feature issue ...
-
14:59 Feature #15247 (New): Group definition by set operations on other groups
- So if you have groups eg "mechanical engineers", "electrical engineers" you can define group "engineers" to be a union of the two groups.
-
14:01 Feature #15246 (New): User groups whose members are different for each project.
- We are a shop with several different departments like Software, Mechanical or Electrical engineering.
My idea is to have the same User Groups - <X> Engineers. Then I could assign Issues to a group "<X> Engineers" but only to those who...
2013-11-01
-
20:17 Feature #5782: Rename "Boards" to "Forums" in project settings=>Modules
- Jan Niggemann (redmine.org team member) wrote:
> >The module for Forums is labeled Boards under the "Modules" section in project settings.
> ...
FTR: this was changed in r5261. -
19:41 Feature #5782 (Closed): Rename "Boards" to "Forums" in project settings=>Modules
- >The module for Forums is labeled Boards under the "Modules" section in project settings.
Not a tthe moment, closing this old issue. -
19:53 Feature #10080 (Closed): Forums in Reverse Chronological Order
- > "how do I make the forum so that messages are newest first"?
That's just the way it is in recent versions, closing. -
19:29 Defect #6565 (Closed): Error management
- Does not exist in recent versions.
-
16:32 Feature #11300: Update issue - form position
- Actually, yes. I just don't know Ruby syntax, that's why I used JS.
-
16:31 Patch #12524: Update issue - form position
- Ok
-
14:58 Feature #11220 (Closed): View hook on project copy options
-
08:52 Feature #11220 (Resolved): View hook on project copy options
- It's possible to use
-
14:06 Feature #1266: Feature: Allow setting multiple target-milestones
- +1.
We have several live versions running of a project. 1 issue unfortunately may be fixed in several versions. -
10:53 Feature #10569: Save user data on invalid form authenticity token
- I've tried to solve the session timeout problem here #15234.
-
08:45 Patch #15234: A popup message after session timeout
- > I guess that the patch won't work if redmine is installed with a sub-URI.
I've removed the slash in route.rb: -
06:57 Feature #5358: Share Issues Categories for sub-projects
- +1
we need to fragment projects into subprojects in order to not disclose VCS repositories to departments that don't need to see them.
Missing this feature is a blocker on categories for us.
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