[Geoserver-devel] [Geotools-devel] Missing Jira issue creation emails

GeoServer GeoServer Developer
1

Also affects GeoServer: last Jira issue creation email was for GEOS-7875 and we are up to GEOS-7889.

On 07/12/16 13:26, Ben Caradoc-Davies wrote:

Hmm, I got this, so it looks like a Jira problem.

On 07/12/16 13:18, Ben Caradoc-Davies wrote:

This is a test of the mailing list. We have had no Jira issue creation
emails since GEOT-5579 and we are now up to GEOT-5590. So, mailing list
or Jira problem? If you are reading this, the mailing list is working.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

2

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.

On 07/12/16 13:26, Ben Caradoc-Davies wrote:

Hmm, I got this, so it looks like a Jira problem.

On 07/12/16 13:18, Ben Caradoc-Davies wrote:

This is a test of the mailing list. We have had no Jira issue creation
emails since GEOT-5579 and we are now up to GEOT-5590. So, mailing list
or Jira problem? If you are reading this, the mailing list is working.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

3

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 <ben@anonymised.com> wrote:

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.

On 07/12/16 13:26, Ben Caradoc-Davies wrote:

Hmm, I got this, so it looks like a Jira problem.

On 07/12/16 13:18, Ben Caradoc-Davies wrote:

This is a test of the mailing list. We have had no Jira issue creation
emails since GEOT-5579 and we are now up to GEOT-5590. So, mailing list
or Jira problem? If you are reading this, the mailing list is working.

Kind regards,

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi

GeoTools-Devel mailing list
GeoTools-Devel@anonymised.com66…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313

fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

4

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 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 <ben@anonymised.com> wrote:

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.

On 07/12/16 13:26, Ben Caradoc-Davies wrote:

Hmm, I got this, so it looks like a Jira problem.

On 07/12/16 13:18, Ben Caradoc-Davies wrote:

This is a test of the mailing list. We have had no Jira issue creation
emails since GEOT-5579 and we are now up to GEOT-5590. So, mailing list
or Jira problem? If you are reading this, the mailing list is working.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

------------------------------------------------------------
------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

5

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 <ben@anonymised.com4191…> wrote:

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 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 <ben@anonymised.com> wrote:

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.

On 07/12/16 13:26, Ben Caradoc-Davies wrote:

Hmm, I got this, so it looks like a Jira problem.

On 07/12/16 13:18, Ben Caradoc-Davies wrote:

This is a test of the mailing list. We have had no Jira issue creation
emails since GEOT-5579 and we are now up to GEOT-5590. So, mailing list
or Jira problem? If you are reading this, the mailing list is working.

Kind regards,

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi

GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313

fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

6

On Mon, Dec 12, 2016 at 4:25 PM, Andrea Aime <andrea.aime@anonymised.com>
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
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

7

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'd suggest
to do the same.

Cheers
Andrea

On Sat, Dec 10, 2016 at 6:55 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

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 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 <ben@anonymised.com>
wrote:

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.

On 07/12/16 13:26, Ben Caradoc-Davies wrote:

Hmm, I got this, so it looks like a Jira problem.

On 07/12/16 13:18, Ben Caradoc-Davies wrote:

This is a test of the mailing list. We have had no Jira issue creation
emails since GEOT-5579 and we are now up to GEOT-5590. So, mailing
list
or Jira problem? If you are reading this, the mailing list is working.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

------------------------------------------------------------
------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand