Skip to content

Feature Request: Add CRUD for Story Tasks and Workflow Status Updates #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
7 tasks
steveclarke opened this issue Mar 27, 2025 · 3 comments
Open
7 tasks

Comments

@steveclarke
Copy link
Contributor

steveclarke commented Mar 27, 2025

Just testing out the new MCP server in Cursor. Love it! I was able to fetch a story and have Cursor implement the feature perfectly.

Couple of feature requests that would have made the experience perfection:

Requested Features

1. Story Tasks CRUD Operations

Add support for the following task operations:

  • Create new tasks within a story
  • Read/list existing tasks
  • Update task details (description, completion status)
  • Delete tasks
  • Mark tasks as complete/incomplete

2. Workflow Status Updates

Add the ability to:

  • Move stories between workflow states
  • Get available workflow states for a story

Use Cases

  1. AI assistants need to track implementation progress by creating and updating tasks
  2. Automated workflow management (e.g., moving cards to "In Review" after code changes are committed)
  3. Read card description and create a full set of tasks from it; modify tasks based on updated description

Benefits

  1. More complete automation capabilities through the MCP interface
  2. Reduced context switching for developers using AI assistants
  3. Better task tracking and workflow management
@steveclarke
Copy link
Contributor Author

I've just submitted a PR that implements the Tasks management feature.

@steveclarke
Copy link
Contributor Author

I've just submitted a PR that implements the Workflow status updates feature.

@steveclarke
Copy link
Contributor Author

I just realized that it may be difficult to merge the second feature PR after accepting the first. I have a branch with the full feature set that I can submit as a single PR if that would make it easier. Please let me know and I can replace PR #4 and PR #5 as a single PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant