3 ms·

Interesting, would love to see a better system. In the end, it's work to make it work. A bit like personal hygiene. I brush my teeth everyday, not because it h

Interesting, would love to see a better system. In the end, it's work to make it work. A bit like personal hygiene. I brush my teeth everyday, not because it helps me now but because I don't want tooth decay. My 2cts, there is a lot that already works, or works in theory. Here are my biggest pain points. As a developer my biggest gripes are: - not having a clear flow open->closed, etc. - not knowing what it means (open/closed/resolved/etc) - not knowing what the right way to close the bug via a commit is - not having the work item and communication separated and no easy flow between the two - not being able to 'resolve' the issue when there is a checkup down the line - having to have my own shadow list of bugs I'm responsible for, i.e. when I need input from somebody else and I assign the bug to them, then it's gone from my 'assigned' tickets list. As a product owner: - not heaving a way to be reminded about bugs - having to bug people about updating the tickets

avinashjn 5y ago
- not having a clear flow open->closed, etc. - not knowing what it means (open/closed/resolved/etc) - not knowing what the right way to close the bug via a commit is Maybe a visual representation of the flow and a text desc of what each stage means might help? - not having the work item and communication separated and no easy flow between the two - not being able to 'resolve' the issue when there is a checkup down the line What does this mean? - having to have my own shadow list of bugs I'm responsible for, i.e. when I need input from somebody else and I assign the bug to them, then it's gone from my 'assigned' tickets list. This is already available. It was a major thing for us as we both build the software and also find issues when we use it. So we needed a way to take care of both. The dashboard gives you a view of issues assiged to you and reported by you. - not heaving a way to be reminded about bugs Not having 'to' remind others or to be reminded? If its the former, then we have nudges that gently nudges people assigned to move the bug. If its the later, maybe a way to switch off nudges would help. - having to bug people about updating the tickets already there https://bugasura.io/release-notes/nudges-to-assign-and-resolve-issues/ https://bugasura.io/release-notes/nudges-to-assign-and-resol... https://bugasura.io/release-notes/email-reminders-weekly-summary/ https://bugasura.io/release-notes/email-reminders-weekly-sum...

avinashjn 5y ago

- not having a clear flow open->closed, etc. - not knowing what it means (open/closed/resolved/etc) - not knowing what the right way to close the bug via a commit is Maybe a visual representation of the flow and a text desc of what each stage means might help? - not having the work item and communication separated and no easy flow between the two - not being able to 'resolve' the issue when there is a checkup down the line What does this mean? - having to have my own shadow list of bugs I'm responsible for, i.e. when I need input from somebody else and I assign the bug to them, then it's gone from my 'assigned' tickets list. This is already available. It was a major thing for us as we both build the software and also find issues when we use it. So we needed a way to take care of both. The dashboard gives you a view of issues assiged to you and reported by you. - not heaving a way to be reminded about bugs Not having 'to' remind others or to be reminded? If its the former, then we have nudges that gently nudges people assigned to move the bug. If its the later, maybe a way to switch off nudges would help. - having to bug people about updating the tickets already there https://bugasura.io/release-notes/nudges-to-assign-and-resolve-issues/ https://bugasura.io/release-notes/nudges-to-assign-and-resol... https://bugasura.io/release-notes/email-reminders-weekly-summary/ https://bugasura.io/release-notes/email-reminders-weekly-sum...