db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: Jira field definitions
Date Wed, 01 Jul 2009 13:20:43 GMT
Rick Hillegas wrote:
> Hi Dag,
> Once again, thanks for overhauling our JIRA form. I just want to note 
> what I think is a welcome divergence from last week's version of your 
> proposal. I thought that your proposal called for paring back the 
> legal values of the Issue Type field to Bug, Improvement, Task, and 
> Sub-task. I see that you have eliminated the last value as well. So 
> now there are only 3 values: Bug, Improvement, and Task. I think 
> that's ok because Sub-tasks can be flagged by linking issues together.

For clarity, we can still create sub-tasks. What has changed, I guess, 
is that it can't be done from the main "Create new issue" link any more.
For existing issues you can just click "Create sub-task" though.

> Thanks,
> -Rick
> Dag H. Wanvik wrote:
>> Another update, folks, the next phase has been completed, Derby now
>> uses its own JIRA Issue Type Scheme, which means that the "Wish", "New
>> Feature", and "Test" issue types are gone. Old "Test" issues have been
>> converted to "Bug" or "Improvement" on a case by case basis, "Wish"
>> and "New Feature" have been moved to "Improvement".
>> Of course I forgot to unclick the "Send email" check-box in one case
>> so you have been properly spammed again; sorry!
>> Dag

View raw message