Notification Setting

There are 2 types of Notification

a. Project/ticket based
b. Role Based

Project / Ticket based

When a bug ticket is opened (usually going to be a child ticket)

When a dependant feature ticket is opened (usually a child ticket)
Hourly updates digest
On any reopen of a ticket
Reminder to set goals
Reminder to close tickets
Goals status on every Sunday
Notify the selected participants when explicitly asked in a ticket
Notification requiring QC
If more than one ticket in 'In progress'
If there is zero ticket in 'In progress' for more than 15 min, repeating
every 15 min after that.
Whenever a ticket is moved from current sprint to backlog

Role Based

Weekly goals digest by staff on

every Monday
Menu Design:

Default Setting:

Brand have an option to select the default notification channel.

For now projectwheel provide the notification channel Slack and telegram

Other notification channel can be included based on the brand request

Add/Edit Team Notification channel:

Each team will have the notification channel. Channel link can be added here. And
default channel will be based on the setting. It can be changed based on the team

If none Selected , The Input box to get the channel link can be hidden. And Notification is sent to the
team channel so it will not show in the team list of notification setting.
Notification Setting
Project based

Based on the project selected, the notification status changes role and team
involved need to be shown.

Mainly based on the project content type eg. Back to {dev}, Ready to {QC}

Type, Notify, Team are multi selection option

Type  List of all notification type

Notify  Whom the notification to be sent. Everyone, Asssignee, Reporter. For

ticket status related notification show all the 3 option, remaining only Everyone.

Team  List of all Teams involved in the project. The notification will be sent to
the Respective team channel based on whom the notification to be sent

If Everyone is selected, the notification to be sent to all team channels mentioned.

Even if notification is related to specific staff and Everyone notify selected. And
It need to notify in all team channel selected ,by mentioning name or by tagging
them if they are available in channel

Eg: Time log for more than 45 hours

If Time log type is selected and notify “ Everyone “ is selected.

It need to notify all the selected team channel, If staff present in the channel
then Tag them, else mention only the staff name.

If Assignee or Reported selected, The staff need to be tagged in the specific team
channel involved.

When Select All option is selected all the option need to be selected and shown.

For Type and team select all option

Don’t Show SelectAll In Box if selected

Edit option of Notification status:

When the status is selected, If Already notify and team is mapped. It need to be
showed.

Eg: if Back to {dev} is mapped to Notify ( Assignee ) and team(orderific-

UI,orderific-devleopment)
If Back to {dev} is selected automatically respective Notify and team need to be
showed.

Edit the Notify and team option and submit it. It needs to replace the changes in
the list.

Display of Notification:

Based on the project, Type, Notify and team notification added list need to be
shown.

Eg. Orderific project

Type  back to dev

Notify  Assignee
Team Orderific-UI, Orderific-developers

Show the list of Notification type linked to Notify and team

Delete Notification Popup

Delete option need to be shown for each status. Using delete option the
notification status can be removed. Once deleted the notification of the status is
not sent to the team channel

Error Message:

Notification status, team and role is required field. If not selected, error message
needs to be shown.
Notification Setting Permission:

Add this setting in permission page

Update  Create, edit for notification status

View  View the notification setting page, when Update and Delete option is selected. By default view option
need to be selected.

Delete  delete the notification status

NOTIFICATION TYPE:

1. Ticket Status:

List all the ticket status in notification type. Based on the

Environment and the project content type, ticket status changes.

Format:
@channeltagname: The ticket ‘PMS-1234-Data table values
issue’ is moved to {TicketStatus}

2. Back to {Creator}

For Back to {creator} status format of ticket notification differs.

Format:
@channeltagname : The ticket 'QRM-310 : Mobile version -
Enter the text inside qrcode box - facebook share page u r l'
has been reopened
 For More than 12 hours
@channeltagname : The ticket 'QRM-310 : Mobile version -
Enter the text inside qrcode box - facebook share page u r l'
has been in back to {creator} column for over 12 hours .

For more than 12 hours every hour reminder

needs to be sent
@channeltagname : Reminder 1: The ticket ‘PMS-1935 : Scroll issue in
Tickets & Backlog’ has been in Back to {creator} column for more than 12
hours.

@channeltagname : Reminder 2: The ticket ‘PMS-1935 : Scroll issue in

