QGIS Issue Tracking

2018-02-02

07:47 PM QGIS Application Bug report #16524 (Open): Processing/geoprocessing operations failing in 2.18 with memory layers

Since my new ticket #18006 related to this was rejected. Here is the additional information that I wrote in that tick...

07:47 PM QGIS Application Bug report #16524 (Open): Processing/geoprocessing operations failing in 2.18 with memory layers

Since my new ticket #18006 related to this was rejected. Here is the additional information that I wrote in that tick...

07:47 PM QGIS Application Bug report #16524 (Open): Processing/geoprocessing operations failing in 2.18 with memory layers

Since my new ticket #18006 related to this was rejected. Here is the additional information that I wrote in that tick...

07:47 PM QGIS Application Bug report #16524 (Open): Processing/geoprocessing operations failing in 2.18 with memory layers

Since my new ticket #18006 related to this was rejected. Here is the additional information that I wrote in that tick...

07:47 PM QGIS Application Bug report #16524 (Open): Processing/geoprocessing operations failing in 2.18 with memory layers

Since my new ticket #18006 related to this was rejected. Here is the additional information that I wrote in that tick...

07:42 PM QGIS Application Bug report #18007: QGIS 3 Vector data corruption when Adding a Point Feature

The issue is resolved.

07:40 PM QGIS Application Bug report #17878: QGIS 3 Vector Layer Fields Garbled when Clicking the Toggle Editing Icon

That seems to have resolved the issue.

2018-01-30

09:28 PM QGIS Application Bug report #17878: QGIS 3 Vector Layer Fields Garbled when Clicking the Toggle Editing Icon

Here is the new ticket #18007

09:27 PM QGIS Application Bug report #18007 (Closed): QGIS 3 Vector data corruption when Adding a Point Feature

Attached is a sample data set to illustrate the problem. This was broken off as a separate issue from #17878.
To c...

09:05 PM QGIS Application Bug report #18006 (Rejected): Geoprocessing Tools Fail with Memory Layers in QGIS 2.18

I have attached a python script to illustrate this bug. I posted this problem on the qgis-developer group and Richard...