"Accepted" status for issues
Hey Development, What about adding a "Accepted" status for issues, kind of in between "active" and "has a patch" - we recognize it's a bug, we're working to fix it, or we like this feature, we're going to implement it. What are your thoughts? Dmitri
On Sun, Mar 8, 2009 at 6:29 AM, Dmitri Gaskin <dmitrig01@gmail.com> wrote:
What about adding a "Accepted" status for issues, kind of in between "active" and "has a patch" - we recognize it's a bug, we're working to fix it, or we like this feature, we're going to implement it.
I felt the need for this before, but then realized that "accepted" == "active" and "assigned to someone". Sure, this combined approach does not allow you to filter for such issues as easy as just to look for a certain state. Gábor
Using a "New" status for newly created tickets is a common way to say that a ticket has not yet been reviewed for validity. I find it useful and use it in my ticket tracking systems. -- Kathleen Murtagh On Sun, Mar 8, 2009 at 12:36 AM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
On Sun, Mar 8, 2009 at 6:29 AM, Dmitri Gaskin <dmitrig01@gmail.com> wrote:
What about adding a "Accepted" status for issues, kind of in between "active" and "has a patch" - we recognize it's a bug, we're working to fix it, or we like this feature, we're going to implement it.
I felt the need for this before, but then realized that "accepted" == "active" and "assigned to someone". Sure, this combined approach does not allow you to filter for such issues as easy as just to look for a certain state.
Gábor
Quoting Dmitri Gaskin <dmitrig01@gmail.com>:
Hey Development,
What about adding a "Accepted" status for issues, kind of in between "active" and "has a patch" - we recognize it's a bug, we're working to fix it, or we like this feature, we're going to implement it.
What are your thoughts?
It belongs in an issue queue for the web maintainers. I would like for each project to be able to add or remove statuses to their liking but I don't have time to work a patch and it isn't as important as other items on the list. -- Earnie http://r-feed.com Make a Drupal difference and review core patches. -- http://for-my-kids.com/ -- http://www.4offer.biz/
There's already an issue open on d.o about re-organising the issue status settings - http://drupal.org/node/171350 Cheers, Stella On Sun, Mar 8, 2009 at 9:31 AM, Earnie Boyd <earnie@users.sourceforge.net>wrote:
Quoting Dmitri Gaskin <dmitrig01@gmail.com>:
Hey Development,
What about adding a "Accepted" status for issues, kind of in between "active" and "has a patch" - we recognize it's a bug, we're working to fix it, or we like this feature, we're going to implement it.
What are your thoughts?
It belongs in an issue queue for the web maintainers. I would like for each project to be able to add or remove statuses to their liking but I don't have time to work a patch and it isn't as important as other items on the list.
-- Earnie http://r-feed.com Make a Drupal difference and review core patches.
On Mar 8, 2009, at 6:31 AM, Earnie Boyd wrote:
I would like for each project to be able to add or remove statuses to their liking but I don't have time to work a patch and it isn't as important as other items on the list.
That'd be a pain for various reasons. For one thing, it'd be impossible to filter by status across projects if the set of possible values was different on each project. Basically, status would become just like component in the current issue queues, and I think that's a step in the wrong direction. On Mar 8, 2009, at 7:01 AM, Stella Power wrote:
There's already an issue open on d.o about re-organising the issue status settings - http://drupal.org/node/171350
I hoped to have time on the flight home to look at this closely, but was dealing with other things. My initial impression of that proposal (and what Earnie is saying above) is that we need *less* distinct status values, not more. For all the subtle, fine-grained stuff people keep wanting, that we should use issue tagging (or a separate "Status reason" vocabulary) instead. But, I'll reply with a more coherent counter-proposal at #171350 when I can. Cheers, -Derek (dww)
Quoting Derek Wright <drupal@dwwright.net>:
On Mar 8, 2009, at 6:31 AM, Earnie Boyd wrote:
I would like for each project to be able to add or remove statuses to their liking but I don't have time to work a patch and it isn't as important as other items on the list.
That'd be a pain for various reasons. For one thing, it'd be impossible to filter by status across projects if the set of possible values was different on each project. Basically, status would become just like component in the current issue queues, and I think that's a step in the wrong direction.
Thanks for the explanation Derek.
On Mar 8, 2009, at 7:01 AM, Stella Power wrote:
There's already an issue open on d.o about re-organising the issue status settings - http://drupal.org/node/171350
I hoped to have time on the flight home to look at this closely, but was dealing with other things. My initial impression of that proposal (and what Earnie is saying above) is that we need *less* distinct status values, not more. For all the subtle, fine-grained stuff people keep wanting, that we should use issue tagging (or a separate "Status reason" vocabulary) instead. But, I'll reply with a more coherent counter-proposal at #171350 when I can.
I really appreciate the work you do to keep project improving. It is one of the things that sets Drupal apart from some other projects. I just wish I had more time to help you. -- Earnie http://r-feed.com Make a Drupal difference and review core patches. -- http://for-my-kids.com/ -- http://www.4offer.biz/
I like the idea of managing my list with issue tags. We'd just need to be able to see them in the table at http://drupal.org/project/user, and filter by them. Is there an open issue for this? -tao Derek Wright wrote:
On Mar 8, 2009, at 6:31 AM, Earnie Boyd wrote:
I would like for each project to be able to add or remove statuses to their liking but I don't have time to work a patch and it isn't as important as other items on the list.
That'd be a pain for various reasons. For one thing, it'd be impossible to filter by status across projects if the set of possible values was different on each project. Basically, status would become just like component in the current issue queues, and I think that's a step in the wrong direction.
On Mar 8, 2009, at 7:01 AM, Stella Power wrote:
There's already an issue open on d.o about re-organising the issue status settings - http://drupal.org/node/171350
I hoped to have time on the flight home to look at this closely, but was dealing with other things. My initial impression of that proposal (and what Earnie is saying above) is that we need *less* distinct status values, not more. For all the subtle, fine-grained stuff people keep wanting, that we should use issue tagging (or a separate "Status reason" vocabulary) instead. But, I'll reply with a more coherent counter-proposal at #171350 when I can.
Cheers, -Derek (dww)
On Mar 9, 2009, at 9:52 AM, Tao Starbow wrote:
I like the idea of managing my list with issue tags. We'd just need to be able to see them in the table at http://drupal.org/project/ user, and filter by them. Is there an open issue for this?
Filter, yes: http://drupal.org/node/389096 Display: not so sure -- there are already complaints that the issue tables are way too wide as it is. I spoke with Mark Boulton in DC about redesigning the issue queue tables (something they spent 0 effort on during their original redesign efforts). It's a hard problem, and he said he wants to think about it more before making any specific recommendations to me and the other redesign implementors. So, for now, the idea is just that you'd be able to filter issues via an autocomplete text field, but the tags themselves on the issue wouldn't (yet) be displayed in the huge table. We'd add the tags later when we have a good plan for the whole experience. Cheers, -Derek (dww)
participants (7)
-
Derek Wright -
Dmitri Gaskin -
Earnie Boyd -
Gábor Hojtsy -
Kathleen Murtagh -
Stella Power -
Tao Starbow