<?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/bugtracker/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/bugtracker/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/bugtracker/feature-requests/</id><updated>2009-08-12T20:16:39Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>JSR Portlets</title><link href="https://sourceforge.net/p/bugtracker/feature-requests/4/" rel="alternate"/><published>2009-08-12T20:16:39Z</published><updated>2009-08-12T20:16:39Z</updated><author><name>RecentCoin</name><uri>https://sourceforge.net/u/midirr/</uri></author><id>https://sourceforge.net576867e91ed460c9b924c96d338cefaedcdf91a8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Have you considered releasing this as portlets?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Allow emails to contain "last updated by"</title><link href="https://sourceforge.net/p/bugtracker/feature-requests/3/" rel="alternate"/><published>2008-07-30T14:45:13Z</published><updated>2008-07-30T14:45:13Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net29341869340c722eeaeb5d4ade8e1ff11bc670c1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The current list of variables to chose from with email subjects is:-&lt;/p&gt;
&lt;p&gt;$THING$&lt;br /&gt;
$BUGID$&lt;br /&gt;
$ACTION$ - added or changed&lt;br /&gt;
$SHORTDESC$&lt;br /&gt;
$PROJECT$&lt;br /&gt;
$CATEGORY$&lt;br /&gt;
$ORGANIZATION$&lt;br /&gt;
$PRIORITY$&lt;br /&gt;
$STATUS$&lt;br /&gt;
$TRACKINGID$&lt;/p&gt;
&lt;p&gt;However, it would be awesome if there was also a "last submitted by" variable.&lt;/p&gt;
&lt;p&gt;(We have a tester who's REALLY annoying... being able to apply a mail filter on his name would be awesome).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Search for a Bug</title><link href="https://sourceforge.net/p/bugtracker/feature-requests/2/" rel="alternate"/><published>2001-06-19T13:37:14Z</published><updated>2001-06-19T13:37:14Z</updated><author><name>Michael Greifeneder</name><uri>https://sourceforge.net/u/mikegremi/</uri></author><id>https://sourceforge.net1a368f13ec1615733eaf115645dd8c92cafb2568</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A great thing would be if the solutions are stored in &lt;br /&gt;
the database and there&lt;br /&gt;
is a form for searching within the bugdatabase and get &lt;br /&gt;
the solution for the found bugs.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Bug History</title><link href="https://sourceforge.net/p/bugtracker/feature-requests/1/" rel="alternate"/><published>2001-06-19T13:36:14Z</published><updated>2001-06-19T13:36:14Z</updated><author><name>Michael Greifeneder</name><uri>https://sourceforge.net/u/mikegremi/</uri></author><id>https://sourceforge.net31b3238a885cc6cdb29dad76d70e1ae771ee7b00</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Each Bug should get a Bug-History where is stored who &lt;br /&gt;
redirects the bug,&lt;br /&gt;
adds a comment, changes a status and when he did it.&lt;/p&gt;
&lt;p&gt;Maybe like that&lt;/p&gt;
&lt;p&gt;Bug-headers&lt;br /&gt;
like id, description,..&lt;br /&gt;
bug-history&lt;br /&gt;
step 1: new Status=open, user=tester, comment='i &lt;br /&gt;
found the bug,...'&lt;br /&gt;
step 2: new Status=open, user=project-admin, &lt;br /&gt;
comment='developer has to fix&lt;br /&gt;
it'&lt;br /&gt;
step 3: new Status=fixed, user=developer, comment='i &lt;br /&gt;
have changed code'&lt;br /&gt;
step 4: new Status=open, user=tester, comment='can't &lt;br /&gt;
verified'&lt;br /&gt;
step 5: new Status=fixed, user=developer, &lt;br /&gt;
comment='you must get it&lt;br /&gt;
there...'&lt;br /&gt;
step 6: new Status=closed, user=tester, &lt;br /&gt;
comment='FIXED in Version x.x'&lt;/p&gt;
&lt;p&gt;A bug should always have an 'active person', who has &lt;br /&gt;
to act.&lt;br /&gt;
The action can be redirect the bug to another person, &lt;br /&gt;
fix the bug or close&lt;br /&gt;
it(tester). &lt;/p&gt;&lt;/div&gt;</summary></entry></feed>