I see complexities arising from it, to do with the logic of:
a) which states to show after an edit (it may be different ones than in the first attempt, e.g. for a different Sphere of issue Type etc.)
b) decision about restricting which items can be edited, and what happens when it's none
c) issue factory: correctly dealing with items in the history that are now not relevant anymore e.g. entry for Facility when Issue Type was changed from one with to one without Facilities etc.
For the time when I do implement edit, my idea was to add a Ui() to DomainGlossary to each IWorkflowState there, which would then be used in the DomainTermSelection in the output of the Prompt.
After implementing Edit issue, check whether after the renewed Review, it also adds all Guids to all the new inputs from the editing.
I see complexities arising from it, to do with the logic of: a) which states to show after an edit (it may be different ones than in the first attempt, e.g. for a different Sphere of issue Type etc.) b) decision about restricting which items can be edited, and what happens when it's none c) issue factory: correctly dealing with items in the history that are now not relevant anymore e.g. entry for Facility when Issue Type was changed from one with to one without Facilities etc. For the time when I do implement edit, my idea was to add a Ui() to DomainGlossary to each IWorkflowState there, which would then be used in the DomainTermSelection in the output of the Prompt.
After implementing Edit issue, check whether after the renewed Review, it also adds all Guids to all the new inputs from the editing.