Processing issues

This page describes workflows for processing issues and links to relevant views on the issue tracker.

Daily

Daily tasks ensure that all inbound issues are processed and have sufficient information to be worked on.

Label incoming issues

All incoming issues need to be read and labeled either:

• by type (bug, enhancement, question, e.t.c.) and component if applicable;
• by necessary action to proceed (wait for feedback, needs decision, e.t.c.).

View link: no:label

Close issues that lack details to act on

The traditional inactivity (requested information has not been provided) cut–off is 14 days.

View link: label:"wait for feedback"

Gardening

Gardening tasks ensure that issues, which might not be in immediate development focus, are not getting stale and overlooked.

Review issues which need decision

Some issues needs decision on feasibility or direction on how to proceed.

View link: label:"needs decision"

Review stale issues

Some issues stay open for significant amounts of time and need to be checked if they still are relevant and not missing necessary attention.

View link: sort:updated-asc