-
Type: Improvement
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: ADDONS_10.10
-
Fix Version/s: ADDONS_10.10, ADDONS_2021
-
Component/s: Aspera Connector
-
Tags:
-
Sprint:Connectors Sprint 5 - Oct
-
Story Points:3
we are starting to encounter "issues" around the existing definition to the aspera transfer lifecycle and the status mapping.
studio project with the current and proposed lifecycle. screenshot of the current is below. the studio links have a little more info as part of the state description.
Current pain points involve some slightly illogical transitions, missing transitions, and a need for multiple "completed" or "failed" state.
Modifying the current lifecycle would allow for some better scheduling and eventually, more targeted notifications to the users (based on a more meaningful lifecycle status).
It should be noted that, as usually happens, the names given to the lifecycle states is not 100% in agreement, so the ability to modify the "label" of the lifecycle state within the UI is needed. : )
- is related to
-
NXP-29424 Remove the limitation around Draft Transfers
- Resolved
-
NXP-29425 Ensure transfer update is done under one transaction
- Resolved
-
NXP-29527 adjust the action/dropzone/status icon permissions based on transfer lifecycle
- Resolved
-
NXP-29406 As a user, I have access to a dashboard of transfers
- Resolved
- is required by
-
NXP-31098 We need one more tab in Aspera Dashboard for the failed transfer
- Resolved
- mentioned in
-
Page Loading...
1.
|
Testing of modified lifecycle | Resolved | spaul |