/
Priority VS Order terms

Priority VS Order terms

Owned by Alex
Last updated: Jun 08, 2020

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/642e052b0a65d98c#

In-Portal has Priority column in tables, which data is displayed also on Front-end. This allows to position data in any order, no matter what sorting user has specified. I personally like Priority term, but according to Dmitry's input about user experience it seems, that "Order" term would be more appropriate. 

As a temporary measure in http://qa.in-portal.org/rINP12216 (2009 year) we changed translation of "la_col_Priority" and "la_fld_Priority" phrases to "Order" to solve that problem. Later in http://qa.in-portal.org/rINP14853 (2011 year) the "la_fld_Order" phrase was added.

Now, when I really need to have column/form field named "Priority" I see "Order" text instead. If "Order" term is no longer needed, then I propose to revert that change. If it's still needed, then appropriate "la_col_Order" and "la_fld_Order" phrases should be added and used, when appropriate.

Solution

  1. inspect places where "la_fld_Priority" phrase is used (either name is mentioned directly as-is or indirectly by using "Priority" field in "inp_edit_..." block)
  2. if this is PriorityEventHandler-based priority dropdown, then use "la_fld_Order" phrase (for both editing and in grids)
  3. otherwise keep "la_fld_Priority" phrase (for both editing and in grids)
  4. change translation of "la_fld_Priority" phrase (for both editing and in grids) to say "Priority"

Related Tasks

INP-1667 - Getting issue details... STATUS