Add Tradon development backlog workflow
This commit is contained in:
GiorgioCALLIGARO
@@ -2,6 +2,18 @@
|
||||
|
||||
This file records decisions taken after reviewing the GL-001 exposure to Tryton / Tradon.
|
||||
|
||||
## Development readiness rule
|
||||
|
||||
A development backlog item can move from `Blocked` to `Ready` only when all linked pending decisions are `Confirmed`.
|
||||
|
||||
A decision is `Confirmed` when it has:
|
||||
|
||||
- a selected option or explicit arbitration;
|
||||
- a rationale;
|
||||
- an impact statement;
|
||||
- linked backlog items;
|
||||
- a validation or review expectation.
|
||||
|
||||
## Decision log
|
||||
|
||||
| Date | ID | Decision | Rationale | Impact | Status |
|
||||
@@ -18,3 +30,146 @@ This file records decisions taken after reviewing the GL-001 exposure to Tryton
|
||||
| GL001-PD004 | Decide which source origin models feed `document_date`, `document_type` and supplier invoice references. | GL001-Q006, GL001-Q012 | Open |
|
||||
| GL001-PD005 | Decide whether commodity fields `payable_qty` and `uom` are required in the first implementation. | GL001-Q007, GL001-Q013 | Open |
|
||||
| GL001-PD006 | Decide whether GL-001 requires a new flat reporting dataset. | GL001-Q008 | Open |
|
||||
| GL001-PD007 | Decide whether audit and source reference mappings are generic across accounting reports or specific to GL-001 first. | GL001-Q010 | Open |
|
||||
|
||||
## Decision details
|
||||
|
||||
### GL001-PD001 Document reference mapping
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q001, GL001-Q002, GL001-Q003
|
||||
|
||||
Impacted backlog items: DEV-GL001-004
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
### GL001-PD002 Transaction-currency fallback
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q004
|
||||
|
||||
Impacted backlog items: DEV-GL001-002, DEV-GL001-006
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
### GL001-PD003 GL sign convention transformation
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q005
|
||||
|
||||
Impacted backlog items: DEV-GL001-007
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
### GL001-PD004 Source document metadata
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q006, GL001-Q012
|
||||
|
||||
Impacted backlog items: DEV-GL001-005
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
### GL001-PD005 Commodity quantity fields
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q007, GL001-Q013
|
||||
|
||||
Impacted backlog items: DEV-GL001-010
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
### GL001-PD006 Flat GL-001 dataset
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q008
|
||||
|
||||
Impacted backlog items: DEV-GL001-001, DEV-GL001-003, DEV-GL001-009
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
### GL001-PD007 Shared audit and reference mapping scope
|
||||
|
||||
Status: Open
|
||||
|
||||
Linked open points: GL001-Q010
|
||||
|
||||
Impacted backlog items: DEV-GL001-008
|
||||
|
||||
Decision:
|
||||
TBD
|
||||
|
||||
Rationale:
|
||||
TBD
|
||||
|
||||
Impact:
|
||||
TBD
|
||||
|
||||
Validation expectation:
|
||||
TBD
|
||||
|
||||
@@ -4,26 +4,26 @@
|
||||
|
||||
| ID | Question | Area | Status |
|
||||
| --- | --- | --- | --- |
|
||||
| GL001-Q001 | In Tryton / Tradon mapping, should `document_number` be `account.move.number`, `account.move.post_number`, invoice `number`, or a context-dependent value? | Document references | Open |
|
||||
| GL001-Q002 | Should `journal_entry_number` be `move.number` and `document_number` be the business document number? | Document references | Open |
|
||||
| GL001-Q003 | Is `voucher_number` distinct in Tradon, or should it remain blank? | Document references | Open |
|
||||
| GL001-Q004 | Should `transaction_currency` default to company currency when `second_currency` is empty? | Currency | Open |
|
||||
| GL001-Q005 | Should credit columns be exported as negative values to match the target GL, even though Tryton UI displays credit as positive? | Sign convention | Open |
|
||||
| GL001-Q006 | Which origin models should feed `document_date` and `document_type` in the first implementation? | Source document metadata | Open |
|
||||
| GL001-Q007 | Can `payable_qty` and `uom` be derived reliably from `account.move.line.lot`, fees or invoice line origin for all commodity postings? | Commodity fields | Open |
|
||||
| GL001-Q001 | Q: In Tryton / Tradon mapping, should `document_number` be `account.move.number`, `account.move.post_number`, invoice `number`, or a context-dependent value? | Document references | Open |
|
||||
| GL001-Q002 | Q: Should `journal_entry_number` be `move.number` and `document_number` be the business document number? | Document references | Open |
|
||||
| GL001-Q003 | Q: Is `voucher_number` distinct in Tradon, or should it remain blank? | Document references | Open |
|
||||
| GL001-Q004 | Q: Should `transaction_currency` default to company currency when `second_currency` is empty? | Currency | Open |
|
||||
| GL001-Q005 | Q: Should credit columns be exported as negative values to match the target GL, even though Tryton UI displays credit as positive? | Sign convention | Open |
|
||||
| GL001-Q006 | Q: Which origin models should feed `document_date` and `document_type` in the first implementation? | Source document metadata | Open |
|
||||
| GL001-Q007 | Q: Can `payable_qty` and `uom` be derived reliably from `account.move.line.lot`, fees or invoice line origin for all commodity postings? | Commodity fields | Open |
|
||||
|
||||
## Implementation questions
|
||||
|
||||
| ID | Question | Area | Status |
|
||||
| --- | --- | --- | --- |
|
||||
| GL001-Q008 | Should GL-001 be implemented as a new flat reporting dataset rather than extending the standard Tryton General Ledger views? | Dataset design | Open |
|
||||
| GL001-Q009 | Should transaction-currency opening and closing balances be calculated in the reporting layer or stored in an intermediate model? | Currency balances | Open |
|
||||
| GL001-Q010 | Should document and source reference mappings be generic across all accounting reports or specific to GL-001 first? | Shared mappings | Open |
|
||||
| GL001-Q008 | Q: Should GL-001 be implemented as a new flat reporting dataset rather than extending the standard Tryton General Ledger views? | Dataset design | Open |
|
||||
| GL001-Q009 | Q: Should transaction-currency opening and closing balances be calculated in the reporting layer or stored in an intermediate model? | Currency balances | Open |
|
||||
| GL001-Q010 | Q: Should document and source reference mappings be generic across all accounting reports or specific to GL-001 first? | Shared mappings | Open |
|
||||
|
||||
## Business arbitration points
|
||||
|
||||
| ID | Question | Area | Status |
|
||||
| --- | --- | --- | --- |
|
||||
| GL001-Q011 | Is multi-entity selection required, or is the current company context sufficient for the first GL-001 implementation? | Entity | Open |
|
||||
| GL001-Q012 | Should AP-specific fields such as `supplier_invoice_number` be mandatory only when the source is an AP invoice? | Audit trail | Open |
|
||||
| GL001-Q013 | Are `payable_qty` and `uom` mandatory for GL-001 launch, or can they remain low-priority commodity extensions? | Scope | Open |
|
||||
| GL001-Q011 | Q: Is multi-entity selection required, or is the current company context sufficient for the first GL-001 implementation? | Entity | Open |
|
||||
| GL001-Q012 | Q: Should AP-specific fields such as `supplier_invoice_number` be mandatory only when the source is an AP invoice? | Audit trail | Open |
|
||||
| GL001-Q013 | Q: Are `payable_qty` and `uom` mandatory for GL-001 launch, or can they remain low-priority commodity extensions? | Scope | Open |
|
||||
|
||||
@@ -54,6 +54,28 @@ The assessment process does not change after intake: use the copied repository s
|
||||
| `decisions.md` | Decisions and arbitrations taken after review |
|
||||
| `source_material.md` | Source documents, date, scope and traceability notes |
|
||||
|
||||
## Open question notation
|
||||
|
||||
Open questions must be written in the relevant assessment document, except when the user explicitly asks to handle them elsewhere.
|
||||
|
||||
Use these prefixes:
|
||||
|
||||
| Prefix | Meaning |
|
||||
| --- | --- |
|
||||
| `Q: ` | Open question requiring user, business or technical arbitration |
|
||||
| `C: ` | Comment that clarifies the open question, context or constraint |
|
||||
| `PROPOSITION: ` | Accounting-compatible proposal suggested for arbitration |
|
||||
| `R: ` | User response or confirmed answer |
|
||||
|
||||
After a document review, any new framing question should be added to the document using the same notation, unless an explicit exception is requested.
|
||||
|
||||
Expected file usage:
|
||||
|
||||
- `open_points.md` is the register of open questions. It should contain the `Q: ` entries and, when useful, related `C: ` comments or `PROPOSITION: ` proposals.
|
||||
- `decisions.md` is the register of answers and arbitrations. It should contain the user's `R: ` responses, the selected decision, rationale, impact and validation expectation.
|
||||
- A question may remain `Open` in `open_points.md` until the linked decision in `decisions.md` is confirmed.
|
||||
- When a decision is confirmed, update the linked backlog items according to the development readiness rule.
|
||||
|
||||
## Recommended statuses
|
||||
|
||||
| Status | Meaning |
|
||||
|
||||
Reference in New Issue
Block a user