[MAGNOLIA-1296] Can't display the inbox of another user Created: 09/Jan/07  Updated: 23/Jan/13  Resolved: 23/Feb/07

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

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1396 Workflow module api/code cleanup Closed
is related to MAGNOLIA-1295 Inbox can't be displayed if we use ex... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

at the moment, eventhough the getWorkItems method in WorkflowUtil lets us supposedly get the inbox for any user, it won't work properly, since its using the given username only to retrieve the directly assigned items. It will then use the current user's groups and roles to get the items assigned to groups/roles.



 Comments   
Comment by Magnolia International [ 10/Jan/07 ]

3 options

1) we change the api so the method takes a User instance
2) we change the api so the method takes no param but gets the current User itself like it does now
3) we don't change the api so the method takes a String username and uses the UserManager to get a User instance

#3 is probly the best option for a 3.0.x release, and i would vote for #1 for a 3.1 release

Comment by Nicolas Modrzyk [ 05/Feb/07 ]

I've commited #3 in svn.

I propose we add a method that takes a User but keep the method with the username, therefore we can actually proceed with this item without waiting for the 3.1 release.

What do you think ?

Niko

Comment by Philipp Bracher [ 06/Feb/07 ]

Sounds fine for me. You can merge to the 3.0 branch.

Comment by Magnolia International [ 23/Feb/07 ]

commited to branches/magnolia-3.0 and trunk

todo : create jira tasks for 3.1 w/better api

Comment by Magnolia International [ 23/Feb/07 ]

See MAGNOLIA-1396 for further improvements

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