https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292008-09-26T00:04:53ZRedmineRedmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=49602008-09-26T00:04:53ZAnonymous
<ul></ul><p>I'm all in favour of this too.</p>
<p>This is the one reason that I nearly chose FogBugz over Redmine (we may still switch - nothing is ever set in concrete!), and it's a really important one at that.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=49892008-09-30T21:24:05ZJeff Dombach
<ul></ul><p>I vote for this as well.</p>
<p>I am using Redmine until I can cost-justify Fogbugz. I also prefer the method Fogbugz uses of the developer inputting the number of hours remaining instead of percent completion.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=58282008-11-26T15:49:02ZMauricio Miranda
<ul><li><strong>Assignee</strong> set to <i>Thomas Lecavelier</i></li></ul><p>I created this feature request 2 month ago and I have no response from your side. We really think it's a good and very useful feature and we can contribute to the project developing if you agree.</p>
<p>Btw... Thomas, I assigned it to you because you answered my question on the forum (<a class="external" href="http://www.redmine.org/boards/1/topics/show/2447">http://www.redmine.org/boards/1/topics/show/2447</a>)</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=77862009-03-03T22:22:34ZMauricio Miranda
<ul><li><strong>Assignee</strong> changed from <i>Thomas Lecavelier</i> to <i>Jean-Philippe Lang</i></li></ul> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=101582009-07-14T08:40:56ZMichael Diederich
<ul></ul><p>+1 - I also request theses features!</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=101632009-07-14T15:02:14ZMauricio Miranda
<ul></ul><p>I think there is a lot of people who would like this feature but nobody from redmine answered or commented the issue. May be we can build it as a plugin but I think the best way is to add it to the main structure. Let me know what you think.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=102512009-07-19T04:17:32ZEric Davis
<ul><li><strong>Assignee</strong> deleted (<del><i>Jean-Philippe Lang</i></del>)</li></ul><p>Mauricio Miranda wrote:</p>
<blockquote>
<p>May be we can build it as a plugin but I think the best way is to add it to the main structure. Let me know what you think.</p>
</blockquote>
<p>Building a plugin would be best. Once the plugin is ready, we can see about adding it to the core.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=129502009-12-14T18:32:11ZDavid Davis
<ul></ul><p>+1 for this feature from me as well. Is anyone currently working on this? Just wondering if this is actually under development in the mainline or as a plugin, or if it's stalled. I might be willing to contribute some time to trying to implement this if it's not currently going anywhere.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=129642009-12-15T00:01:59ZMischa The Evil
<ul></ul><p>Maybe the <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/PluginSchedules">Schedules</a> plugin fills your request partially?</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=129832009-12-15T18:48:59ZDavid Davis
<ul></ul><p>I banged out an attempt at this feature and submitted a pull request from edavis10 on github. We'll see if it makes it in, as it's my first attempt at contributing to Redmine. I'll post an update here if the functionality does make it in, and if it doesn't maybe I can figure out how to make a plugin that would add the functionality that way.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=132462009-12-24T19:13:25ZEric Davis
<ul></ul><p>David Davis:</p>
<p>Could you post a link and/or patch here? I'm the only one that gets pull requests and I don't want to roadblock this issue if I'm busy.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=133342009-12-28T20:51:52ZDavid Davis
<ul><li><strong>File</strong> <a href="/attachments/2964">issue_1953.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2964/issue_1953.diff">issue_1953.diff</a> added</li></ul><p>Posting patch; this is based on redmine 09e47a3b6325c109c63a70dc47a9a8e32e762b44 as head.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=162972010-04-30T11:32:22ZYuri Tkachenko
<ul></ul><p>Can this issue be implemented into one of next releases?<br />I think it's very important, let it be optional, but it'll be a big plus to Redmine.</p>
<p>Sorry for my English :)</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=216192010-10-21T10:57:23ZNajam Alvi
<ul></ul><p>Is this implemented or not. We are looking for it desperately .</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=277632011-04-09T15:39:52ZEtienne Massip
<ul><li><strong>Category</strong> set to <i>Issues planning</i></li><li><strong>Target version</strong> set to <i>Unplanned backlogs</i></li></ul> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=282132011-04-21T10:50:56ZLuis Serrano Aranda
<ul></ul><p>+1</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=282192011-04-21T14:53:12ZTerence Mill
<ul></ul><p>+1</p>
<p>Especially we like the estimation accourancy profile thing. This will create a retroperspective on every version cycle and leaning curve for better estimations and make them more expert. In fact it should be possible to have them anonymous per feature/version or per personalized.<br />Great idea!</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=350972012-01-03T10:15:23ZMarcel Ritter
<ul></ul><p>+1</p>
<p>I also totally require this feature as well. But I would like an additional or different feature.</p>
<p>It would work the following:<br />For a Milestone (or Version in Redmine) I define Issues. I would specify the time estimate, an assignee and a unique priority number (e.g. added as a custom field). <br />Now, Redmine should be able to compute the start and end dates for each issue in the version, based on priorities (higher priority number first), issue depencies (relations, predecessors first) and assignees (issues can be done in parallel by different people).</p>
<p>I would also be willing contribute, since I'm a developer myself. (Unfortunatly I'm not into Ruby, but c++. Maybe I could help to write the algorithm, when having some of your expert-ruby-assistance. :) )</p>
<p>I really require this! :) Or was it already added meanwhiles? Answers and comments are highle appreciated!!</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=382742012-05-17T17:35:50ZRick Hunnicutt
<ul></ul><p>+1</p>
<p>This sounds amazing! Would love to see it implemented.</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=408192012-09-11T09:17:38ZAndy Ivanov
<ul></ul><p>+1</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=505542013-07-15T10:20:19ZBernd Worsch
<ul></ul><p>+1</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=506772013-07-19T19:49:03ZSantiago Burgues
<ul></ul><p>Definitely need this!! Currently we have to do our planning on MS Project, then add all the same tasks to Redmine using the dates info MS Project gave us.</p>
<p>Each time we need to move the start date of a task (and believe me, that happens a LOT, mainly when we work on our in-house projects on our free times) we have to manually change all the dates. Think of that when a project has 100+ tasks, it takes at least 2hs to update all the tasks...</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=538722013-12-17T06:34:55ZDavid Tremblay
<ul></ul><p>at least to be able to choose between due date or duration</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=561982014-05-07T14:24:06ZBrad Smith
<ul></ul><p>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 management tool I've ever used. It didn't even occur to me that you simply wouldn't be able to do it in Redmine. Lacking this basically prevents it from being usable by me, so I really hope this gets some attention soon. :(</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=561992014-05-07T16:13:40ZBrian Lindahl
<ul></ul><p>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.</p>
<p>Add the 'Custom Workflow' plug-in:<br /><a class="external" href="http://www.redmine.org/plugins/custom-workflows">http://www.redmine.org/plugins/custom-workflows</a></p>
<p>The Custom Workflow plug-in is extremely powerful and you can use it in many ways to customize Redmine to a pretty high level. It basically executes custom code before and after saving an issue. Create a new custom workflow as follows.</p>
<p>Description:<br />When <em>Start Date</em> or <em>Estimated Hours</em> changes, updates the issue <em>Due Date</em>. Saturdays and Sundays are skipped and and its assumed that there are 8 <em>Estimated Hours</em> per work day.</p>
<p>Code block (left side):</p>
<pre><code class="ruby syntaxhl"><span class="k">if</span> <span class="n">leaf?</span> <span class="o">&&</span> <span class="nb">self</span><span class="p">.</span><span class="nf">start_date</span> <span class="o">&&</span> <span class="nb">self</span><span class="p">.</span><span class="nf">estimated_hours</span>
<span class="k">if</span> <span class="n">start_date_changed?</span> <span class="o">||</span> <span class="n">estimated_hours_changed?</span>
<span class="nb">self</span><span class="p">.</span><span class="nf">due_date</span> <span class="o">=</span> <span class="nb">self</span><span class="p">.</span><span class="nf">start_date</span> <span class="o">+</span> <span class="p">(</span><span class="nb">self</span><span class="p">.</span><span class="nf">estimated_hours</span><span class="o">+</span><span class="mi">7</span><span class="p">)</span><span class="o">/</span><span class="mi">8</span>
<span class="n">non_work_days</span> <span class="o">=</span> <span class="mi">0</span>
<span class="p">(</span><span class="nb">self</span><span class="p">.</span><span class="nf">start_date</span><span class="o">..</span><span class="nb">self</span><span class="p">.</span><span class="nf">due_date</span><span class="p">).</span><span class="nf">each</span> <span class="k">do</span> <span class="o">|</span><span class="n">date</span><span class="o">|</span>
<span class="k">if</span> <span class="n">date</span><span class="p">.</span><span class="nf">wday</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="n">date</span><span class="p">.</span><span class="nf">wday</span> <span class="o">==</span> <span class="mi">6</span>
<span class="n">non_work_days</span> <span class="o">+=</span> <span class="mi">1</span>
<span class="k">end</span>
<span class="k">end</span>
<span class="nb">self</span><span class="p">.</span><span class="nf">due_date</span> <span class="o">+=</span> <span class="n">non_work_days</span> <span class="o">+</span> <span class="mi">2</span><span class="o">*</span><span class="p">(</span><span class="n">non_work_days</span><span class="o">/</span><span class="mi">7</span><span class="p">)</span>
<span class="k">end</span>
<span class="k">end</span>
</code></pre> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=786822017-05-18T15:48:52ZTxinto Vaz
<ul></ul><p>Brian Lindahl wrote:</p>
<blockquote>
<p>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.</p>
<p>Add the 'Custom Workflow' plug-in:<br />....</p>
</blockquote>
<p>FANTASTIC!!!</p> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=809062017-09-01T10:05:19Zholly chen
<ul></ul><p>Brian Lindahl wrote:</p>
<blockquote>
<p>[...]</p>
</blockquote>
<p>Thanks for Brian.<br />It's a big help.<br />But in some situations the due day will fall into weekends by your code.</p>
<p>I made a revision to this.<br />And in my redmine, the due date is the last day for the job, not the last+1<br />(Didn't use ruby before. If something is wrong, plz correct me.)</p>
<pre>
<code class="ruby syntaxhl"><span class="k">if</span> <span class="n">leaf?</span> <span class="o">&&</span> <span class="nb">self</span><span class="p">.</span><span class="nf">start_date</span> <span class="o">&&</span> <span class="nb">self</span><span class="p">.</span><span class="nf">estimated_hours</span>
<span class="k">if</span> <span class="n">start_date_changed?</span> <span class="o">||</span> <span class="n">estimated_hours_changed?</span>
<span class="n">work_days</span> <span class="o">=</span> <span class="p">((</span><span class="nb">self</span><span class="p">.</span><span class="nf">estimated_hours</span> <span class="o">+</span> <span class="mf">7.9</span><span class="p">)</span><span class="o">/</span><span class="mi">8</span><span class="p">).</span><span class="nf">to_i</span>
<span class="k">if</span> <span class="n">work_days</span> <span class="o"><=</span> <span class="mi">1</span>
<span class="nb">self</span><span class="p">.</span><span class="nf">due_date</span> <span class="o">=</span> <span class="nb">self</span><span class="p">.</span><span class="nf">start_date</span>
<span class="k">else</span> <span class="c1"># >= 2</span>
<span class="n">work_days</span> <span class="o">-=</span> <span class="mi">1</span> <span class="c1"># check from the next day.</span>
<span class="n">cur_date</span> <span class="o">=</span> <span class="nb">self</span><span class="p">.</span><span class="nf">start_date</span> <span class="o">+</span> <span class="mi">1</span> <span class="c1"># move to next day </span>
<span class="k">while</span> <span class="n">work_days</span> <span class="o">></span> <span class="mi">0</span> <span class="k">do</span>
<span class="k">if</span> <span class="n">cur_date</span><span class="p">.</span><span class="nf">wday</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="n">cur_date</span><span class="p">.</span><span class="nf">wday</span> <span class="o">==</span> <span class="mi">6</span> <span class="c1"># if next day is weekend</span>
<span class="n">cur_date</span> <span class="o">+=</span> <span class="mi">1</span>
<span class="k">else</span>
<span class="n">work_days</span> <span class="o">-=</span> <span class="mi">1</span>
<span class="nb">self</span><span class="p">.</span><span class="nf">due_date</span> <span class="o">=</span> <span class="n">cur_date</span>
<span class="k">if</span> <span class="n">work_days</span> <span class="o">></span> <span class="mi">0</span>
<span class="n">cur_date</span> <span class="o">+=</span> <span class="mi">1</span> <span class="c1"># move to next day</span>
<span class="k">end</span>
<span class="k">end</span>
<span class="k">end</span>
<span class="k">end</span>
<span class="k">end</span>
<span class="k">end</span>
</code><br /></pre> Redmine - Feature #1953: Due date calculation based on developer's estimationshttps://www.redmine.org/issues/1953?journal_id=906942019-03-11T17:51:04Zsnow windwaves
<ul></ul><p>There is also a plugin that will assign the due date based on versions and durations:<br /><a class="external" href="https://github.com/railsformers/redmine_issue_due_date">https://github.com/railsformers/redmine_issue_due_date</a></p>