dotCMS / dotCMS/core

Announcements Menu is broken in several ways

Open
#31,477 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Core Features OKR : User Experience Team : Falcon Type : Defect
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

No response

Problem Statement
  1. The announcements are out of date.
    • Many new features aren't shown in the announcements.
    • The most recent announcement is
  2. Almost all links in the menu are broken.
    • The only link that works is the link to our Github repository.
    • This is likely a problem with the new dotCMS.com web site, because these links were likely all Vanity URLs which were not copied to the new site.
  3. All announcements eventually get reset to show as unread, even if the user has opened the announcements and read them all before.
Steps to Reproduce
  1. Open the Announcements menu.
  2. View the dates on the most recent item (the one at the top).
    • Result: The most recent announcement is from 6 months ago (August 2024).
  3. Click on any of the normal (blue underlined) links except the one labeled Github Repository.
    • Result: 404.
  4. Logout, and login a day later.
    • Result: The announcements menu icon shows the "unread" mark.
  5. Open the Announcements menu.
    • Result: All announcements are marked as unread.
Acceptance Criteria
  1. When you open the Announcements, items are shown for all the following features:
    • UVE Future Time Machine
    • Content Analytics: Dynamic Analytics Displays
    • Headless Experiments
  2. All links in the menu work.
  3. Once the menu is opened, items in the menu are never shown as unread again.
    • They must continue to show as unread even when logging in days or weeks later.
dotCMS Version

25.02.12

Proposed Objective

User Experience

Proposed Priority

Priority 2 - Important

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

Problems with this feature reduce customer confidence in the product, and interfere with our communications to customers about new features.
This slows down our efforts to help customers adopt new features and get additional value from the product.

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Announcements menu behavior described in the issue, including outdated items, broken links, and unread state after a later login. Trace the menu's announcement data, link targets, and read-state handling; done means the three listed features appear, every link works, and opened items remain read across later logins.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.