On Mon, May 1, 2017 at 3:44 PM, Allen Wittenauer <a...@effectivemachines.com> wrote:
> > > On May 1, 2017, at 2:27 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > > I believe I asked about this on dev-yetus a while back. I'd prefer that > the presence of the fix version be sufficient to indicate whether a JIRA is > included in a release branch. Yetus requires that the JIRA be resolved as > "Fixed" to show up, which is why we are in our current situation. > > We can't do this because Hadoop is the only one that I've seen > that sets Fix version at close time. Everyone else is setting fix version > in place of target (which is a custom field, iirc). > > Let's see if I can revive the discussion over on a yetus list/jira. I think it's easier to add a new flag to Yetus than changing the Hadoop JIRA workflow, and it seems like this issue is becoming more acute.
