Flyspray - The bug killer!

“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra

This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!

Do not issue bugs reports against versions earlier than 0.9.9.5

Security problem? Check the security section.

Tasklist

FS#287 - Status list is not editable

Attached to Project: Flyspray - The bug killer!
Opened by John Jacob (elros) - Monday, 28 June 2004, 22:22 GMT+1
Last edited by Tony Collins (knigits) - Saturday, 28 August 2004, 09:32 GMT+1
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To Florian Schmitz (Floele)
Operating System All
Severity Low
Priority Low
Reported Version 0.9.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The list of choices for Task Types, Resolutions, and Categories is editable through the user interface, but the list for Status is not. How about making Status editable? Severity might fall into the same category.

This task depends upon

Closed by  Florian Schmitz (Floele)
Friday, 06 January 2006, 23:18 GMT+1
Reason for closing:  Implemented in devel
Additional comments about closing:  rev 573
Comment by Tony Collins (knigits) - Wednesday, 21 July 2004, 03:19 GMT+1

Certainly possible. It was done this way to allow for translations, but could be changed. I’ll think about it. The Severity list will not be changed.

Comment by Sebastian Sjoholm (ssjoholm) - Friday, 11 February 2005, 13:54 GMT+1

Good idea, I support it.

Comment by Mac Newbold (macnewbold) - Friday, 20 May 2005, 22:07 GMT+1

I think this would be extremely helpful, since status depends a lot on your development process, which varies from place to place. This bug could also resolve  FS#296  I think too, regarding a Released status.

Is there a fundamental reason why severity and priority lists cannot editable? (I ask out of curiosity and because it would help us I think.)

Comment by Mac Newbold (macnewbold) - Friday, 20 May 2005, 22:08 GMT+1

Correction: I meant  FS#496  above.

Comment by Mac Newbold (macnewbold) - Friday, 27 May 2005, 22:51 GMT+1

Another idea: The tables in the translations could be used as the default status list, to initialize the global status list, then anyone wanting to edit it could do so. I wonder if the other default entries in global lists are translated or not. *goes to look*

Comment by Rupert Hawkes (dweezil) - Wednesday, 12 October 2005, 21:31 GMT+1

PLEASE! The status list needs to be editable - my coders want “coding” as an option. The closest to this is “researching” which is NOT the same thing.

Comment by Mac Newbold (macnewbold) - Friday, 23 December 2005, 20:04 GMT+1

I would really like to see this in 0.9.9 - I think it would be very valuable. And it doesn’t seem any harder than the editable version lists and resolution lists.

Comment by Tony Collins (knigits) - Friday, 23 December 2005, 22:09 GMT+1

We could fairly easily make it editable, but the tasklist would then lose the ‘all open tasks’ search.

Comment by Florian Schmitz (Floele) - Friday, 23 December 2005, 22:29 GMT+1

Not necessarily - see Mac’s comment for  FS#276 

Loading...