Re: [GNC-dev] BZ migration detail

2018-06-30 Thread David Carlson
Thank you. On Sat, Jun 30, 2018 at 5:59 PM, John Ralls wrote: > David, > > No, the status is actually "RESOLVED" and comes with a bunch of > resolutions like "FIXED", "WONTFIX", "NOTGNUCASH", and "NOTABUG". > > There's also a little-used status, "VERIFIED", that's intended to be set > after so

Re: [GNC-dev] BZ migration detail

2018-06-30 Thread John Ralls
David, No, the status is actually "RESOLVED" and comes with a bunch of resolutions like "FIXED", "WONTFIX", "NOTGNUCASH", and "NOTABUG". There's also a little-used status, "VERIFIED", that's intended to be set after someone has checked that the "FIXED" resolution really is. Regards, John Ralls

Re: [GNC-dev] BZ migration detail

2018-06-30 Thread David Carlson
I just did not mention all the others. I was not sure about that one because it looked like it should have been closed, but it looked like it wasn't, and I thought that closed bugs might not be migrated. Not sure about that, though. So there is not a status called Closed? David C On Sat, Jun 3

Re: [GNC-dev] BZ migration detail

2018-06-30 Thread John Ralls
> On Jun 30, 2018, at 1:54 PM, David Carlson > wrote: > > I am not sure if this is supposed to happen this way or not, so I will > simply let you know about this observation. > > I received a notice that https://bugs.gnucash.org/show_bug.cgi?id=598788 > had been migrated. That bug was resol

[GNC-dev] BZ migration detail

2018-06-30 Thread David Carlson
I am not sure if this is supposed to happen this way or not, so I will simply let you know about this observation. I received a notice that https://bugs.gnucash.org/show_bug.cgi?id=598788 had been migrated. That bug was resolved about 5 years ago for release 2.6 but apparently not closed. Since