[TASKS-36] (Port Master) Task detail app does not reflect assignment Created: 13/Mar/23  Updated: 19/Mar/23  Resolved: 16/Mar/23

Status: Closed
Project: Tasks
Component/s: None
Affects Version/s: 6.2.22
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Philipp Guettler Assignee: Thuy To
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: 0d Remaining Estimate: 0d
Σ Time Spent: 1h Time Spent: 1h
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

demoauthor.magnolia-cms.com


Issue Links:
Cloners
clones TASKS-28 Task detail app does not reflect assi... Closed
dependency
depends upon TASKS-28 Task detail app does not reflect assi... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
TASKS-37 Implementation Sub-task To Do  
TASKS-38 Review Sub-task To Do  
TASKS-39 Pre-Integration QA Sub-task To Do  
TASKS-40 QA Sub-task To Do  
Template:
Acceptance criteria:
Empty
Epic Link: AuthorX Support
Story Points: 0.5
Team: AuthorX
Work Started:

 Description   

Steps to reproduce

  1. Login at https://demoauthor.magnolia-cms.com/.magnolia/admincentral
  2. Publish a website
  3. Go to tasks app and open details of created task
  4. Execute action "Assign to me"

.. Logs, screenshots, gifs...

Expected results

The view should update and display the current user name in field "Assignee".

.. Justify non-trivial expectations with a link to a doc or a relevant discussion.

Actual results

The view is not updated, the field is empty.

Workaround

Refresh browser or reopen the task detail view. Note that in "browser view" in tasks app, the view is updated after executing the action.

Development notes

Tested with browsers Chrome 109.0.5414.120 and Firefox 109.0.1.

 

Discovery

Bug in task detail only. Need to initiate task detail refresh on action.

Task detail is using actions from here

info.magnolia.ui.admincentral.shellapp.pulse.task.action.ClaimTaskAction

instead from here
info.magnolia.task.app.actions.ClaimTasksAction

 

 


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