Please give a once-over on the JIRA migration

[Mike Percy <mp...@apache.org>]

Hi devs,
I'm working with the admins of issues.cloudera.org to add an HTTP redirect
for the Kudu project to issues.apache.org, but I want to make sure we have
caught and corrected any migration issues before we put the redirect into
place. Please take a moment to look at a few of your favorite issues on
https://issues.cloudera.org/browse/KUDU vs
https://issues.apache.org/jira/browse/KUDU and let me know if you think
anything was missed in the migration. I'm planning on ask them to activate
the redirect tomorrow.

Thanks!
Mike

Re: Please give a once-over on the JIRA migration

[Adar Dembo <ad...@cloudera.com>]

I did a spot check of some of the umbrella JIRAs I filed in the past and
they seem OK on the Apache JIRA.

On Mon, Feb 29, 2016 at 10:39 AM, Todd Lipcon <to...@cloudera.com> wrote:

> I've been using the apache JIRA the last few days and it has seemed fine to
> me. Thanks
>
> -Todd
>
> On Mon, Feb 29, 2016 at 10:32 AM, Mike Percy <mp...@apache.org> wrote:
>
> > Hi devs,
> > I'm working with the admins of issues.cloudera.org to add an HTTP
> redirect
> > for the Kudu project to issues.apache.org, but I want to make sure we
> have
> > caught and corrected any migration issues before we put the redirect into
> > place. Please take a moment to look at a few of your favorite issues on
> > https://issues.cloudera.org/browse/KUDU vs
> > https://issues.apache.org/jira/browse/KUDU and let me know if you think
> > anything was missed in the migration. I'm planning on ask them to
> activate
> > the redirect tomorrow.
> >
> > Thanks!
> > Mike
> >
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Re: Please give a once-over on the JIRA migration

[Todd Lipcon <to...@cloudera.com>]

I've been using the apache JIRA the last few days and it has seemed fine to
me. Thanks

-Todd

On Mon, Feb 29, 2016 at 10:32 AM, Mike Percy <mp...@apache.org> wrote:

> Hi devs,
> I'm working with the admins of issues.cloudera.org to add an HTTP redirect
> for the Kudu project to issues.apache.org, but I want to make sure we have
> caught and corrected any migration issues before we put the redirect into
> place. Please take a moment to look at a few of your favorite issues on
> https://issues.cloudera.org/browse/KUDU vs
> https://issues.apache.org/jira/browse/KUDU and let me know if you think
> anything was missed in the migration. I'm planning on ask them to activate
> the redirect tomorrow.
>
> Thanks!
> Mike
>



-- 
Todd Lipcon
Software Engineer, Cloudera

Re: Please give a once-over on the JIRA migration

[Mike Percy <mp...@apache.org>]

Sorry to resurrect this old thread. Just wanted to follow up and say the
above things have been fixed. The INFRA JIRA was
https://issues.apache.org/jira/browse/INFRA-11397

Note that we couldn't figure out how to reorder the Unreleased / Released
versions in the Target Version/s dropdown menu. The rest of the workflow
changes are done, though.

Mike

On Tue, Mar 1, 2016 at 10:00 AM, Dave Wang <ds...@cloudera.com> wrote:

> +1.  I find In Review more informative than In Progress (which can vary
> depending on what you define as "in progress"), but if we're going to
> address one issue, we might as well add both at the same time.
>
> - Dave
>
> On Tue, Mar 1, 2016 at 9:59 AM, Todd Lipcon <to...@cloudera.com> wrote:
>
> > On Tue, Mar 1, 2016 at 9:41 AM, Mike Percy <mp...@cloudera.com> wrote:
> >
> > >
> > >  - Add In Progress workflow status
> > >  - Add In Review workflow status
> > >
> > > For the workflow items, I don't really use them much, personally, but
> if
> > > others want them to be added back in then please speak up.
> >
> >
> > I was a fan of the 'In Review' status -- helpful especially towards the
> end
> > of a release when it's useful to know when things are 'almost done' vs
> > still under fairly active dev.
> >
> > -Todd
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera
> >
>

