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.




Priority and Severity

web-app

I used to do QA work in a large development shop. We used DDTS for incident tracking.

One thing that was useful about DDTS was that you could track both priority and sevity of a bug. We used to evaluate our bug queue every week and modify priorities. Our high priority list usually contained both low and high severity issues.

 

I'd like to see Gemini have both a priority and a severity setting

 

You priority setting is actually the severity of the issue.  Prioity should indicate when a bug gets attention, not how bad the bug is. Severity indicates how bad the bug is.

Show stopper indicates a big bad bug like a crash. But if it takes an very obscure combination of button pushes to cause the crash this problem may have a low priority. This would be High severity + low priority.

If you misspelled the name of your application on the login window this would be low severity but high priority.

Make sense?

 
nickh
· 1 		nickh
Tuesday, February 28, 2006, 11:02:21 PM
Replies (10)
helpful
0
not helpful

Makes sense.

Do you think this could be achieved with a combination of custom fields and localisation (which would allow you to change screen labels/text)?

Or do you think severity and priority should be standard features for all to have?
Harvey Kandola
· 212 		Harvey Kandola
Thursday, March 2, 2006, 12:49:19 PM
helpful
0
not helpful

Standard Feature for all to have.  Or give the user the option for what he would like it to be.   But as for me, this makes sense.
irperez
· 1 		irperez
Wednesday, March 29, 2006, 9:05:19 PM
helpful
0
not helpful

I agree - in practice this is an important distinction, and would be good to have standard, out of the box.

It's 2 aspects of work:
   - Where do we allocate our internal work resources next?
   - What is the impact of the bug / change-request / task on the external client (user/customer)?

On the other hand, if you're a smaller shop and don't separate these two, then Priority (as noted earlier - not really used) could be configured out (not shown).   Too many fields make for "noise". 

One of the consistent comments I hear about Gemini (as people look at bigger, big-bang, enterprise level tracking and reporting systems which we never seem to get - always something else you can want in them) - is that it's easy, quick.  Ask for a project, and 10 minutes you can be up and running.  No, you can't do all the fancy stuff you want with custom data;  No, you won't have nice, hyperlinked bar/pie chart reports out of the box.  Deal with it; get to work! grin
yarkot
· 1 		yarkot
Tuesday, April 4, 2006, 4:54:10 PM
helpful
0
not helpful

I would also like to see this as a standard feature.  In my own experience, I have always tracked these attributes separately and, even in small shops, the distinction can be very valuable.
GaryG
· 1 		GaryG
Friday, May 19, 2006, 10:36:17 PM
helpful
0
not helpful

I will like to see this feature standard as well. We are using UDF for some of our projects within Gemini but the problem is that UDF are not available in the filter section of the issues and therefore are not very usable.
Ankur
· 1 		Ankur
Tuesday, March 4, 2008, 8:42:21 PM
helpful
0
not helpful

Done for 3.0.
Harvey Kandola
· 212 		Harvey Kandola
Sunday, March 9, 2008, 11:47:06 PM
helpful
0
not helpful

When's 3.0 releasing?
Ankur
· 1 		Ankur
Monday, March 10, 2008, 3:30:10 AM
helpful
0
not helpful

[quote user="Ankur"]When's 3.0 releasing?[/quote]

I'd like to know too. According to http://gemini.countersoft.com/Issues.aspx?m=1&c=2&v=33 it might take quite some time until it's ready.
mbischoff
· 1 		mbischoff
Monday, March 10, 2008, 10:57:30 AM
helpful
0
not helpful

Online beta this week.

We are working flat out to ship a downloadable ZIP file of the beta 1 this week as well (with updated web services).

See attached screenshot (note Issue Severity field, RSS issues feed support, customisable issue status/workflow). 


Harvey Kandola
· 212 		Harvey Kandola
Monday, March 10, 2008, 1:16:11 PM
helpful
0
not helpful

Thanks for the update!
mbischoff
· 1 		mbischoff
Monday, March 10, 2008, 1:58:25 PM