Relabel priority lanes in the backend only

[yaelberger-commits]

Relabel priority lanes

Description

Our priority lanes are currently labelled Priority, Normal and Bulk, but if we ever expose these labels to clients it is likely to cause confusion as we have a "Priority" priority lane and we can also have bulk priority notifications etc.

As a Sender, I need to be able send notifications within a certain timeframe without delay so that my notifications have the desired impact.

Ideas

Bulk = Slow
Normal = Normal
Priority = High

high, medium, casual

Standard, High, Critical

WHY are we building?
We have an assumption that if we were to expose our priority lane names to clients that it would cause confusion.

WHAT are we building?
Usability testing our labels, possibly doing card sorting exercise to learn what words our clients use to describe different types of notifications based on priority and need for quick delivery.

VALUE created by our solution
Clients will be able to understand our Service Level Objectives and level their expectations according to these.

Clients will be able to request higher priority for some of their templates if they need them to be sent faster to have the desired impact.

Work Items:

• Redis buffers will need to be renamed
• SQS Queues need to be renamed
• Will celery still check the queues?
• May have to have multiple queues existing at the same time to ensure no downtime

Acceptance Criteria** (Definition of done)

[ ] Redis Buffer Queues Renamed
[ ] SQS Queues renamed
[ ] PO's approval on naming convention
[ ] Queue migration strategy in place

QA Steps

• Tested in a realistic production scenario

[sastels]

setup email delivery SQS queues the same as the sms ones
cds-snc/notification-api#1997

[sastels]

spun off some of the work to subcard https://app.zenhub.com/workspaces/notify-planning-core-6411dfb7c95fb80014e0cab0/issues/gh/cds-snc/notification-planning-core/206