Re: Please give a once-over on the JIRA migration

[Dave Wang <ds...@cloudera.com>]

+1.  I find In Review more informative than In Progress (which can vary
depending on what you define as "in progress"), but if we're going to
address one issue, we might as well add both at the same time.

- Dave

On Tue, Mar 1, 2016 at 9:59 AM, Todd Lipcon <to...@cloudera.com> wrote:

> On Tue, Mar 1, 2016 at 9:41 AM, Mike Percy <mp...@cloudera.com> wrote:
>
> >
> >  - Add In Progress workflow status
> >  - Add In Review workflow status
> >
> > For the workflow items, I don't really use them much, personally, but if
> > others want them to be added back in then please speak up.
>
>
> I was a fan of the 'In Review' status -- helpful especially towards the end
> of a release when it's useful to know when things are 'almost done' vs
> still under fairly active dev.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Re: Please give a once-over on the JIRA migration

[Todd Lipcon <to...@cloudera.com>]

On Tue, Mar 1, 2016 at 9:41 AM, Mike Percy <mp...@cloudera.com> wrote:

>
>  - Add In Progress workflow status
>  - Add In Review workflow status
>
> For the workflow items, I don't really use them much, personally, but if
> others want them to be added back in then please speak up.


I was a fan of the 'In Review' status -- helpful especially towards the end
of a release when it's useful to know when things are 'almost done' vs
still under fairly active dev.

-Todd
-- 
Todd Lipcon
Software Engineer, Cloudera

Re: Please give a once-over on the JIRA migration

[Mike Percy <mp...@cloudera.com>]

Good catch, JD. I also noticed that Fix Version is not required when we
mark a jira Resolved, and that In Progress and In Review are no longer
workflow options.

Since we haven't found any more missing data, let's go ahead and install
the redirect today, and I'll file an ASF infra ticket to address these
other more subtle concerns.

Here is the list I have right now for that ticket to be filed:

- Find out if Unreleased versions can precede Released versions on Target
Version
- Require Fix Version to be set when marking an issue Resolved

Maybe fix:

 - Add In Progress workflow status
 - Add In Review workflow status

For the workflow items, I don't really use them much, personally, but if
others want them to be added back in then please speak up. Also, please
bring up any additional complaints so I can file one big ticket that
includes all of our desired changes.

Thanks,
Mike

On Tue, Mar 1, 2016 at 7:32 PM, Jean-Daniel Cryans <jd...@apache.org>
wrote:

> I think the target version is slightly misconfigured. It suggests released
> version on top instead of unreleased versions.
>
> On Mon, Feb 29, 2016 at 10:32 AM, Mike Percy <mp...@apache.org> wrote:
>
> > Hi devs,
> > I'm working with the admins of issues.cloudera.org to add an HTTP
> redirect
> > for the Kudu project to issues.apache.org, but I want to make sure we
> have
> > caught and corrected any migration issues before we put the redirect into
> > place. Please take a moment to look at a few of your favorite issues on
> > https://issues.cloudera.org/browse/KUDU vs
> > https://issues.apache.org/jira/browse/KUDU and let me know if you think
> > anything was missed in the migration. I'm planning on ask them to
> activate
> > the redirect tomorrow.
> >
> > Thanks!
> > Mike
> >
>

Re: Please give a once-over on the JIRA migration

[Jean-Daniel Cryans <jd...@apache.org>]

I think the target version is slightly misconfigured. It suggests released
version on top instead of unreleased versions.

On Mon, Feb 29, 2016 at 10:32 AM, Mike Percy <mp...@apache.org> wrote:

> Hi devs,
> I'm working with the admins of issues.cloudera.org to add an HTTP redirect
> for the Kudu project to issues.apache.org, but I want to make sure we have
> caught and corrected any migration issues before we put the redirect into
> place. Please take a moment to look at a few of your favorite issues on
> https://issues.cloudera.org/browse/KUDU vs
> https://issues.apache.org/jira/browse/KUDU and let me know if you think
> anything was missed in the migration. I'm planning on ask them to activate
> the redirect tomorrow.
>
> Thanks!
> Mike
>