Which plugins to use for advanced tickets field

16 views
Skip to first unread message

david

unread,
Dec 20, 2018, 9:36:24 AM12/20/18
to Trac Users
Hello,

I use trac since 10 years, (but without advanced worklow).

Now, I want advanced tickets field management.

But, I don't know which plugin to use.

It seems best are KeepInterfaceSimplePlugin and DynamicFieldsPlugin.

I want the more powerfull one.

I don't now for the moment all functions that I need.

What I know:

- hide some fields based on permissions, tciket type, ticket status, value of other custom fields.
- block actions of the workflow based on value of others fields ( and custom-fields).

Which one do you advise me?

Thanks.

David.

RjOllos

unread,
Dec 26, 2018, 5:21:59 PM12/26/18
to Trac Users
You are on the right track by focusing on those two plugins. They are likely the most complete and best maintained of the "ticket fields" plugins.

I suggest cloning your site and installing each plugin in a cloned instance, then trying to implement your rules with each plugin. The rules can get complex and the best way is to just give it a try. You may end up with feature requests for the plugins, so the sooner you can evaluate, the better.

- Ryan
 

David Bonnin

unread,
Dec 26, 2018, 6:15:09 PM12/26/18
to trac-...@googlegroups.com
Hello,

I've started with KeepInterfaceSimplePlugin.

I've a big problem to hide field when create a ticket: the status <none> don't work or I don't have the good syntax: 'none' "none" <none> '<none>' "<none>" ?
My workaround is to explicitly to list all other status to show the field..

I thinks, I will also try DynamicFieldsPlugin 

I use 15 plugins.. lol
nearly, no modifications on it.

Thanks Ryan for reply and for the job done for Trac.

An idea for the release 1.4?
For me, my biggest problem know is multi-trac.... 20 projects..
It need to be multiProject in the core ( 1 DB ).

David.

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+...@googlegroups.com.
To post to this group, send email to trac-...@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

RjOllos

unread,
Dec 27, 2018, 10:45:40 PM12/27/18
to Trac Users


On Wednesday, December 26, 2018 at 3:15:09 PM UTC-8, david wrote:
Hello,

I've started with KeepInterfaceSimplePlugin.

I've a big problem to hide field when create a ticket: the status <none> don't work or I don't have the good syntax: 'none' "none" <none> '<none>' "<none>" ?
My workaround is to explicitly to list all other status to show the field..

I'm guessing the plugin hasn't been updated for the ticket create action, introduced in Trac 1.2. I'd open a ticket for the issue with KIS plugin.
 
I thinks, I will also try DynamicFieldsPlugin 

I use 15 plugins.. lol
nearly, no modifications on it.

Thanks Ryan for reply and for the job done for Trac.

An idea for the release 1.4?

Soon, I hope. I haven't had much free time lately.
 
For me, my biggest problem know is multi-trac.... 20 projects..
It need to be multiProject in the core ( 1 DB ).

I agree it's needed, but it will be a substantial effort.
 
David.

Le mer. 26 déc. 2018 à 23:22, RjOllos <rjo...@gmail.com> a écrit :


On Thursday, December 20, 2018 at 6:36:24 AM UTC-8, david wrote:
Hello,

I use trac since 10 years, (but without advanced worklow).

Now, I want advanced tickets field management.

But, I don't know which plugin to use.

It seems best are KeepInterfaceSimplePlugin and DynamicFieldsPlugin.

I want the more powerfull one.

I don't now for the moment all functions that I need.

What I know:

- hide some fields based on permissions, tciket type, ticket status, value of other custom fields.
- block actions of the workflow based on value of others fields ( and custom-fields).

Which one do you advise me?

Thanks.

David.

You are on the right track by focusing on those two plugins. They are likely the most complete and best maintained of the "ticket fields" plugins.

I suggest cloning your site and installing each plugin in a cloned instance, then trying to implement your rules with each plugin. The rules can get complex and the best way is to just give it a try. You may end up with feature requests for the plugins, so the sooner you can evaluate, the better.

- Ryan
 

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages