workflow at redmine.org
Added by John Pankowicz almost 9 years ago
I made a chart of number of issues for status vs tracker at Redmine.org. This is what I found:
(tracker/status) new -- needs-feedback -- confirmed - resolved - reopened - open -- closed - total
feature --------- 2798 - 17 ---------------- 1 ----------- 22 ------- 49 --------- 2887 -- 2778 --- 5665
defect ---------- 989 -- 107 --------------- 38 ---------- 19 ------- 36 --------- 1189 -- 6148 --- 7337
patch ----------- 405 -- 14 ---------------- 0 ------------ 5 -------- 4 ---------- 426 --- 1728 --- 2154
totals ---------- 4192 --138 --------------- 39 ---------- 46 ------- 89 --------- 4502 -- 10654 -- 15156
Almost all issues appear to go directly from "new" to "closed". They don't go through any other stages. What this tells us is that there are really only TWO types of status for all trackers at redmine.org. Issues are either OPEN or CLOSED. But we know that can't really be true, since a lot of good work gets done on Redmine. So my question is - How does anyone know what the actual status of an issue really is. Which issues are "accepted to be worked on"? Which issues are "in the process of being worked on"? Which are "being tested"? And then, which have either passed or failed testing, before being finally closed?
The main reason that I am asking this is because I am trying to configure Redmine for an open source project. I am trying to figure out we can keep track of this, if we are not using the issue status to do this. And if I wanted to contribute to Redmine development, how would I know which of the 2,798 "new features" stands any chance of being implemented?