[MAGNOLIA-1632] Inbox shows only page name without full path Created: 19/Jul/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: zam6ak Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

3.1-SNAPSHOT
JBoss 4.0.5.GA


Issue Links:
relation
is related to MAGNOLIA-1362 Activating a subtree (Activate inc. s... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Scenario:

There are 50 subsites each having contact.html page.
The page gets updated frequently and is sent to publishers to be activated.
Publishers then get 50 contact pages in the Inbox and there is no easy way to find which page belongs to a certain subsite in order to publish it (publisher has to open a dialog for each page in order to figure this out). The situation gets even more convoluted when people publish multiple versions of the same page....

Simple solution:

Since "real estate" on the Inbox page is precious, implement simple "onmouseover" hover (or even status in the status bar) that would show entire path of the page in the inbox. This would not require adding columns to the treetable thus saving space on those lengthy page paths...



 Comments   
Comment by Magnolia International [ 19/Jul/07 ]

Thanks for the report. Linking to MAGNOLIA-1362 since this is only an issue since that one was implemented.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:28:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.