We’ve been loving our Trac install at work, but we are still sanding down a few rough spots. \u00a0One particular spot that’s been bobbing up has been what happens when “new” tickets have an owner assigned. \u00a0I liked the ticket status being “new”, because it meant that I could easily look at my ticket list and see tickets that had been directly assigned to me that I hadn’t acknowledged yet by accepting them. \u00a0Someone else really disliked having to “accept” a ticket that was already assigned to him before he could move it to QA.<\/p>\n
I actually managed to create a solution for this using the\u00a0TicketConditionalCreationStatusPlugin<\/a>\u00a0from TracHacks. \u00a0This plugin allowed me to conditionally set the status of the ticket based on the contents of the “owner” field. \u00a0This was actually a pretty slick solution, but for various reasons it didn’t sit well with a lot of people.<\/p>\n The next idea we had was to prevent new tickets from being created with any owner besides the default value of “dev” (our dev team mailing list). \u00a0This solution had three main benefits – It worked the same for everyone; no one would ever have a “new” ticket assigned to them; and the “dev” alias was always associated with a new ticket, which has some value in relation to email notifications.<\/p>\n Easy enough, right? \u00a0Maybe it’s just me, but I could not find a good way to enforce this. \u00a0There’s no native ability to hide fields that aren’t drop-downs, and owner’s not a drop down by default. \u00a0It can be made a drop-down, but not in a manner which would allow it to be removed. \u00a0There are several owner-oriented plugins, but none of them differentiate between the “new ticket” screen and the “modify ticket” screen.<\/p>\n After a bit of fruitless experimentation I realized that I was overthinking it. \u00a0I made the following change:<\/p>\n et voila! \u00a0My default owner value is visible but immutable!<\/p>\n I know this isn’t a rock-solid solution, but in our environment (restricted corporate access) I’m not worried about evil-doers and griefers, I’m just wanting to remind people that they’re not supposed to change the value…<\/p>\n","protected":false},"excerpt":{"rendered":" We’ve been loving our Trac install at work, but we are still sanding down a few rough spots. \u00a0One particular spot that’s been bobbing up has been what happens when “new” tickets have an owner assigned. \u00a0I liked the ticket … Continue reading \r\n- <body py:match="body" py:attrs="select('@*')">\r\n+ <body onload='document.getElementById("field-owner").disabled = true;' py:match="body" py:attrs="select('@*')">\r\n<\/pre>\n