story-kit: accept 278_story_auto_assign_agents_to_pipeline_items_on_server_startup
This commit is contained in:
@@ -1,22 +0,0 @@
|
|||||||
---
|
|
||||||
name: "Rename upcoming pipeline stage to backlog"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 287: Rename upcoming pipeline stage to backlog
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a project owner, I want the "upcoming" pipeline stage renamed to "backlog" throughout the codebase, UI, and directory structure, so that the terminology better reflects that these items are not necessarily coming up next.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] Directory renamed from 1_upcoming to 1_backlog
|
|
||||||
- [ ] All server code references updated (watcher, lifecycle, MCP tools, workflow, etc.)
|
|
||||||
- [ ] Frontend UI labels updated
|
|
||||||
- [ ] MCP tool descriptions and outputs use "backlog" instead of "upcoming"
|
|
||||||
- [ ] Existing story/bug files moved to the new directory
|
|
||||||
- [ ] Git commit messages use "backlog" for new items going forward
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
Reference in New Issue
Block a user