Best practice for tracking a full stack feature enhancement in GitHub Projects #67010
Replies: 2 comments
-
|
Hey - thanks for asking - I'm going to include this in our next check-in so it gets some visibility for users to weigh in 😄 |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Feature Area
Projects
Body
Hi, I would like to know if the community has an opinion on the best practice for my use case.
We are making some full-stack feature enhancements to an app. There are multiple user stories/feature enhancements, each of which would require modification of both API and frontend app.
We are running two sprints, one to update the API and the other to update the frontend.
I am wondering if I should create three issues for each user story, one master issue to track and discuss each feature enhancement with two separate sub-issues for API and frontend changes. This way I can assign the API sub-issue to the backend sprint and the frontend sub-issue to the frontend sprint. But this is leading to a large number of issues not easy to manage, especially in project boards and views.
Are there guidelines / best practices on how to approach such situations?
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions