Activity
From 2016-11-26 to 2016-11-28
2016-11-28
-
19:50 Feature #24477 (New): CSV export feature for thousand of issues
- At the moment, it is not possible to export thousand of issues with many custom fields. The request takes either too much time to respond (resulting in timeouts if gateways are used), or too much memory.
It would be great to have a CS... -
16:18 Defect #24473: CSV Export Very slow for issues with lots of Custom Fields
- I have attached a (dirty) patch which fixed the problem for me. The export time is basically twice faster.
-
12:23 Defect #24473 (New): CSV Export Very slow for issues with lots of Custom Fields
-
15:13 Feature #4097 (Closed): Batch issue creation: keep previous selected values in the new issue form
-
14:14 Feature #24013: Firebird and RedDatabase support
- Fixed issue number of patch files.
-
14:06 Feature #24013: Firebird and RedDatabase support
- These are patches which remained attachment:Firebird_support_v3.patch after r16008 and r16009.
I think attachment:issue-24013-r16009-db-migrate.diff breaks existing system. -
13:58 Defect #23055: Error with Fetch commits with Mercurial repository when log has invalid char
- I can also confirm this. Any workaround?
Environment:
Redmine version 3.2.0.stable
Ruby version 2.3.1-p112 (2016-04-26) [x86_64-linux-gnu]
Rails version 4.2.5
Environment ... -
12:36 Feature #16638: Optimizing CSV export
- Stephane Evr wrote:
> Same problem here, with Redmine 3.3.0-stable. It goes on and on for thousand of log lines:
> ...
FTR: #24473.
-
11:02 Feature #16638: Optimizing CSV export
- Same problem here, with Redmine 3.3.0-stable. It goes on and on for thousand of log lines:
-
11:23 Defect #24470 (Closed): How to add header and footer in issue pdf report
- Please use forum for question.
If you have feature request, please describe more details. -
10:11 Defect #24470 (Closed): How to add header and footer in issue pdf report
-
11:02 Feature #24469 (Needs feedback): In the Gantt chart I'd like to add a new row function sequentially same as a ticket tab by order
- We can reorder issues in "Issues" page by clicking header column.
Is it correct that you want to reorder issues in Gantt page in the same way? (showing more column other than subject and reorder issues in gantt by cliking the header).
-
08:59 Feature #24469 (Needs feedback): In the Gantt chart I'd like to add a new row function sequentially same as a ticket tab by order
- I contribute it for the first time
I expect a new feature
In the Gantt chart I'd like to add a new row function sequentially same as a ticket tab by order
-
10:36 Defect #22977: A project member has no access and gets no notification, when being a watcher of the issue
- Hi again, I have double-checked this behaviour in version 3.3.1 too. Is it a chance to confirm this issue? Thanks.
2016-11-27
-
05:54 Feature #4097: Batch issue creation: keep previous selected values in the new issue form
- Closing as a duplicate of #7623.
-
05:51 Feature #15549 (Closed): Remember previous selections when creating multiple issues
- Closing this issue as a duplicate of #4097.
-
05:28 Feature #14164 (Closed): filter issue list by version status
- Implemented as a part of #23215.
This feature will be available in Redmine 3.4.0. -
05:26 Feature #20197 (Closed): Filter Issue by attribute of the Version
- Implemented as a part of #23215.
This feature will be available in Redmine 3.4.0.
2016-11-26
-
20:21 Feature #12444: Ability to "set as default" settings when creating users
- +1 - Now that we are using redmine more, this would be really useful to have. Currently, our users are set up on LDAP. And for every user, we need to change the timezone manually. Thanks.
-
16:09 Defect #24433: The changeset display is slow when changeset_issues has very many records
- Thank you for fixing.
> Maybe we should also add an index on changeset_id to speed up the display of related issues on the changeset view. Do you have performance issues on the changeset view too?
There is no performance problem in... -
10:54 Defect #24433 (Resolved): The changeset display is slow when changeset_issues has very many records
- Index added in r16007.
Maybe we should also add an index on changeset_id to speed up the display of related issues on the changeset view. Do you have performance issues on the changeset view too? -
10:06 Patch #24296 (Closed): Add tablename to siblings query to prevent AmbiguousColumn errors
-
10:04 Patch #24283 (Closed): Validate length of string fields
-
10:02 Defect #24348 (Closed): acts_as_versioned use old style (Rails 2.x) of method call for #all
-
10:01 Defect #24297 (Closed): Show action not allowed for time entries in closed projects
-
09:56 Defect #24041 (Closed): Issue subject is not updated when you select another issue in the new "Log time" page
- Some routes were changed, setting target to next major release.
-
09:54 Defect #24439: Uable to add module on My Page
- Could you try r15998 instead of the proposed fix? Thanks.
-
09:25 Patch #24062 (Resolved): Allow only vertical reorderingin sortable lists
- Committed, thanks.
-
05:31 Patch #24062 (New): Allow only vertical reorderingin sortable lists