Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display 'No Notifications' Message for User Clarity #27368

Closed
manuelrojas opened this issue Jan 18, 2024 · 2 comments · Fixed by #27611
Closed

Display 'No Notifications' Message for User Clarity #27368

manuelrojas opened this issue Jan 18, 2024 · 2 comments · Fixed by #27611

Comments

@manuelrojas
Copy link
Contributor

manuelrojas commented Jan 18, 2024

Parent Issue

#25733

User Story

As a user, I want to be able to see a "No Notifications" message on the interface when there are no notifications present, so I can quickly and clearly understand that there are currently no new notifications to view.

Acceptance Criteria

Ensure the display of the following message according to the provided Figma file design. Refer to the file for specific details and layout.

image

Figma https://www.figma.com/file/3f17xtGfHmJx3RuC9YhQox/What%E2%80%99s-New-Menu?node-id=631:8405&mode=dev

Proposed Objective

Please Select

Proposed Priority

Please Select

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@manuelrojas manuelrojas self-assigned this Jan 18, 2024
@manuelrojas manuelrojas moved this from New to Current Sprint Backlog in dotCMS - Product Planning Jan 18, 2024
@manuelrojas manuelrojas moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Feb 9, 2024
manuelrojas added a commit that referenced this issue Feb 13, 2024
@manuelrojas manuelrojas moved this from In Progress to In Review in dotCMS - Product Planning Feb 13, 2024
@manuelrojas manuelrojas linked a pull request Feb 13, 2024 that will close this issue
3 tasks
manuelrojas added a commit that referenced this issue Feb 14, 2024
manuelrojas added a commit that referenced this issue Feb 14, 2024
manuelrojas added a commit that referenced this issue Feb 14, 2024
github-merge-queue bot pushed a commit that referenced this issue Feb 14, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in dotCMS - Product Planning Feb 14, 2024
@nollymar nollymar moved this from Done to Internal QA in dotCMS - Product Planning Feb 15, 2024
@nollymar nollymar reopened this Feb 15, 2024
@github-project-automation github-project-automation bot moved this from Internal QA to Current Sprint Backlog in dotCMS - Product Planning Feb 15, 2024
@nollymar nollymar moved this to Internal QA in dotCMS - Product Planning Feb 15, 2024
@dcolina dcolina self-assigned this Feb 15, 2024
@dcolina
Copy link
Contributor

dcolina commented Feb 15, 2024

Internal QA: Passed.

As you can see in the following image.

Screenshot 2024-02-15 at 18 39 00

@dcolina dcolina moved this from Internal QA to QA - Backlog in dotCMS - Product Planning Feb 15, 2024
@dcolina dcolina removed their assignment Feb 15, 2024
@github-project-automation github-project-automation bot moved this from QA - Backlog to Done in dotCMS - Product Planning Feb 16, 2024
@nollymar nollymar moved this to QA - Backlog in dotCMS - Product Planning Feb 16, 2024
@bryanboza
Copy link
Contributor

Fixed, tested on master // Docker // FF

@bryanboza bryanboza moved this from QA - Backlog to Done in dotCMS - Product Planning Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants