Andrea,
it looks like the problem was fixed in the last 24 hours.
Kind regards,
Ben.
On 13/12/16 04:25, Andrea Aime wrote:
> So,
> looks like it's a known but with no workaround:
>
> https://jira.atlassian.com/browse/JRA-63395
>
> I've been told to vote for it... if you have an account there, I'
On Mon, Dec 12, 2016 at 4:25 PM, Andrea Aime
wrote:
> So,
> looks like it's a known but with no workaround:
>
Known... bug! (and no buts!)
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Ing. Andrea Aime
@geowolf
Tech
So,
looks like it's a known but with no workaround:
https://jira.atlassian.com/browse/JRA-63395
I've been told to vote for it... if you have an account there, I'd suggest
to do the same.
Cheers
Andrea
On Sat, Dec 10, 2016 at 6:55 PM, Ben Caradoc-Davies
wrote:
> Thanks, Andrea.
>
> I see "You
Thanks, Andrea.
I see "You do not have permission to view this request." but at least
the problem is reported.
Kind regards,
Ben.
On 11/12/16 04:42, Andrea Aime wrote:
> Hi,
> I've create a ticket on Atlassian support site, not sure if it's visible by
> everybody, logged in users from the same
Hi,
I've create a ticket on Atlassian support site, not sure if it's visible by
everybody, logged in users from the same org, or just me:
https://support.atlassian.com/servicedesk/customer/portal/23/JST-242860
Cheers
Andrea
On Wed, Dec 7, 2016 at 1:49 AM, Ben Caradoc-Davies wrote:
> I checked
I checked and all the notifications appear to be correctly configured. I
think we need to contact Atlassian Cloud support, but I do not know how.
On 07/12/16 13:32, Ben Caradoc-Davies wrote:
> Also affects GeoServer: last Jira issue creation email was for GEOS-7875
> and we are up to GEOS-7889.
>