Tickets & Backlog’ has been in Back to {creator} column for more than 12
hours.

… So On Till ticket is moved to To Do or In Progress column

3. FeedBack
Add Feedback in Notification Type select dropdown

If new feedback is received, Notification to be sent to the respective team channel

selected.

Format:

{Project} new feedback: ‘Acknowledgement or read option for each comment’ is

added.

Notification for New Feedback for more than 12hours

When the Feedback status is New more than 12hrs the notification should be sent to
the respective QA group.

If there are multiple feedbacks are in New status for 12hrs:

“For past 12hours, 5 {Project name} feedbacks are awaiting for approval.”
 if single ticket

“For past 12hours, 1 {Project name} feedback is awaiting for approval.”

Notification for New Feedback for more than 24hours

When the Feedback status is New more than 24hrs the notification should be sent to
the respective QA group.

If there are multiple feedbacks are in New status for 24hrs:

“For past 24hours, 5 {Projectname} feedbacks are awaiting for approval.”

if single ticket

“For past 24hours, 1 {Projectname} feedback is awaiting for approval.”

4.WEEKLY GOAL
In Notification type, Add ‘Weekly goal’

On Sprint closing date and time, Week goal status need to be posted
based on the team channel selected

Format:

Weekly Goal(10-Apr-2023 to 16-Apr-2023) Status.

Completed By: Staff name 1, Staff name 2
Not Completed By : Staff name 3, Staff name 4

Reminder to set the goal

If efficiency is Yes , task is assigned and Goal confidence is not set.

Remainder need to be sent at Sprint start date and timezone at 6PM,

9PM, 11PM

@channeltagname: Kind reminder to set your weekly goal confidence level.

The deadline ends in 6 hours 00 minutes.

@channeltagname: Kind reminder to set your weekly goal confidence level.

The deadline ends in 3 hours 00 minutes.

@channeltagname: Kind reminder to set your weekly goal confidence level.

The deadline ends in 1 hour 00 minutes.
5. Backlog
Add "Backlog' in Notification Status

Reminder to make the tickets ready for Next sprint at Sprint end date and time
zone “6PM, 9PM, 11PM”.

Format:

Kind reminder to make the tickets ready for next sprint. The deadline ends in 6 hours
00 minutes.

Kind reminder to set your weekly goal confidence level. The deadline ends in 3 hours
00 minutes.

Kind reminder to set your weekly goal confidence level. The deadline ends in 1 hour
00 minutes

6. {Environment }Deployed / Ready to {auditor} column

List all the ticket status in notification type. Based on the
Environment and the project content type, ticket status changes.

Format:
@channeltagname: The ticket ‘PMS-1234-Data table values
issue’ is moved to {TicketStatus}

Reminder to close the tickets

If the tickets are in {Environment }Deployed / Ready to {auditor} column

Reminder need to be sent at Sprint end date and time zone at 6PM, 9PM,
11PM

Kind reminder to Close or Audit the tickets which are awaiting for approval.
The deadline ends in 6 hours 00 minutes.

Kind reminder to Close or Audit the tickets which are awaiting for approval.
The deadline ends in 3 hours 00 minutes.
 Kind reminder to Close or Audit the tickets which are awaiting for approval.
The deadline ends in 1 hours 00 minutes.

7. TIME LOG

In Notification Status add “TimeLog”.

Notification about timelog

50% of the week is over but 50% of availability hours ( committed Working hours)
have not been logged by Staff who has Availability “YES” and has task in Task
board. Reminder to be send everyday after 50% of week at 10AM timezone till the
50% of availability is achieved.

Format:

@channeltagname: Reminder to log the time, Time logged in the tickets are 10
hours.

TimeLog more than 45 hours

If timelog is more than 45 hours , then notifiy in group staff has logged more than 45
hours

Format:

@{Staffname} has logged more than 45 hours.

Confirmation popup for time log before moving Ready to {auditor}

Before moving the ticket to "Ready to {auditor}. Confirmation to get the time log
made or not.

Popup for Ticket Status change, View detail ticket status change, Board drag and
drop

Is time Log done before moving to Ready to {QC}?"

Yes No
If yes button is pressed , move the ticket to respective column

If No button is pressed, Open the ticket description popup to log the time in
Time tracking.