Some more Noob questions Just trying to fine tune the ticketing system for my own needs.
1 - Looks like there is TH1 script to determine what values can be chosen from the ticketing webgui for filling certain fields, like status, priority, severity, etc. I want to sort my ticket reports based on severity, priority. I can see how to update the SQL in the report definition to have the fields I want, ordered and colored however I want. Great. However, it looks to me like a collating sequence is really needed to make ordering make sense… "Important" needs to be at the top of the list, not “cosmetic”, for example. Ideally the list would sort based on the same collating order that is shown in the actual TH1 script used to fill the GUI top to bottom. But somehow I don’t think that is possible without a collating sequence so that the SQL command of the ticket report will be able to do what it needs to do. It seems to me that I would need to manually add a collating sequence to sqlite and then use it in the report. The bummer is that I am guessing this object would not get cloned or sync’d to other repos, but please correct me if I’m wrong. Or maybe there is a better way to handle this task to get the ticket list sorted in an order that makes sense to me..not alphabetical. I can of course put numbers into the values for severity and priority, which would then sort things appropriately, but with ugly numbers showing up all over the place, including in the ticket reports. 2 - When I changed the SQL for a ticketing report, even just slightly like remove a field, the report now has a big blank white space in between each row. Is this a bug or something I’m doing wrong? Possibly this is related to the AS ‘_comments’ part of the SQL..that is perhaps different then the actual default report is, I’m not sure. Just trying to understand. No actual comments are showing up in the report in that white space…so maybe that is what is confusing me, I notice when I don’t have any _<fields> then no white space. Comments? 3 - I notice when I hover the mouse over the header row of the ticket list, it changes to a finger cursor..implying that there may be some functionality for clicking on the header of the column, but nothing seems to happen. Any comment about that? 4 - this is actually more related to the timeline, but my timeline always shows ‘Ticket’.title, on the timeline for each ticket…rather then the actual text of the title, it shows this SQL syntax instead. I tried to adjust the definition under timeline settings, to Ticket.title, which just shows that.. is something broken in Fossil or am I doing something wrong? How can I get the actual ticket title and/or comments into the timeline? 5 - After having created a hundred tickets or so, I realized that I would like to have a certain tag in the sub-system field. I see that I need to go add them with TH1, fine. however, what is the ok way to go back to add those tags to all my hundred tickets. Will it be ok to use a SQL statement to manually set the value of that field enmass to a bunch of tickets, or will that in any way confuse some fossil artifact somewhere? Is ticket data stored anywhere besides in the ticket table which would get confused if I manually change those values directly with SQL? same goes if I want to go tweak a bunch of the title fields where i actually put my own all caps word in each title for the sub-system (before I realized there was a dedicated field for it, since its not on the NEW ticket page (yet). 6 - I notice that when I create a new ticket, the combo box for priority shows the first item on the list. If I don’t change it…then null is stored in the DB rather then that value. Seems like these combo boxes should default to what is going to be stored..if NULL is the default, then show blank unless I manually select a value. Or is there a way to configure things so that they will be defaulted to a particular value rather then displaying something the user may assume is going to be stored, but isn’t going to be stored unless they change the combo box explicity. Am I making sense? enough for now... _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
