Activity
From 2014-05-05 to 2014-05-07
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...
2014-05-05
-
21:52 Feature #4885: Option to make time log comments field mandatory
- +1
-
21:46 Feature #16712: Create an up-to-date documentation for Redmine on Heroku
- Done,thanks again!
-
10:57 Feature #16712: Create an up-to-date documentation for Redmine on Heroku
- Etienne Massip wrote:
> Tanks, could you please create an howto in wiki?
Done, but as you can see maybe I did an error and opened a second version (>2.5.x), now i cant delete the first one (>25) that isn't linked in the How-To's.
Ma... -
20:37 Defect #16808 (Closed): No hook for issues closed by commit
- Notification plugins like "zulip-redmine-plugin":https://github.com/zulip/zulip-redmine-plugin seem to use the @controller_issues_edit_after_save@ hook. It doesn't look like this hook gets triggered when I mention or close an issue in a ...
-
20:14 Defect #15320: Changing Child's Parent Ticket Field To Parent's Parent fails.
- Using Redmine v2.5.1.
In @app/models/issue.rb@, there is the following bit of code. -
18:54 Patch #16685: Introduce the request_store gem to hold User.current and prevent data leakage in error messages
- Etienne: It's way too easy to introduce data leaks when dealing with before filters, either in the core or in Plugins, so this adds an additional safety net.
Also, the gem is actually about 10 lines of code, so not that much of a depe... -
18:33 Feature #2585: Add Modules to hide/display Overview, Activity, Roadmap
- Is there any plugging or a patch to do this.
_hide overview and road map module for specific role._ -
17:29 Feature #16807 (New): Allow strict before (<) or after (>) filters for dates
- Hello,
I guess I've found bug with Issues API. The problem exists with query like this:
@/issues.json?limit=100&offset=0&project_id=30&status_id=5&closed_on=<2014-04-01&sort=closed_on@
The following query works just like it is sup... -
17:22 Feature #2829: Ability to set default search filter for Issues
- +1
-
16:46 Feature #16638: Optimizing CSV export
- please give me feedback...
thanks -
09:07 Feature #16802 (New): Disable auto-filling tracker, status and priority in new issue creation
- Users, often don't pay attention on tracker field - just because it's alredy filled by system, and as result - issue gets wrong tracker. But if system will not fill it automaticly, user will more probably choose right tracker. The same ...
-
08:57 Feature #8417: per tracker configurable issue form layout with preview
- +1
-
06:53 Feature #16207: Use query name as the file name when exporting queries
- Toshi MARUYAMA wrote:
> You need handle non ASCII filename.
> ...
Sorry, it is #16711. -
06:50 Feature #16207 (New): Use query name as the file name when exporting queries
- You need handle non ASCII filename.
See #16207. -
06:51 Feature #16754 (Closed): File naming of exported custom queries