Follow-up to #3610065 (the pull-based operations surface).

Two improvements to the "My actions" list and its per-instance sibling:

  • The standalone list moves out of the user account menu into the admin Content menu as "My Orchestra actions", next to "Orchestra tasks", so operators find it where they manage work. Its columns become Process / Step / Action, and the Process cell links to the instance trace when the viewer may see it.
  • Each row folds its actions into an operations dropbutton: the act link (open the node) first, then a one-click item per directly-signalable outcome, matching how the per-instance list column already renders. The shared logic is extracted into a PendingActionLinksTrait used by both surfaces.

No change to what a user may act on or how completion works: this is placement and presentation. Covered by a kernel test for the shared link assembly (act-first order, guarded and unlinked filtering, destination, node prefix); the operation suites stay green.

Issue fork orchestra-3610387

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mably created an issue. See original summary.

mably’s picture

Status: Active » Needs review

  • mably committed a4be9306 on 1.x
    task: #3610387 Move the My actions list under Content and render its...
mably’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.