microsoft / microsoft/dynamics365patternspractices
[ERROR]: Delivery plan: Acquire to dispose template text copied unchanged into six other end-to-end processes (19 tasks) + workshop names that contradict their own description (5 workshops)
@rachel-profitt is already working on this.
Since Aug 10, 2026.
- Dominant language
- Python
- Stars
- 227
- Forks
- 106
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 1
Description
Contact Details
lholck@pingala.eu
Describe the error you see in the documentation, or the correction you suggest
Body (copy-paste herunder):
Describe the error
In SbD Delivery Plan JUL 2026, the post-workshop task descriptions under Process-focused solutions (Strategize) for six end-to-end processes are verbatim copies of the Acquire to dispose (10.01.xxx) template — the text still refers to the acquire to dispose lifecycle although the task belongs to a different end-to-end process. The 10.01.001/.002/.003 originals are correct; the copies were not adapted.
Affected: 18 tasks across design to retire, forecast to plan, hire to retire, inventory to deliver, order to cash, and source to pay (each on .001, .002 and .003). The remaining end-to-end processes (20, 30, 70, 80, 85, 90, 95) are not affected because their tasks have no description at all.
Seq | Title | Microsoft ID | Text says -- | -- | -- | -- 40.01.001 | Create design to retire user stories | d6689987c51786v0 | "user stories that cover the acquire to dispose lifecycle" 40.01.002 | Configure design to retire solution | d6689987c51787v0 | "showcase the lifecycle from acquisition to disposal" 40.01.003 | Design the design to retire high-level solution architecture | d6689987c51788v0 | "architecture for the Acquire to Dispose process" 50.01.001 | Create forecast to plan user stories | d6689987c51795v0 | "cover the acquire to dispose lifecycle" 50.01.002 | Configure forecast to plan solution | d6689987c51796v0 | "lifecycle from acquisition to disposal" 50.01.003 | Design forecast to plan high-level solution architecture | d6689987c51797v0 | "for the Acquire to Dispose process" 55.01.001 | Create hire to retire user stories | d6689987c51804v0 | "cover the acquire to dispose lifecycle" 55.01.002 | Configure hire to retire solution | d6689987c51805v0 | "lifecycle from acquisition to disposal" 55.01.003 | Design hire to retire high-level solution architecture | d6689987c51806v0 | "for the Acquire to Dispose process" 60.01.001 | Create inventory to deliver user stories | d6689987c51813v0 | "cover the acquire to dispose lifecycle" 60.01.002 | Configure inventory to deliver solution | d6689987c51814v0 | "lifecycle from acquisition to disposal" 60.01.003 | Design inventory to deliver high-level solution architecture | d6689987c51815v0 | "for the Acquire to Dispose process" 65.01.001 | Create order to cash user stories | d6689987c51822v0 | "cover the acquire to dispose lifecycle" 65.01.002 | Configure order to cash solution | d6689987c51823v0 | "lifecycle from acquisition to disposal" 65.01.003 | Design order to cash high-level solution architecture | d6689987c51824v0 | "for the Acquire to Dispose process" 75.01.001 | Create source to pay user stories | d6689987c51840v0 | "cover the acquire to dispose lifecycle" 75.01.002 | Configure source to pay solution | d6689987c51841v0 | "lifecycle from acquisition to disposal" 75.01.003 | Design source to pay high-level solution architecture | d6689987c51842v0 | "for the Acquire to Dispose process"Expected behavior
Each task's description should refer to the end-to-end process it belongs to; each workshop description should use the name and workshop type from its own title. 85.15.001 needs a description covering Manage customer relationships (its siblings can serve as the pattern).
Additional context
Found in a systematic review of all 839 delivery plan items after importing SbD Delivery Plan JUL 2026 with the standard tooling. Same genre as #359 (title/description mismatch), reported separately because the root cause here is a template copy across end-to-end processes. Happy to provide the full review if useful.
Link to the article where the error is
bpc
Code of Conduct
- I agree to follow this project's Code of Conduct
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.