bcgov / bcgov/entity

In-app notifications of business removal by staff

Open
#6,219 0 comments 0 reactions 0 assignees View on GitHub
Pay STORY
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

* As an account administrator
* I want an in-app notification
* so that I know if staff has unaffiliated a business with my account

**Acceptance Criteria**

**Scenario 1: Bell with red dot**
* GIVEN staff has removed a business
* WHEN the account administrator logins
* THEN the bell icon will have a red dot

CONTENT:

Staff has removed [INSERT BUSINESS NAME HERE) from your BC Registries account. This action was taken after staff received a formal request. If you have questions, please contact us

**Scenario 2: Click on bell icon**
* GIVEN staff has removed a business
* WHEN the account administrator clicks on the bell icon
* THEN a message will be displayed with the date of the change:

Staff has removed [INSERT BUSINESS NAME HERE) from your BC Registries account. This action was taken after staff received a formal request. If you have questions, please contact us

**Scenario 3: Close message**
* GIVEN a account administrator has opened the in-app notification of approval
* WHEN the account administrator clicks away from the notification
* THEN a message will close
* AND the red dot on the bell icon will continue to be displayed and the message will be there

**Scenario 4: Delete message**
* GIVEN a account administrator has opened the in-app notification of approval
* WHEN the account administrator clicks on the 'Trash' can next to the message
* THEN a message will be deleted
* AND the red dot on the bell icon will no longer appear unless their is more messages

Scenario 2, 3, 4
![notification-menu](https://user-images.githubusercontent.com/16613999/106773459-eba84b00-65f5-11eb-8677-77610d435c62.png)

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**
* Do you know a possible contact person to reach out (from the other team)?

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

----

**Link to DoR for a US/ Feature**
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Relationships.md
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Entity.md

**Link to the DoD for a US/ Feature**
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Relationships.md
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Entity.md

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by locating the existing notification menu and the staff business-removal flow, then use the four acceptance scenarios and attached screenshot as the behavior checklist; the work is done when the red-dot, display, dismissal, and deletion behavior matches those scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.