Rhythm 2.0 Specifications

Appearance

FAS-CRM-ACT-03Managing Task Work: Feature Acceptance Suite

Markdown

FAS-CRM-ACT-03

Managing Task Work: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-ACT-03
Capabilities
CAP-CRM-ACT-010, CAP-CRM-ACT-011, CAP-CRM-ACT-012, CAP-CRM-ACT-013, CAP-CRM-ACT-014, CAP-CRM-ACT-015
Executed by
TST-CRM-ACT-018, TST-CRM-ACT-024, TST-CRM-ACT-060, TST-CRM-ACT-079

Product areaCRMModuleActivities, Follow-ups and Task WorkRevision1

Read atservices-crm a8d1364freact-console baf6dae3rhythm-v2-docs 18a49edf

Managing Task Work: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The feature acceptance checks follow personal and shared work across discovery, routing, progress and overdue attention. Role-offered work and general task views retain their separate access and discovery contracts.

Interactions Between Capabilities ​

Claims change task holders and overdue audiences, while closure changes list placement and attention standing. Combined queue and role routing receives its own interaction case.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish cumulative acceptance across the feature and its related capabilities.

Scenarios

6 scenarios proving FEAT-CRM-ACT-03 as a whole.

01 Manage personal work through the task screen behaviour test
Exercises
CAP-CRM-ACT-010 CAP-CRM-ACT-012 CAP-CRM-ACT-014
Relies on
ATS-CRM-ACT-010-04 ATS-CRM-ACT-012-01 ATS-CRM-ACT-014-01
Preconditions
The run owns a task type, queue and invited teammate.
Steps
[object Object], [object Object]
Expected
The view identifies the created task and the read confirms its holder, type and supported details.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:e2e/dev/tasks.dev.spec.ts
02 Claim and release shared overdue work interaction proposed
Exercises
CAP-CRM-ACT-012 CAP-CRM-ACT-013 CAP-CRM-ACT-014 CAP-CRM-ACT-015
Relies on
ATS-CRM-ACT-012-06 ATS-CRM-ACT-013-04 ATS-CRM-ACT-015-02
Preconditions
An overdue queued task also carries a candidate role and publishing is enabled.
Steps
[object Object], [object Object]
Expected
The same task returns to shared work with its original arrival; attention follows the holder and then the queue responsibility.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/tasks/services/persistence/tasks.ts
03 Complete visible work through the console lifecycle test
Exercises
CAP-CRM-ACT-010 CAP-CRM-ACT-011 CAP-CRM-ACT-014
Relies on
ATS-CRM-ACT-011-03 ATS-CRM-ACT-014-03
Preconditions
A run-owned task is open and visible to an updater.
Steps
[object Object], [object Object]
Expected
The stored task is Completed and names the completing user; the row no longer offers Complete and the Completed view contains it.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:e2e/dev/tasks.dev.spec.ts
04 Keep read-only work access separate from mutation permissionnegative test
Exercises
CAP-CRM-ACT-010 CAP-CRM-ACT-011 CAP-CRM-ACT-012 CAP-CRM-ACT-014
Relies on
ATS-CRM-ACT-014-03 ATS-CRM-ACT-019-04
Preconditions
Read-only, contributor and administrator personas access the same task.
Steps
[object Object], [object Object]
Expected
Reads and actions follow task authority; forbidden mutations preserve the record.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0716.spec.ts
05 Select one holder in competing shared-work claims regression test
Exercises
CAP-CRM-ACT-012 CAP-CRM-ACT-013
Relies on
ATS-CRM-ACT-012-06 ATS-CRM-ACT-013-03
Preconditions
Several users can claim queued work and two users hold a role offered separate work.
Steps
[object Object], [object Object]
Expected
Each task has one holder; losing claimants receive a conflict that identifies the winner.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/tasks/tests/integration/services/persistence/tasks.concurrency.integration.spec.js
06 Resolve attention on closure and republish after reopening interaction test
Exercises
CAP-CRM-ACT-010 CAP-CRM-ACT-011 CAP-CRM-ACT-015
Relies on
ATS-CRM-ACT-015-04 ATS-CRM-ACT-011-06
Preconditions
Enabled local attention fixtures hold an open overdue task.
Steps
[object Object], [object Object]
Expected
Closing resolves the item and reopening overdue work publishes a new generation.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software