[MGNLWORKFLOW-278] Allow tasks to be aborted Created: 01/Dec/14  Updated: 29/Apr/15  Resolved: 16/Feb/15

Status: Closed
Project: Magnolia Workflow Module
Component/s: Base
Affects Version/s: 5.4.2
Fix Version/s: 5.5

Type: Improvement Priority: Major
Reporter: Andreas Weder Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-3349 Task action availability should allow... Closed
relation
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   

Tasks currently can only be removed from the list of tasks (in Pulse) when they're marked as "completed". The only way to mark them "completed" is by either accepting or rejecting them. Completed tasks may then be removed from the list with the corresponding action.

This leaves a gap in the current user experience, as you can't remove or delete tasks which have become obsolete. Typical cases are workflows, which were started initially - during development or while setting up a new site -, but were eventually canceled or deleted. Such workflows often leave dozens of tasks in Pulse, which are no longer relevant.

We should allow tasks to be aborted, which would:

  • abort the corresponding workflow
  • remove the task from the list of tasks

The abort action should be available as bulk action as well to allow for easy handling of a large set of tasks. If should consider to ask users to first "assign to me" all tasks they intend to abort to ensure for a clean audit trail, but this has to be discussed more thoroughly first.



 Comments   
Comment by Espen Jervidalo [ 16/Feb/15 ]

Aborting tasks is implemented, but not for batch actions. see linked ticket about that.

Generated at Mon Feb 12 10:08:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.