Document the "bug" workflow
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Yeah that's a very good point. I have not yet landed on an ideal bug workflow with Jira, I'll raise an issue in
practicesto do (and document) that more appropriately.For now, I recommend just using typical "stories", but I will get on a better workflow for them soon.
Originally posted by @jdhoffa in #63
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.
Research direction
Start with the quoted discussion from pull request #63 and review the practices repository for its current story workflow. The issue does not specify the Jira bug workflow, target documentation location, or acceptance criteria, so the workflow decision must be settled before documenting it.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100