Skip to content
This repository has been archived by the owner on Aug 24, 2019. It is now read-only.

Assign priorities #87

Open
webknjaz opened this issue Feb 7, 2016 · 5 comments
Open

Assign priorities #87

webknjaz opened this issue Feb 7, 2016 · 5 comments

Comments

@webknjaz
Copy link
Member

webknjaz commented Feb 7, 2016

I've created a bunch of labels for specifying issue priorities from P1 (urgent, highest priority level) to P5 (give up on task and never think of it anymore).
Plz iterate through all tickets and assign them with corresponding priority.

@webknjaz
Copy link
Member Author

webknjaz commented Feb 7, 2016

@cleac @anxolerd @gora050 you may use those as well

@webknjaz
Copy link
Member Author

ping

@anxolerd
Copy link
Contributor

I'll take a look into this

@anxolerd
Copy link
Contributor

Well, as for this.

If we use waffle as a task dashboard then let's consider the following convention:

  1. Task are grouped in columns.
    • Backlog -- any opened issues, which require requirements validation
    • On hold -- postponed. Do these only if current ready for dev column is empty
    • Ready for dev -- actual task which should be done
    • In dev -- tasks which are in progress now
    • Done -- task is finished
  2. Tasks in columns are sorted according to their priority. The most urgent and important tasks are on the top of the column, the least important are at the column's bottom

Such convention will allow us to avoid having issues with thousands of labels and still have them all organized.

/cc @webknjaz @bluebirrrrd @cleac

@webknjaz
Copy link
Member Author

ok, but labeling should still be considered.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants