docs: Werkbaum-Plan — 1 Knoten in Produktion
Beim Deploy der stabilen Instanz gehen diese Knoten live; SPEC §4 unterscheidet [x] fertig von [^] in Produktion (D30): - #trk.write: Write the status back (M) :#trk.resolve
This commit is contained in:
@@ -204,7 +204,7 @@
|
|||||||
- [/] #trk.resolve: Resolve "#US-123" over the REST API (M)
|
- [/] #trk.resolve: Resolve "#US-123" over the REST API (M)
|
||||||
- [^] #trk.resolve.read: Read title, link and status (S)
|
- [^] #trk.resolve.read: Read title, link and status (S)
|
||||||
- [/] #trk.resolve.map: Map the workflow onto the states (S)
|
- [/] #trk.resolve.map: Map the workflow onto the states (S)
|
||||||
- [x] #trk.write: Write the status back (M) :#trk.resolve
|
- [^] #trk.write: Write the status back (M) :#trk.resolve
|
||||||
- [^] #trk.create: Create tickets from nodes (XL)
|
- [^] #trk.create: Create tickets from nodes (XL)
|
||||||
- [^] #trk.create.proxy: Backend proxy with named endpoints (M)
|
- [^] #trk.create.proxy: Backend proxy with named endpoints (M)
|
||||||
- [^] #trk.create.login: Log in to Taiga, token stays in the browser (S) :#trk.create.proxy
|
- [^] #trk.create.login: Log in to Taiga, token stays in the browser (S) :#trk.create.proxy
|
||||||
|
|||||||
Reference in New Issue
Block a user