Per-project ticket.default_* settings

[endquote]

In our projects we like to set the default_cc on tickets to people in the project, the default_milestone to the next mulestone, etc. When using SMPP, we'd have to set those environment-wide. It would be nice if a project included settings for these things.

[anonymous]

If a project had settings default_cc and default_milestone (e.g. new columns in the db structure of table smp_project), how would you use them? Do you have another plugin for that or something?

[anonymous]

or do you expect this plugin to insert the values in the fields on a new ticket form? Just for understanding what you want...

[endquote]

I would expect to set default_cc and default_milestone per-project in some way (via the admin panel or trac.ini), and have those values appear by default in the new ticket form. Just the same as the non-SMPP behavior, but with different values per project.

We use default_cc in order to make sure some people (QA, managers, dev leads) get notified on every ticket automatically, but those people are different according to the project.

[falkb]

Sounds like a useful feature I could have well used here also. I think I'm going to implement that as soon as I find time again. Thanks for the suggestion.

[falkb]

I saw there's also TracTicketTemplatePlugin but that is not able to define default entries for custom ticket-fields for each project. Currently, I'm brooding over if it's better to hack that plugin or rather extend my own plugin. At the moment I tend to think if we're sure it's only default_cc and default_milestone (and maybe default_version), it'll be better to add the functionality to SimpleMultiProjectPlugin.

[endquote]

Glad to hear you're still thinking about it. I could certainly still use it. Let me know if I can help test.

[falkb]

I also have a custom-field 'tester' which could get a project-wise 'default_tester' setting. This holds me back from simply adding 'default_cc' and 'default_milestone' because it looks like we need a more generic approach.

Probably a db-table 'smp_ticketfielddefaults' consisting of 3 columns 'project', 'field_name' and 'default_value'.

The web-interface page for the configuration could be list of project links, and each link leads to a new page where a table with 2 columns 'field name'+'default value' is there for editing.

[endquote]

That makes sense to me -- perhaps if I had an easy ability to make custom fields, I'd come up with interesting ways to use them.

[nenad@…]

Being able to push per-project field default values would be excellent.

Probably a db-table 'smp_ticketfielddefaults' consisting of 3 columns 'project', 'field_name' and 'default_value'.

This is probably way to go, but at least setting of "default_cc" and "default_milestone" using other (non-generic) approach would be better than nothing :)