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

Open in a new button button is confusing under a Preview tab #28347

Closed
bryanboza opened this issue Apr 24, 2024 · 1 comment · Fixed by #28348
Closed

Open in a new button button is confusing under a Preview tab #28347

bryanboza opened this issue Apr 24, 2024 · 1 comment · Fixed by #28348

Comments

@bryanboza
Copy link
Member

bryanboza commented Apr 24, 2024

Problem Statement

Users are finding the "Open in a new tab" button confusing under the Preview tab in dotCMS. The button's purpose and functionality are unclear, leading to uncertainty about its intended use.
image

According to the discussion, we need to rename this button to Open Published Version to be clear about what you will do when you click on it

Steps to Reproduce

  • Open any page
  • Click under the "Preview" Tab
  • Check the button

Acceptance Criteria

  • We need to rename that button to Open Published Version

dotCMS Version

Tested on the last Trunk // docker // FF

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

@bryanboza bryanboza changed the title Open in a new tab button is confusing under s Preview tab Open in a new button button is confusing under s Preview tab Apr 24, 2024
@bryanboza bryanboza changed the title Open in a new button button is confusing under s Preview tab Open in a new button button is confusing under a Preview tab Apr 24, 2024
erickgonzalez added a commit that referenced this issue Apr 24, 2024
@bryanboza
Copy link
Member Author

Fixed, tested on the last trunk image // docker // FF

Image

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.

2 participants