Read and file an epic's child issues and sub-tasks through a plan backend interface, with a Jira backend and an in-memory fake #594
Reference in New Issue
Block a user
Delete Branch "item-403"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds
bin/do_epic/backend/: theEpicStoreprotocol, a Jira backend and an in-memory fake, both held to one contract. A read gives each child issue of the epic, open or done, followed by its sub-tasks, with labels, assignee, status and parent. Filing makes a child issue, or a sub-task through the project's sub-task issue type.plan_store.jira_epic's paged search moves intosearched, which both use. The store stays apart fromPlanStore, since an epic item names no release.WIP: Read and file an epic's child issues and sub-tasks through a do-epic backend interfaceto Read and file an epic's child issues and sub-tasks through a plan backend interface, with a Jira backend and an in-memory fake