I can't see the resolve button either - Maybe we can forward this to Apache Infra and see if they can close these issues ?
Shivaram On Fri, Jan 13, 2017 at 6:35 AM, Sean Owen <so...@cloudera.com> wrote: > Yes, I'm asking about a specific range: 19191 - 19202. These seem to be the > ones created during the downtime. Most are duplicates or incomplete. > > On Fri, Jan 13, 2017 at 2:32 PM Artur Sukhenko <artur.sukhe...@gmail.com> > wrote: >> >> Yes, I can resolve/close SPARK-19214 for example. >> >> On Fri, Jan 13, 2017 at 4:29 PM Sean Owen <so...@cloudera.com> wrote: >>> >>> Do you see a button to resolve other issues? you may not be able to >>> resolve any of them. I am a JIRA admin though, like most other devs, so >>> should be able to resolve anything. >>> >>> Yes, I certainly know how resolving issues works but it's suddenly today >>> only working for a subset of issues, and I bet it's related to the JIRA >>> problems this week. >>> >>> On Fri, Jan 13, 2017 at 1:55 PM Artur Sukhenko <artur.sukhe...@gmail.com> >>> wrote: >>>> >>>> Hello Sean, >>>> >>>> I can't resolve SPARK-19191 to SPARK-19202 too. I believe this is a bug. >>>> Here is JIRA Documentation which states this or similar problems - How >>>> to Edit the Resolution of an Issue >>>> >>>> >>>> >>>> On Fri, Jan 13, 2017 at 3:28 PM Sean Owen <so...@cloudera.com> wrote: >>>>> >>>>> Looks like the JIRA maintenance left a bunch of duplicate JIRAs, from >>>>> SPARK-19191 to SPARK-19202. For some reason, I can't resolve these issues, >>>>> but I can resolve others. Does anyone else see the same? >>>>> >>>>> I know SPARK-19190 was similarly borked but closed by its owner. >>>> >>>> -- >>>> -- >>>> Artur Sukhenko >> >> -- >> -- >> Artur Sukhenko --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
