Issue tracking for this project has moved to the BitBucket issue tracker.
Project URL is: http://bitbucket.org/jdbernard/personal-issue-tracker/
This commit is contained in:
Jonathan Bernard
@ -1,4 +0,0 @@
|
||||
Show full issue text with -v, --verbose
|
||||
=======================================
|
||||
|
||||
Print the full issue when passed the verbose option.
|
||||
@ -1,6 +0,0 @@
|
||||
Add the ability to change an issue's category
|
||||
=============================================
|
||||
|
||||
The -l/--list options lists issues, add a set of options to reclassify
|
||||
an issue from one category to another. The most common is CLOSED, but
|
||||
other categories should also be supported.
|
||||
@ -1,2 +0,0 @@
|
||||
Add the ability to re-prioritize an issue.
|
||||
==========================================
|
||||
@ -1,4 +0,0 @@
|
||||
Add the ability to enter new issues
|
||||
===================================
|
||||
|
||||
Implemented on 2010/02/17
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for LIST operation
|
||||
=================================
|
||||
|
||||
Add unit tests for listing issues with no filter.
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for the PRIORITY filter
|
||||
======================================
|
||||
|
||||
Add unit tests covering the priority selection criteria of the filter.
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for the CATEGORIES filter
|
||||
========================================
|
||||
|
||||
Add unit tests covering the categories filter criteria.
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for the PROJECTS filter
|
||||
======================================
|
||||
|
||||
Add unit tests covering the projects filter criteria.
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for the RECURSE filter
|
||||
=====================================
|
||||
|
||||
Add unit tests covering the subprojects filter criteria.
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for the VERBOSE option
|
||||
=====================================
|
||||
|
||||
Add unit tests covering the verbose option
|
||||
@ -1,5 +0,0 @@
|
||||
Add Apache Ivy to the build process.
|
||||
====================================
|
||||
|
||||
Add the neccesary structure to leverage an existing Ivy repository and to
|
||||
generate artifacts for a local repository.
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests for changing an issue's category.
|
||||
================================================
|
||||
|
||||
Test defined in test/com/jdbernard/pit/IssueTest.groovy
|
||||
@ -1,5 +0,0 @@
|
||||
Add unit tests for changing an issue's priority.
|
||||
================================================
|
||||
|
||||
|
||||
Test defined in test/com/jdbernard/pit/IssueTest.groovy
|
||||
@ -1,4 +0,0 @@
|
||||
Add unit tests covering Issue construction.
|
||||
===========================================
|
||||
|
||||
Test defined in test/com/jdbernard/pit/IssueTest.groovy
|
||||
@ -1,2 +0,0 @@
|
||||
Add unit tests covering Project construction.
|
||||
=============================================
|
||||
@ -1,8 +0,0 @@
|
||||
New Issue ID is off by one.
|
||||
===========================
|
||||
|
||||
Problem
|
||||
-------
|
||||
|
||||
When creating a new issue with the --new-issue option, the created issue has
|
||||
the same id as the most recent issue, as opposed to one more than.
|
||||
@ -1,26 +0,0 @@
|
||||
Creating a new issue bases the next id only on the filtered issues.
|
||||
===================================================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
|
||||
This represents a more systematic error. Filtering should be applied when
|
||||
viewing the data only, not when loading the data. It is possible that
|
||||
operations may need the full data to modify parts of it.
|
||||
|
||||
Solution
|
||||
--------
|
||||
|
||||
Remove filtering fromt he project and issue construction. Double check that
|
||||
filtering is correctly applied during all the access methods (eachIssue,
|
||||
eachProject, each)
|
||||
|
||||
Testing
|
||||
-------
|
||||
|
||||
Updated ProjectTest.testConstruction() to reflect changes.
|
||||
|
||||
Added a test to ProjectTest.testCreateNewIssue() that needs to count a closed
|
||||
task to correctly generate a new id.
|
||||
|
||||
TODO: Need to create filter tests.
|
||||
@ -1,12 +0,0 @@
|
||||
FileProject.delete() does not handle sub-projects correctly.
|
||||
============================================================
|
||||
|
||||
FileProject.delete() deletes the project directory if the directory is empty,
|
||||
but fails to do so if the directory is not empty.
|
||||
|
||||
Initial Recommendation
|
||||
----------------------
|
||||
|
||||
Loop through the issues and delete the files, loop through the projects and
|
||||
call Project.delete(). Alternatively, use File.deleteDir() rather than
|
||||
File.delete()
|
||||
@ -1,2 +0,0 @@
|
||||
Add unit tests for FileIssue.delete()
|
||||
=====================================
|
||||
@ -1,2 +0,0 @@
|
||||
Add unit tests for FileProject.delete()
|
||||
=======================================
|
||||
@ -1,2 +0,0 @@
|
||||
Fix Issue.toString() so that only the first letter is capitalized.
|
||||
==================================================================
|
||||
@ -1,33 +0,0 @@
|
||||
Divorce opened/closed status and classification.
|
||||
================================================
|
||||
|
||||
We need to track open/closed status and classification independantly.
|
||||
|
||||
Classification is one category, status should be another. Possible values for
|
||||
status:
|
||||
|
||||
* new
|
||||
* resolved
|
||||
* awaiting validation
|
||||
* rejected
|
||||
* reassigned
|
||||
|
||||
For the file-based issue implementation, the file format changes from
|
||||
``nnnnsp`` to ``nnnncsp`` where:
|
||||
|
||||
* ``nnnn`` still represents the bug number (no change)
|
||||
* ``c`` represents the *category* (used to be ``s`` the status):
|
||||
|
||||
* ``b``: Bug
|
||||
* ``f``: Feature
|
||||
* ``t``: Task
|
||||
|
||||
* ``s`` represents *status*, a new field:
|
||||
|
||||
* ``a``: Reassigned
|
||||
* ``j``: Rejected
|
||||
* ``n``: New
|
||||
* ``s``: Resolved
|
||||
* ``v``: Awaiting Validation
|
||||
* ``p`` still represents priority, ``0`` being the highest and ``9`` the
|
||||
lowest.
|
||||
@ -1,4 +0,0 @@
|
||||
Ignore hidden directories.
|
||||
==========================
|
||||
|
||||
Directories that are hidden (determined via File.isHidden()) should not be traversed.
|
||||
Reference in New Issue
Block a user