Changes between Version 10 and Version 11 of TracUserSelectFieldPlugin

Timestamp:

Oct 4, 2021, 11:50:42 AM (18 months ago)

Author:

figaro

Comment:

Cosmetic changes and license update

TracUserSelectFieldPlugin

@@ -4 +4 @@
 
 {{{#!box info
-This plugin uses a 'patch-style' implementation rather than the normal one. It may cause unknown influence to other plugins that depends on {{{TicketSystem.custom_fields}}} and {{{ConfigurableTicketWorkflow._to_users}}}.
+This plugin uses a 'patch-style' implementation rather than according to standard Trac's guidelines. It may adversely affect other plugins that depend on {{{TicketSystem.custom_fields}}} and {{{ConfigurableTicketWorkflow._to_users}}}.
 
 Not recommended in production use. Use at your own risks.
@@ -13 +13 @@
 This plugin enables a field to select a specific user according to configuration. This field can later be used in workflow.
 
-1. Create a select Custom Field:
+1. Create a select Custom Field in your `trac.ini` file:
 
  {{{#!ini
@@ -28 +28 @@
  [[Image(1.png, border=2)]]
 
-2. Use this user in workflow:
+2. Use this user in the workflow configuration section in your `trac.ini` file:
  {{{#!ini
 pj0102_test = PJ01 -> PJ02
@@ -40 +40 @@
  [[Image(2.png, border=2)]]
 
-Notice: Function 2 can also be achieved by AdvancedTicketWorkflowPlugin's set_owner_to_field operation
+'''Note''': Function 2 can also be achieved by AdvancedTicketWorkflowPlugin's set_owner_to_field operation:
 {{{#!ini
 [ticket]
@@ -73 +73 @@
 General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
 
-Special:
-UserSelectFieldPlugin should be activated, but PatchedTicketSystem is NOT supposed to be activated!
+'''Note''': UserSelectFieldPlugin should be activated, but PatchedTicketSystem is NOT supposed to be activated!
 
 Make the following changes in your `trac.ini` file: