Resolves issues 0013, 0022, and 0019.

0013: Hide a new issue after a delay if does not match the viewing criteria.
0022: New 'Bugs' created are not correctly categorized.
0019: Add the ability to change the Issue text size.

issues/pit-swing/0013fs7.rst

@@ -1,2 +1,7 @@
 Hide a new issue after a delay if does not match the viewing criteria.
-======================================================================
+======================================================================
+
+Solution
+--------
+
+The issue is not hidden after a delay, it is immediately hidden.

issues/pit-swing/0019fn5.rst

@@ -1,24 +0,0 @@
-Add the ability to change the Issue text size.
-=====
-
-Description
------------
-
-Type a description of the feature here.
-
-Implementation Notes
---------------------
-
-Optionally, describe any specific implementation notes.
-
-Solution
---------
-
-How was the feature realized?
-
-Resolution
-----------
-
-Date Created:   YYYY-MM-DD
-Date Resolved:  YYYY-MM-DD
-Delivery:       ####

issues/pit-swing/0019fv5.rst

@@ -0,0 +1,28 @@
+Add the ability to change the Issue text size.
+==============================================
+
+Description
+-----------
+
+It would be good to be able to choose the size of the text for issue display.
+
+Implementation Notes
+--------------------
+
+This is a shared value between all project panels, so this needs to be on the
+enclosing PIT mvc, not the individual *ProjectPanel* mvcs. The ideal
+implementation is to bind the ``issueDetailTextArea.font`` property from the
+*ProjectPanel* view to the main mvc ``model.issueDetailFont``, but this fails
+and I cannot determine why. 
+
+Solution
+--------
+
+The ``ProjectPanelController.displayIssue`` method checks the value of
+``issueDetailTextArea.font`` against the main mvc ``model.issueDetailFont`` and
+updates it if it differs before actually displaying the issue selected.
+
+Resolution
+----------
+
+Delivery:       0019

issues/pit-swing/0020tn5.rst

@@ -4,7 +4,7 @@ The auto-generated pit-swing.groovy file needs to be renamed.
 Description
 -----------
 
-Currently, when
+Currently, when 
 
 Solution
 --------

issues/pit-swing/0021bn7.rst

@@ -0,0 +1,23 @@
+Icons not displaying in the project tree.
+=========================================
+
+Description
+-----------
+
+There should be icons in the list to the left to decorate it a bit.
+
+Implementation Notes
+--------------------
+
+
+Solution
+--------
+
+How was the bug fixed?
+
+Resolution
+----------
+
+Date Created:   2010-04-20
+Date Resolved:  YYYY-MM-DD
+Delivery:       0021

issues/pit-swing/0022bn3.rst

@@ -0,0 +1,35 @@
+New 'Bugs' created are not correctly categorized.
+=================================================
+
+Description
+-----------
+
+If the user clicks *New Issue* and does not manually select *Bug* from the drop-down
+list, but instead leaves the default *Bug* selected, the actual issue bypasses the
+template generation phase and gets its category defaulted to *Task*.
+
+Implementation Notes
+--------------------
+
+It looks like this is related to the default value of the category list in the 
+*New Task* dialog.
+
+Solution
+--------
+
+The values from the *NewIssueDialog* are publicly visible via fields on the
+model. The view has bound properties to update the model's fields whenever the
+appropriate gui field is updated. But when the dialog is shown initially, the
+view is reset programatically, not triggering the update to the model values.
+In the case of the first new issue since launching the program, the fields on
+the model are ``null`` or have their default initialized values. In subsequent
+issues, they hold whatever was there before. If the user never changed those
+values, they held their old values. The solution was to update the model as
+well as the view when showing the dialog.
+
+Resolution
+----------
+
+Date Created:   2010-04-20
+Date Resolved:  2010-04-20
+Delivery:       0022

issues/pit-swing/0022bs3.rst

@@ -0,0 +1,27 @@
+New 'Bugs' created are not correctly categorized.
+=================================================
+
+Description
+-----------
+
+If the user clicks *New Issue* and does not manually select *Bug* from the drop-down
+list, but instead leaves the default *Bug* selected, the actual issue bypasses the
+template generation phase and gets its category defaulted to *Task*.
+
+Implementation Notes
+--------------------
+
+It looks like this is related to the default value of the category list in the 
+*New Task* dialog.
+
+Solution
+--------
+
+How was the bug fixed?
+
+Resolution
+----------
+
+Date Created:   2010-04-20
+Date Resolved:  YYYY-MM-DD
+Delivery:       0022