-
Type: Epic
-
Status: Resolved
-
Priority: Minor
-
Resolution: Won't Do
-
Affects Version/s: 4.4.0
-
Fix Version/s: Not yet scheduled version
-
Component/s: Direct Transfer
-
Tags:
-
Sprint:nxDrive 11.1.27, nxDrive 11.1.28, nxDrive 11.1.32, nxDrive 11.1.33, nxDrive 11.1.34, nxDrive 11.1.35
-
Completion Level (0 to 5):5
Now that the POC has been "validated", e.g. users are interested by the working feature, it is time to implement it the right way.
We are going to use TDDD (Test Domain-Driven Design) for that specific feature as it is an entire application on itself. A sub-application to be more precise, because it will live within Nuxeo Drive.
Each step of development will be driven by user stories and the code will implement those user stories only. No need to think of a possible near future stuff to handle, it will be easily tackable using specific tickets with their own user stories, thanks to the DDD.
User Stories to Qualify
- As a user, I can plan a new transfer before the previous one is done.
- As a user having started some transfers, I can suspend any transfer not in “ended“ or “faulted”.
- As a user having sent several transfers not yet “ended“, I can change their priority.
- As a user having a erroneous transfer, I can try to fix the problem and try again to upload the transfer.
Notes for Future User Stories
- “ended“ transfers disappear after 2 weeks.
- depends on
-
NXDRIVE-2189 Move non-Python test files to specific folders
- Resolved
- is related to
-
NXDRIVE-2006 [Direct Transfer] Isolate the component
- Resolved
- Is referenced in