Activity
From 2014-05-06 to 2014-05-08
2014-05-08
-
22:43 Feature #16843 (Closed): Enable grouping on time entries list
- Currently, Time entries do not have the ability to be grouped. It would be a great feature to have it group by User, Date, Category, Tracker and/or Project. See screenshot for further details.
-
02:44 Patch #4776: Totals for Estimated Time
- We are still on Redmine 2.0.3.devel.10073 - I am surprised we have got so far behind, I need to check what is new in Redmine!
-
02:02 Feature #6846: Add VIM-like keyboard shortcuts
- Would be nice to rename this isse, and the related plugin, to "VIM-like" shortcuts. (Or, better yet (but harder): shift the focus explicitly toward _customizable_ shortcuts.)
Most of those, who also desperately need keyboard shortcuts... -
01:48 Feature #449: Keyboard shortcuts
- And, generally, for editing/updating stuff:
Ctrl+Enter => Submit -
00:51 Feature #1151: Open Links in New-Window
- See the "redmine_open_links_in_new_window plugin":http://www.redmine.org/plugins/redmine_open_links_in_new_window, which seems to do a good job at this!
2014-05-07
-
23:59 Patch #16828 (Closed): Redmine 1.1.3.stable (MySQL) - custom user list field
- We do not support version:1.1.3.
-
17:05 Patch #16828 (Closed): Redmine 1.1.3.stable (MySQL) - custom user list field
- Is there a way to add a custom field with the dynamics user list in the version 1.1.3?
I tried the feature_2096_adriano_crestani.patch but doesn't go, think different version.
Thaks
-
22:10 Patch #4776: Totals for Estimated Time
- Does this patch work with redmine 2.5.0?
-
18:13 Feature #1953: Due date calculation based on developer's estimations
- Here's my solution. It assumes 8 hour workdays and that Saturdays and Sundays are skipped as non-work days. It should be easy to adapt if your work schedule deviates from this.
Add the 'Custom Workflow' plug-in:
http://www.redmine.or... -
16:24 Feature #1953: Due date calculation based on developer's estimations
- All my +1s to this. Frankly, this is huge, and I'm a bit irritated that I've spent the last couple of days trying to get Redmine to do this. Using duration as an alternative to explicit due dates is a basic feature of every project manag...
-
16:23 Defect #10769: Unable to change the due date on an issue when updating
- This issue is still there in Redmine 2.5.0.stable. I sometimes can't change due date on a parent issue even if child issues do NOT have due date set.
-
13:59 Feature #16823 (Closed): IMAP STARTTLS support
- Dear developers of Redmine,
I was setting up receiving emails along the guidelines in http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails .
Our IMAP server listens on port 143, but not on the SSL port 993. It does not... -
09:40 Feature #16821 (New): Time tracking : duration since last update on issue
- Here is a common workflow : issue is new, then assigned to someone, then resolved by the assignee.
The idea is to know how much time has passed since last issue update (only shown if duration is < 24h) to help user to track their spen... -
05:47 Defect #16568 (Needs feedback): Referensing commits to issues across all projects
- It seems user does not have "View changesets" permission.
2014-05-06
-
21:44 Feature #16818 (New): Allow multiple relationships between two issues
- This happens in the current version of redmine from git (svn r13129), with mysql 14.14.
Steps to reproduce:
# Create an issue
# Create a copy of that issue
# Attempt to create a relation between the issues (e.g. set the copy to FOL... -
20:49 Defect #15320: Changing Child's Parent Ticket Field To Parent's Parent fails.
- It seems that the previous code (r3573), before r11641, which implemented subtasking (#443), allowed moving grandchild (descendents) around the tree. (@# move accepted inside tree@).
-
20:32 Defect #15320: Changing Child's Parent Ticket Field To Parent's Parent fails.
- The @elsif@ was added in r11641 to fix #8794 _Circular loop when using relations and subtasks_.
Based on this, it seems that #13654 (_Can't set parent issue when issue relations among child issues are present_) may also be related. -
19:20 Feature #12444: Ability to "set as default" settings when creating users
- +1
-
09:59 Feature #11253: Total time spent from subtasks on the issue list
- +1
-
09:30 Feature #3967: Ability to define default columns to display based on project
- +1
-
09:16 Feature #7360: Issue custom query: default query per instance, project and user
- +1
Each time we open the tasks list, every one of us has to rearrange the list before starting to use it. We have custom queries but you forget to select them. This feature would save a huge amount of time and bad language :) -
08:58 Feature #5754: Allow addition of watchers via bulk edit context menu
- +1
-
08:26 Feature #7907: Display Issues in a hierarchy (tree)
- +1 too.
The gantt diagram already contains it. But it is not enough.
I would create a new view for this. When the user is in the Tickets tab he or she should get the option to display the (existing) list view or the tree view. I th...