Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Not understanding Task types

web-app

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
Trevor Harmon
Replies (3)
helpful
0
not helpful

Every issue type is associated with field visibility scheme(s) for issue creation, edit, view and comments.
Edit the issue type (task, Administration -> Issue Type)  and set the visibility scheme for it (Administration -> Field Visibility Scheme).



Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Cool, that allows me to associate a Task with a Fix Version, which is what I really needed.

But I'm still confused about Tasks vs. Requirements. Anybody have an example of an issue that would best be described as a Requirement rather than a Task?

Thanks.


Trevor Harmon
· 1
Trevor Harmon
helpful
0
not helpful

Trevor,

Tasks, Requirements, and the like are just labels/categories.

You decide what labels/categories you need for your business.

A "Requirement" could be "Implement Billing Module". But then a bunch of Tasks can be linked to the "Requirement" that break down the work into smaller, manageable tasks that all must be done in order to meet the requirement.



Harvey Kandola
· 212
Harvey Kandola