<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/outreach/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/outreach/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/outreach/feature-requests/</id><updated>2006-02-22T15:57:14Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Would like subversion support</title><link href="https://sourceforge.net/p/outreach/feature-requests/51/" rel="alternate"/><published>2006-02-22T15:57:14Z</published><updated>2006-02-22T15:57:14Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netdd446218d331590ece370cdf6d2c45a0043bdb07</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Would like subversion support&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>I can't pipe mail into mail_retrieve.pl</title><link href="https://sourceforge.net/p/outreach/feature-requests/50/" rel="alternate"/><published>2005-10-14T21:29:24Z</published><updated>2005-10-14T21:29:24Z</updated><author><name>Marc Beneteau</name><uri>https://sourceforge.net/u/mbeneteau/</uri></author><id>https://sourceforge.net8f3c25fd00385696534b05b75908ec7c872b506d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For some reason my host is not able to pipe mail into &lt;br /&gt;
mail_retrieve.pl by setting up an alias as described in &lt;br /&gt;
the documentation (they say they run Exim as root and &lt;br /&gt;
don't support aliases).  I am wondering how difficult it &lt;br /&gt;
would be to modify mail_retrieve.pl to read mail POP3 &lt;br /&gt;
and then run it from a cron.  Any ideas would be &lt;br /&gt;
appreciated.&lt;br /&gt;
&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Groups Hierarchy</title><link href="https://sourceforge.net/p/outreach/feature-requests/49/" rel="alternate"/><published>2004-11-18T00:40:10Z</published><updated>2004-11-18T00:40:10Z</updated><author><name>Frederic L. Washer</name><uri>https://sourceforge.net/u/ricwash/</uri></author><id>https://sourceforge.netda39f4cfe0fa276fc488fa168206c6cda7c81015</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I would like to see group hierarchy. We have about 200 employees &lt;br /&gt;
that will each be creating and maintaining projects. It would be &lt;br /&gt;
nice to have nested groups so rollup for supervisors, directors thru &lt;br /&gt;
the vp level was possible.&lt;/p&gt;
&lt;p&gt;-Ric&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Task Description in Gantt Chart</title><link href="https://sourceforge.net/p/outreach/feature-requests/48/" rel="alternate"/><published>2004-10-30T17:48:56Z</published><updated>2004-10-30T17:48:56Z</updated><author><name>affinitymc</name><uri>https://sourceforge.net/u/affinitymc/</uri></author><id>https://sourceforge.netf1f901eeeec2fcb1e462093810435b68fad4a5d8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I know there is a limitation with space, but would it be &lt;br /&gt;
possible to include a fuller description of each task in &lt;br /&gt;
the Gantt chart, as opposed to just the Task # ?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Brian Ward&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modification of create request page?</title><link href="https://sourceforge.net/p/outreach/feature-requests/47/" rel="alternate"/><published>2004-08-04T16:53:47Z</published><updated>2004-08-04T16:53:47Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net392d0871d7020f4c8e22cb2c9813b701a2bff691</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Is there a means to modify the "create request" page to &lt;br /&gt;
make it simpler? Want to dummy it down so that it can &lt;br /&gt;
be used by a pool of users that will only submit &lt;br /&gt;
requests. The plan is to implement OPT as a combination &lt;br /&gt;
trouble ticket and new feature request tool for a very &lt;br /&gt;
small in-house development team.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Task predecessors</title><link href="https://sourceforge.net/p/outreach/feature-requests/46/" rel="alternate"/><published>2004-01-09T19:10:36Z</published><updated>2004-01-09T19:10:36Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net63dd5f6884e9c5f131dc070af0f3d38df863bf8a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I think it would be very useful if I could specify one or &lt;br /&gt;
more predecessors for a task and set their relationships &lt;br /&gt;
(cannot start before the end of other task, must &lt;br /&gt;
complete before the end of task, etc.)&lt;/p&gt;
&lt;p&gt;I realize this might be difficult to implement, relatively, &lt;br /&gt;
however I think it would greatly enhance the usability of &lt;br /&gt;
the Outreach for bigger projects.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Task interface</title><link href="https://sourceforge.net/p/outreach/feature-requests/45/" rel="alternate"/><published>2003-10-30T04:21:25Z</published><updated>2003-10-30T04:21:25Z</updated><author><name>Mark Blevis</name><uri>https://sourceforge.net/u/mblevis/</uri></author><id>https://sourceforge.net48a582fb73775513d366f51792b4e648b4e0d3a3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I find that the task interface, the time management&lt;br /&gt;
component in particular, is very clunky. Frequently,&lt;br /&gt;
tasks end up being completed as a result of the number&lt;br /&gt;
of registered hours and not because of true completion.&lt;br /&gt;
Once a task is complete it feels like I have to jump&lt;br /&gt;
through hoops to assign more hours to reopen the task.&lt;br /&gt;
I would like the ability to allow task closure to take&lt;br /&gt;
place only if a task is flagged as closed and a&lt;br /&gt;
reconciliation of hours can be made after.  Also, it&lt;br /&gt;
should be easier to reopen tasks.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Task/sub-task relocation</title><link href="https://sourceforge.net/p/outreach/feature-requests/44/" rel="alternate"/><published>2003-10-30T04:18:04Z</published><updated>2003-10-30T04:18:04Z</updated><author><name>Mark Blevis</name><uri>https://sourceforge.net/u/mblevis/</uri></author><id>https://sourceforge.netf9c035f15055a1a8be7c7c85c83add38bc15b98c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It is not currently possible, or obvious that it is&lt;br /&gt;
possible, to move sub-tasks between parents.   The only&lt;br /&gt;
way to do this that I have found is to delete the&lt;br /&gt;
existing task and re-enter it in the correct location.&lt;br /&gt;
It would be helpful to have the ability to move tasks&lt;br /&gt;
around if required.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Requirements tracking</title><link href="https://sourceforge.net/p/outreach/feature-requests/43/" rel="alternate"/><published>2003-10-30T04:14:05Z</published><updated>2003-10-30T04:14:05Z</updated><author><name>Mark Blevis</name><uri>https://sourceforge.net/u/mblevis/</uri></author><id>https://sourceforge.netd6acf2e860371784de8f6644abb1874d46f7a20e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There are very few tools available to create RTM/scope&lt;br /&gt;
entries with reference fields from which validation and&lt;br /&gt;
results can be documented and reapplied.   This is true&lt;br /&gt;
for any projects: software, operational processes,&lt;br /&gt;
etc... Even more valuable is this capability built in&lt;br /&gt;
to a project management tool in which requirements and&lt;br /&gt;
solution delivery can be adequately tracked.  I would&lt;br /&gt;
love to see this feature in OPT.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Meeting calendar and agenda/minutes templates</title><link href="https://sourceforge.net/p/outreach/feature-requests/42/" rel="alternate"/><published>2003-10-30T04:10:59Z</published><updated>2003-10-30T04:10:59Z</updated><author><name>Mark Blevis</name><uri>https://sourceforge.net/u/mblevis/</uri></author><id>https://sourceforge.net0378833a19cc290c84ee9bd8a65bea7ff175f6dc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The calendar component would be far more powerful if&lt;br /&gt;
PMs had the ability to use calendar to schedule&lt;br /&gt;
meetings, etc... and meeting reports/minutes can be&lt;br /&gt;
spawned from meeting agendas using standard templates.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>