Tasks with medium priority

Technical Support
1

Could you please clarify the expected behavior when task priority is ‘medium’?
The first task below is medium priority and the second is high priority but they appear the same to me.

image
image1006×1102 270 KB

 
 {
  name: 'task_leap_defaulter',
  icon: 'warning1',
  title: 'Title for LEAP defaulter can go here. Testing the maximum length Testing the maximum length',
  priority: {
    level: 'medium',
    label: 'This is medium priority text for LEAP defaulter (just testing - will be set to high priority). Testing the maximum length. Testing the maximum length.  Testing the maximum length.  Testing the maximum length.  Testing the maximum length. ',
  },
  ...
},
{
  name: 'task_dcp_defaulter',
  icon: 'warning1',
  title: 'This can be a brief description of the DCP defaulter task.',
  priority: {
    level: 'high',
    label: 'This is high priority text for DCP defaulter. Testing the maximum length. Testing the maximum length.  Testing the maximum length.  Testing the maximum length.  Testing the maximum length. ',
  },
  ...
},

Also - the label section given in the docs does not seem to work correctly. I used

    priority: {
      level: 'high',
      label: [ { locale:'en', content:'Home Birth' } ],
    },

and got

ERROR tasks.js invalid schema: 
ERROR Invalid schema at tasks[3].priority.label
"priority" should be an object with optional fields "level" and "label" or a function which returns the same
Current value of tasks[3].priority.label is [{"locale":"en","content":"Home Birth"}]
 
INFO Error: Declarative configuration schema validation errors
    at module.exports (/usr/local/lib/node_modules/cht-conf/src/lib/validate-declarative-schema.js:201:11)
    at compileDeclarativeFiles (/usr/local/lib/node_modules/cht-conf/src/lib/compile-nools-rules.js:45:3)
    at compileNoolsRules (/usr/local/lib/node_modules/cht-conf/src/lib/compile-nools-rules.js:30:12)
    at compileAppSettingsForProject (/usr/local/lib/node_modules/cht-conf/src/fn/compile-app-settings.js:105:18)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.compileAppSettings [as execute] (/usr/local/lib/node_modules/cht-conf/src/fn/compile-app-settings.js:38:19)
    at async module.exports (/usr/local/lib/node_modules/cht-conf/src/lib/main.js:193:5)
    at async /usr/local/lib/node_modules/cht-conf/src/bin/index.js:16:5 
ERROR Declarative configuration schema validation errors

Thank you

2

Hi @jschwab77

Thanks a lot for reporting. Indeed, there’s a mismatch between the schema that we validate (your error) and the documentation. I’ve created an issue to track this: Task priority labels are not internationalized · Issue #571 · medic/cht-conf · GitHub

As far as layout, it does appear that there is no visual difference between a high and medium priority task label in the task list. I’m uncertain if this is a bug or not.
Tagging @Nicole_Orlowski to consult here.

3

For layout I believe all priority text is red but we have other icons that can be used for differnet levels (icon-warning-ambre and icon-warning-black)

4

Thank you. So is there supposed to be any visual difference between a high and medium priority task label in the task list?