We have something very simple. For our use cases, we do not need anything very sophisticated.
When we create an issue, we give it a priority label: Priority 1 being urgent and Priority 4 being not important nor urgent.
When someone is working on an issue, that developer gives it the label "In progress". Making sure that nobody does the same thing twice...
Once that issue is solved, the issue is given the "Need Review" label. Self explanatory.
We tried with labels to specify which type of issues it was in our products, but for our small company, it just creates a lot of noise for nothing.
We also use explicit branch naming to help us understanding what it is we are doing. So something like:
Type_Description_Of_Issue_InitialsOfDeveloper
Where Type would be FEAT or FIX for example ( for feature or fix ). Description of issue is either a few keywords to describe the issue or the issue number and the initials to know who coded what.
FEAT_AddingNewTypePayment_DC
That's about as much as we need for our workflow. Simple, direct, quiet.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We have something very simple. For our use cases, we do not need anything very sophisticated.
When we create an issue, we give it a priority label: Priority 1 being urgent and Priority 4 being not important nor urgent.
When someone is working on an issue, that developer gives it the label "In progress". Making sure that nobody does the same thing twice...
Once that issue is solved, the issue is given the "Need Review" label. Self explanatory.
We tried with labels to specify which type of issues it was in our products, but for our small company, it just creates a lot of noise for nothing.
We also use explicit branch naming to help us understanding what it is we are doing. So something like:
Type_Description_Of_Issue_InitialsOfDeveloper
Where Type would be FEAT or FIX for example ( for feature or fix ). Description of issue is either a few keywords to describe the issue or the issue number and the initials to know who coded what.
FEAT_AddingNewTypePayment_DC
That's about as much as we need for our workflow. Simple, direct, quiet.