Refine a ticket
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the checklist and refining workflow in this issue. Review the team backlog against the user story, Given/When/Then, and testable criteria requirements; done means a selected ticket is refined, while your own ticket remains unpromoted for a teammate to validate.
Written by the indexing model from the issue text.
Description
As a developer, you want to refine tickets so that anyone in your team can pick up and deliver any feature in your application.
Given a ticket in the backlog
When I refine the ticket
Then it is ready to be worked on
I expect a refined ticket to have
- a user story
- G/W/T
- testable criteria
β Checklist
So a refined ticket has all the information anyone might need to complete a feature. This is usually:
- A user story
- Specification by example (Given/When/Then)
- Acceptance criteria or assertions
πΌοΈ Refining Tickets Workflow
- π₯ How important is this task? Prioritise π€
- π How long will this take? Estimate βοΈ
- π Does this task have a deadline? Schedule π
- ποΈ What type of work is this? Sort π
- πΆβπ«οΈ What would someone else need to know to complete this task? Explain π¨ (or Ask)
A ticket is fully refined when anyone in your team could pick it up. If you can validate a ticket in the Backlog as Ready, move it to Ready now.
Only tickets In Progress can belong to any particular team member, so don't claim tickets now.
π« Refine some tickets
Read over your team backlog. Validate the tickets against the checklist given above. If there are any tickets that are Ready, promote them from the Backlog.
Now select a ticket from the Backlog to refine. Use the refining tickets workflow. Don't promote your own ticket to Ready - leave that to a team-mate to validate.
You can do this asynchronously or in a call with your team. Whichever helps you to make progress.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-The-Launch
-
Weekly Catch-up Openπ Priority Mandatory π Size Small π Week 1 π Week 2 π Week 3 π Week 4 π Week 5 Launch Recurring
Difficulty 1/5 Under an hour Newbie friendliness 85/100
CodeYourFuture/Module-The-Launch#3 Β· 8 comments Β·
-
π Week 1 π Priority Key Launch Setup π¦ Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 65/100
CodeYourFuture/Module-The-Launch#1 Β· 1 comment Β·
-
π― Topic Code Review π― Topic Teamwork π Priority Mandatory π Size Medium π Week 2 π Week 3 π Week 4 π Week 5 Recurring
Difficulty 1/5 1-3 hours Newbie friendliness 30/100
-
π Size Medium π Week 4 π Priority Key Core Launch
Difficulty 2/5 Half a day Newbie friendliness 45/100
-
Handover Document Openπ Size Medium π Week 5 π Priority Key Core Launch
Difficulty 1/5 1-3 hours Newbie friendliness 55/100
All issues in CodeYourFuture/Module-The-Launch
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 Β·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 Β·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 Β·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 Β·
-
category/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100