Not understanding Task types
I'm not understanding the Task issue type. For example, let's say version 2.0 of my project will include some fancy new math routines, but I can't write them all on my own, so I want to create an issue described as "Find a third-party library for math routines". I would consider this a task, since it's not a new feature or bug fix or anything like that. However, when I choose the Task type, most of the fields disappear! I can't set the Fixed Version of the task to 2.0 (to declare that it must be completed as part of the 2.0 release). I can't even give it a priority or severity. Why is this?
I see that there is a similar issue type called "Requirement". This does allow all fields to be entered. So in the example above, should I use a Requirement type instead of Task?
If so, what exactly is the purpose of Task types? Without being able to associate it with a version, it seems kind of pointless. Maybe if I could see some examples of Task types vs. Requirement types, I would understand. Thanks.
Trevor Harmon
· 1 |
|
Sunday, August 22, 2010, 11:51:08 PM |