For each payment processors, create a UML activity diagram and a UML sequence diagram to provide a view of control flow and interactions.
Sequence diagrams should show which objects are in PCI scope and which are not.
With luck, this might help us avoid edge case bugs in the queue overhaul, and facilitate maintenance going forward.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T209872 epic: frtech onwiki documentation overhaul | |||
| Open | None | T141617 Documentation: UML activity and sequence diagrams for all processors | |||
| Resolved | AndyRussG | T316584 Adyen - UML sequence diagrams |
@AndyRussG
Hi! I'm wondering if you have in-progress notes we can look at--the thing I'd like to evaluate is whether this is more useful to finish the diagrams this month, or perhaps postpone it until next quarter when the other "Stabilize and later" stuff is happening...
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)