cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Braden Shepherdson <bra...@chromium.org>
Subject Re: Proposal: Change JIRA to have bugs as "unassigned" by default
Date Thu, 19 Sep 2013 14:33:15 GMT
Does JIRA have the "New" state for a bug? That might be another way to
signal whether the bug has ever been looked at, if they begin as New and
then we change them to Accepted or whatever it's called.

Braden


On Thu, Sep 19, 2013 at 10:29 AM, Andrew Grieve <agrieve@chromium.org>wrote:

> Okay, I've made the change. Let's try it out :)
>
> I think start/stop is good if you've actually started working on something,
> but it's different from "this new bug has been looked at by someone".
>
>
>
>
> On Thu, Sep 19, 2013 at 2:51 AM, Anis KADRI <anis.kadri@gmail.com> wrote:
>
> > What about the start/stop progress?
> >
> > On Wed, Sep 18, 2013 at 9:03 PM, Ian Clelland <iclelland@chromium.org>
> > wrote:
> > > +1
> > >
> > > Also, if you are a component "owner", it's pretty simple in JIRA to
> add a
> > > dashboard widget that shows you all unassigned bugs in your component.
> > >
> > > Ian
> > >
> > >
> > > On Wed, Sep 18, 2013 at 11:49 PM, Joe Bowser <bowserj@gmail.com>
> wrote:
> > >
> > >> +1
> > >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message