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 <[email protected]> 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 <[email protected]> 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 > > >
