Issue management

We are tracking 3 types of issues:

• - for feature requests
• - not sure about something or want to clarify
• - something is not working

Issue life-cycle

Life-cycle of the issues is tracked and managed via labels and assignee's.

Possible workflows through the life-cycle

• New -> Clarification -> Prioritization -> In Progress (Squad is working on it) -> Closed
• New -> Prioritization -> Ready for community to pick it up
• New -> Clarification -> Closed

All issues are open with label. The new label means that nobody from Squad took a look at the issue yet.

When any squad member finds an issue with the new label the member removes the label new and assigns themselves.

• If the issue is clear and in proper category the member assigns squad's Product Owner
• If the issue is unclear the member adds label and gather more information

When the Product Owner gets an issue assigned, the Product Owner decides together with other stakeholders whether this is an issue that the squad will work on.

• If the issue is going to be worked on by squad the Product Owner assigns the label
• Otherwise the Product Owner adds the label

When the Squad starts work on an issue the label will be added.

When the Squad resolves the issue, the squad closes it.

Issue handling

We aim to have healthy issue log. Stale issues without response will be closed. Thank you for your understanding.