Opened 14 years ago
Closed 14 years ago
#7839 closed enhancement (wontfix)
Remove # from parent ticket in ticket_custom
| Reported by: | Owned by: | Mark Ryan | |
|---|---|---|---|
| Priority: | normal | Component: | ChildTicketsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.11 |
Description
Neither SubticketsPlugin nor MasterTicketsPlugin use a "#" in the database value, only on display. This patch makes ChildTicketsPlugin consistent with those. It also makes it possible to import ChildTicketsPlugin parents with the TicketImportPlugin.
Attachments (1)
Change History (2)
Changed 14 years ago by
| Attachment: | nonumsign.patch added |
|---|
comment:1 Changed 14 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Hi Chris
The decision to use a '#' in the ticket-custom field was a deliberate one. Prior to trac 0.11(.3 - I think??), in my old firm I did indeed use something similar to the 'linkify' code used in MasterTicketsPlugin. By using the 'parent.type=wiki' setting in the ticket-custom field (available since 0.11), trac will take care of the whole 'linkifying' business and ensure future trac versions remain compatible.
From the point of view of the user it should make little difference as the idea is generally that the child ticket is created from the parent ticket directly using the 'create child' button (MasterTicketsPlugin operates vice-versa) and so the user should never have to actually enter a parent ticket number anyway.
It reduces significantly the code that needs to be maintained in this plugin (ie. the whole 'linkify' code you include in the #7840 patch is not needed).
I have no idea how many people are using this plugin (a few I would guess as I have had several comments asking me to continue support for it) but to implement this patch now would also break any existing ticket relationships they have already in their db. (ie. Existing '#n' values trip up when the plugin tries to treat these values directly as integers).
So.... unless a lot of people come forward and say this is something that is really required I would rather not implement these (#7839 and #7840) patches and will leave it to trac to manage the 'linkify' step on behalf of the plugin. Keep It Simple and all that... :-)
Thanks for the input/ideas and I'd like to know if there are any other compatibility issues with other plugins (ie. exactly how are people using the plugin!)
Thx Mark
Remove # from values in db