docs(epic-workflow): add epic delivery guide on how to manage epics #19551
+91
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrainville
requested review from
a team,
Rsttskyy,
alaibe,
glitchminer,
noeliaSD,
osmaczko,
saledjenic,
sunleos and
xAlisher
and removed request for
a team
Member
Member
Member
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19551#1 🔹 ~15 min 🔹 59aea43 🔹 📦 tests/ui package |
Member
Member
Member
Member
✔️ status-desktop/e2e/prspr19551 🔹 ~17 min 🔹 59aea43 🔹 📦 tests/e2e package |
noeliaSD
approved these changes
Dec 11, 2025
Contributor
noeliaSD
left a comment
noeliaSD
left a comment
There was a problem hiding this comment.
Thanks @jrainville for adding the content here! I've just left 2 comments, otherwise, LGTM! ;)
| ## 4. Development Planning | ||
|
|
||
| * The Dev owner reviews the final design. | ||
| * The Dev owner breaks down the epic into **small, actionable subtasks**. |
Contributor
There was a problem hiding this comment.
Maybe we could also add here what we discussed about creating a task to include this new feature in the automation flow.
| ## 5. Design QA (Post-Implementation Review) | ||
|
|
||
| * Once the implementation is complete, **Dev notifies Design**. | ||
| * A **Design QA task** is created within the epic for tracking. |
Contributor
There was a problem hiding this comment.
Maybe this could be included in point 4, so the necessary subtasks to close the epic are already created from the very beginning. WDYT?
Member
✔️ status-app/prs/android/arm64/package/PR-19551#2 🔹 ~9 min 52 sec 🔹 1fcf3f6 🔹 📦 android/arm64 package |
Member
✔️ status-app/prs/linux/x86_64/tests-nim/PR-19551#2 🔹 ~10 min 🔹 1fcf3f6 🔹 📦 tests/nim package |
Member
✔️ status-app/prs/linux/x86_64/tests-ui/PR-19551#2 🔹 ~14 min 🔹 1fcf3f6 🔹 📦 tests/ui package |
Member
Member
Member
Jenkins Builds
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on top of #19543 since it uses the same folder and links to it
Adds a guide on how to manage Epics effectively and that takes into account all stakeholders. This should make it so that when a feature is done, it is DONE 😄
Huge thanks to @noeliaSD do creating the guide. I mostly just formatted it and put in here.