ticket-custom fields are not getting deleted from the view

[anonymous]

Hi,

I am trying to remove few fields from ticket-custom in trac.ini file but it is not getting removed from the view. When I try to remove trac web page is throwing an error saying i need to upgrade the env but when I do that trac.ini is not reflecting the old changes. When I edit it manually and try removing the fields it is repeating the same issue.

I think the entries are cached somewhere in the db and unable to remove them even trac.ini is being changed.

I see multiple files like sqlite.29.1391033055.bak in the db folder which has trac.db file. Can I delete that to remove the cached entries?

My team is waiting on me to start creating tickets as they are burdened using the excel sheets.

Please advise me on how to resolve this issue.

[Ryan J Ollos]

Which plugin are you reporting this issue for?

[anonymous]

I am not sure to which plugin it relates to.

[Ryan J Ollos]

Which plugins do you have installed?

[anonymous]

And what is the name of the ticket field you are trying to remove?

[anonymous]

I have installed the below plugins :

AccountLDAP-0.32-py2.7.egg
TracAccountManager-0.4.3-py2.7.egg
TracMindMapMacro-0.4-py2.7.egg
AdvancedTicketWorkflowPlugin-0.11dev-py2.7.egg
TracAdvParseArgsPlugin-0.4-py2.7.egg
TracMyPagePlugin-0.11.1.1-py2.7.egg
CodeExampleMacro-1.0-py2.7.egg
Tracchildtickettreemacro-1.0.1-py2.7.egg
TracNav-4.1-py2.5.egg
Genshi-0.6-py2.7.egg
TracCodeReview-2.2dev-py2.7.egg
TracStats-0.5-py2.7.egg
graphviz-0.7.5dev-py2.7.egg
TracCodeReviewer-0.0.2-py2.7.egg
TracSubcomponents-1.2.0-py2.7.egg
HudsonTrac-0.5-py2.7.egg
TracExtractUrl-0.2.7030-py2.6.egg
TracUserManagerPlugin-0.5dev-py2.7.egg
LdapPlugin-0.7.0dev-py2.7.egg
TracGenericClass-1.1.5-py2.7.egg
TracWorkflowAdmin-0.12.0.2-py2.7.egg
ProjectPlan-1.0.2-py2.7.egg
TracGenericWorkflow-1.0.4-py2.7.egg
TracXMLRPC-1.1.2-py2.7.egg
SqlQuery-0.1-py2.7.egg
trac_GenshiMacro-0.1-py2.7.egg
WikiTableMacro-0.2dev-py2.7.egg
STractistics-0.5.0b-py2.7.egg
TracIncludeMacro-3.0.0dev-py2.7.egg
TestManager-1.6.1-py2.7.egg
TracMasterTickets-3.0.5dev-py2.7.egg

Our company needs some additional fields to the ticket so I was trying to remove few previous entries which were added as a sample. I am trying to remove fields like blocked by, blocking, Test Plan, Test Case, cc, Keywords.

I saw some plugin called customticket plugin which can be installed from the admin tab. But I am not sure of how to install the plugin. As I see a tab named plugins in the trac view page. I tried installing by browsing the setup.py and installing it but setup.py files are loaded into the plugins directory on the server which only contain the egg files. The new download of setup.py is bringing the trac server down and is coming up after i remove those files. So please advise me on this..

[Ryan J Ollos]

Replying to anonymous:

Our company needs some additional fields to the ticket so I was trying to remove few previous entries which were added as a sample. I am trying to remove fields like blocked by, blocking, Test Plan, Test Case, cc, Keywords.

The fields are added by MasterTicketsPlugin whenever they are not present: masterticketsplugin/trunk/mastertickets/api.py@12940:101-110#L83​. If you aren't using blocked by and blocking, do you need to have MasterTicketsPlugin installed at all? If you don't need the plugin, you can disable it from the web admin panel. I am not sure if Test Plan and Test Case are similarly added in an IEnvironmentSetupParticipant method by a plugin, so we'll have to see what happens after dealing with MasterTicketsPlugin.

CC and Keywords are built-in fields.

