spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artur Sukhenko <artur.sukhe...@gmail.com>
Subject Re: Can anyone edit JIRAs SPARK-19191 to SPARK-19202?
Date Fri, 13 Jan 2017 15:47:17 GMT
None of JIRA issues of range 19191 -19202 have Resolve/Close Issue button.

e.g. SPARK-19214 "Resolve Issue" button has link
https://issues.apache.org/jira/secure/WorkflowUIDispatcher.jspa?id=13034656&action=5&atl_token=
...
Meaning that this is something to do with *Workflow*  (action 5) (as it has
*WorkflowUIDispatcher*.*jspa* in the URI, which isn't present in any of the
SPARK-19202 links)
Thus I guess you or other Spark JIRA admin should tweak workflows e.g. Working
with workflows
<https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html>



On Fri, Jan 13, 2017 at 4:35 PM Sean Owen <sowen@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.sukhenko@gmail.com>
> wrote:
>
> Yes, I can resolve/close SPARK-19214 for example.
>
> On Fri, Jan 13, 2017 at 4:29 PM Sean Owen <sowen@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.sukhenko@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
> <https://confluence.atlassian.com/jirakb/how-to-edit-the-resolution-of-an-issue-313467778.html>
>
>
>
> On Fri, Jan 13, 2017 at 3:28 PM Sean Owen <sowen@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
>
> --
--
Artur Sukhenko

Mime
View raw message