[MAGNOLIA-1136] Improvements for the inbox display Created: 12/Oct/06  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

In various cases of activation workflows, it could be useful to quickly see the state of a workitem in the inbox, why it is there and for who. (for examplem if an activation was rejected by a publishe, the editor has no easy way to see that it was actually rejected, and that him or someone should take care of making corrections to the document)

Adding columns to the inbox page is an option, but probably not the best, since we already have quite an amount of them.



 Comments   
Comment by Philipp Bracher [ 13/Oct/06 ]

At least we should show this information in the dialog. This can get done easily.

Comment by Philipp Bracher [ 13/Oct/06 ]

assigning everything to gregory makes a lot of fun

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:24:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.