I saw some plugin called customticket plugin which can be installed from the admin tab. But I am not sure of how to install the plugin. As I see a tab named plugins in the trac view page. I tried installing by browsing the setup.py and installing it but setup.py files are loaded into the plugins directory on the server which only contain the egg files. The new download of setup.py is bringing the trac server down and is coming up after i remove those files. So please advise me on this..

You'll want to read: TracPlugins. Plugins installed by uploading through the web admin panel must be an egg or single-file plugin. You'll never want to upload a setup.py.

[anonymous]

Thank You very much for all the information and clarification.

Test Plan and Test case are also appearing because of the Test Manager plugin.

I would need some help in getting the egg for CustomfieldAdmin plugin. I could not find the egg to upload through web.

I saw in a forum with egg name : TracCustomFieldAdmin-0.2.8_r11597-py2.7.egg so can I use it and do easy_intall TracCustomFieldAdmin-0.2.8_r11597-py2.7.egg ?

For installing ti do I need to do it in the plugins folder of my environment or should I do at the root level. Please let me know I read multiple things but couldn't get few clarifications.

[Ryan J Ollos]

Replying to anonymous:

Thank You very much for all the information and clarification.

Test Plan and Test case are also appearing because of the Test Manager plugin.

Have you now disabled the MasterTicketsPlugin? Have you tested the behavior again after deleting the definitions in [ticket-custom]? It's possible that the Test case manager plugin will no re-add them once removed.

I would need some help in getting the egg for CustomfieldAdmin plugin. I could not find the egg to upload through web.

I saw in a forum with egg name : TracCustomFieldAdmin-0.2.8_r11597-py2.7.egg so can I use it and do easy_intall TracCustomFieldAdmin-0.2.8_r11597-py2.7.egg ?

For installing ti do I need to do it in the plugins folder of my environment or should I do at the root level. Please let me know I read multiple things but couldn't get few clarifications.

The TracPlugins page describes how to create an egg. However, even the CustomFieldAdminPlugin shows the specific command to install from the command line. So as long as you have shell access on your server, you can install as described at CustomFieldAdminPlugin#easy_install, and not worry about installing the egg through web admin.

I am happy to help with your questions, but do please make sure to familiarize yourself with the TracPlugins documentation and the CustomFieldAdminPlugin documentation. It will take you less than 20 minutes to read those pages.

[Ryan J Ollos]

Replying to anonymous:

For installing ti do I need to do it in the plugins folder of my environment or should I do at the root level. Please let me know I read multiple things but couldn't get few clarifications.

Either of these approaches will work. Often, admins will install to the site-packages directory if running multiple Trac instances in the Python environment (so that they don't have copy the file to each environment's plugins directory), and in particular if it is a Python virtual environment dedicated to the Trac instance.

[Ryan J Ollos]

I've re-read the ticket, so I'll just add a few additional pointers.

Replying to anonymous:

I am trying to remove few fields from ticket-custom in trac.ini file but it is not getting removed from the view. When I try to remove trac web page is throwing an error saying i need to upgrade the env

It doesn't matter much at this point, but I'm not sure at all what you mean when you say try to remove trac web page.

I see multiple files like sqlite.29.1391033055.bak in the db folder which has trac.db file. Can I delete that to remove the cached entries?

It is best to leave those. They have nothing to do with your issue.

Also, you've mentioned wanting to use the CustomFieldAdminPlugin. The plugin will only allow you to edit the [ticket-custom] section of the trac.ini file through the web interface. It won't specifically help in any way with this issue you are experiencing.

At this point, presumably you've disabled or removed MasterTicketsPlugin and the blocking and blocked by fields are no longer present. Now, as mentioned, please try removing Test Plan and Test Case from [ticket-custom]. If you aren't prompted to upgrade your installation, then they are not re-added by the plugin. If they are re-added, then we need to figure out which plugin is re-adding them. Your best bet is to disable TestManagerForTracPlugin, but some experimentation will be necessary.

So far I've suggested getting rid of the fields by disabling the plugin that adds them. If you don't want the fields in your ticket form, but do want to use the plugin, then the issue will need to be addressed by the plugin author, so please follow-up with a ticket for the specific plugin that adds the fields.

I'm closing this now, but please feel free to follow-up if you have additional trouble. In the future, please consider using the ​t:MailingList first for issues like this, before opening a ticket.