[Rt-commit] rt branch, 5.0-trunk, updated. rt-5.0.1-237-g8e5b21ec1b

[Jim Brandt]

The branch, 5.0-trunk has been updated
       via  8e5b21ec1bc4ce8007ddbf376a1644883006ff11 (commit)
      from  8d3acc48f1f0216cbd32b79a0fd5131fe21a2554 (commit)

Summary of changes:
 docs/UPGRADING-5.0 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

- Log -----------------------------------------------------------------
commit 8e5b21ec1bc4ce8007ddbf376a1644883006ff11
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Apr 22 09:37:16 2021 -0400

    Document how to show Final Priority if desired

diff --git a/docs/UPGRADING-5.0 b/docs/UPGRADING-5.0
index 4aa6b92e4d..5abf895152 100644
--- a/docs/UPGRADING-5.0
+++ b/docs/UPGRADING-5.0
@@ -187,6 +187,20 @@ If you previously used numbers for priority and would like to continue
 to do so, you can set the new C<$EnablePriorityAsString> option to false.
 That will disable the new string-based display.
 
+We also now hide Final Priority by default, but if you previously used it
+and would like to continue to do so, you can add this to the Custom CSS
+section on the Theme editor:
+
+    .FinalPriority, .TicketFinalPriority {
+        display: flex;
+    }
+    .priority div.value .current-value {
+        visibility: visible;
+    }
+    .priority div.value .current-value .FinalPriority {
+        display: inline;
+    }
+
 If you would like to now use strings for priority like Low, Medium, High,
 check the new C<%PriorityAsString> configuration option. RT provides a simple
 default setting that may be sufficient. Set new values if you would like

-----------------------------------------------------------------------