QGIS Redmine (QGIS bug tracker): Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-06T12:37:48ZQGIS Issue Tracking
Redmine Bug report #22004 (Closed): Veetex tool not working on lines when style assignedhttps://issues.qgis.org/issues/220042019-05-06T12:37:48ZPeter Cornelissenpete.cornelissen@outlook.com
<p>I have a project with numerous layers. On a line or polygon shapefile layer without style, it woks fine, however, if I use the same shapefile and it has style associated with it (once it has been saved), the vertex editor does not work. Reproducible on my project with all shapefiles.</p> Bug report #21520 (Closed): Attribute forms - Cannot remove expression from a fieldhttps://issues.qgis.org/issues/215202019-03-08T10:16:36ZRoberto Marzocchiroberto.marzocchi@gter.it
<p>Adding an expression in a field of the attributes form it is impossible to remove it.</p>
<p>QGIS version 3.4.5 <br />OS Ubuntu 18.04</p> Bug report #21360 (Closed): gmail rejects mailhttps://issues.qgis.org/issues/213602019-02-23T19:56:55ZAnonymous
<p>gmail rejects mail</p> Bug report #21053 (Closed): QgsMapMouseEvent misses overload in python APIhttps://issues.qgis.org/issues/210532019-01-21T06:37:57ZBenjamin Jakimow
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>According to the API documentation, the QgsMapMouseEvent can be created using two different constructors <a class="external" href="https://qgis.org/pyqgis/master/gui/QgsMapMouseEvent.html">https://qgis.org/pyqgis/master/gui/QgsMapMouseEvent.html</a>.</p>
<p>However, the python API fails to call the second constructor defintion.</p>
<a name="Test"></a>
<h2 >Test<a href="#Test" class="wiki-anchor">¶</a></h2>
<pre>
from qgis.core import *
from qgis.gui import *
from qgis.PyQt.QtCore import *
from qgis.PyQt.QtGui import *
from qgis.testing import start_app, unittest
start_app()
class TestQgsFeature(unittest.TestCase):
def test_QgsMapMouseEvent(self):
canvas = QgsMapCanvas()
canvas.setFixedSize(300, 300)
pos = QPointF(0.5 * canvas.width(), 0.5 * canvas.height())
# this works
mouseEvent = QMouseEvent(QEvent.MouseButtonPress, pos, Qt.LeftButton, Qt.LeftButton, Qt.NoModifier)
qgsMouseEvent1 = QgsMapMouseEvent(canvas, mouseEvent)
self.assertIsInstance(qgsMouseEvent1, QgsMapMouseEvent)
# fails
qgsMouseEvent2 = QgsMapMouseEvent(
canvas,
QEvent.MouseButtonPress,
QPointF(0.5 * canvas.width(), 0.5 * canvas.height()),
Qt.LeftButton,
Qt.LeftButton,
Qt.NoModifier)
self.assertIsInstance(qgsMouseEvent2, QgsMapMouseEvent)
if __name__ == '__main__':
unittest.main()
</pre>
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<p>Windows 10 Education, 64-Bit<br />QGIS version 3.4.3-Madeira<br />QGIS code revision 2f64a3c4e7</p> Bug report #20366 (Closed): Missing 3.4.1 'Affected QGIS Version' when creating new issue in QGIS...https://issues.qgis.org/issues/203662018-11-05T13:07:02ZJonathan Willitts
<p>There is no option to select 'Affected QGIS version' 3.4.1 when creating new issues in the QGIS Application bug tracker</p> Bug report #19935 (Closed): Split tool changing the attributes of the new feature on QGIS 3.3https://issues.qgis.org/issues/199352018-09-25T00:50:59ZPhilipe Borbaphilipeborba@gmail.com
<p>Instead of the original behaviour of the split feature from previous QGIS (split and both parts getting the same attribute set), split tool creates a new one and does not get the original feature attribute.</p>
<p>The attached gif shows the described behaviour.</p>
<p>I'm running QGIS on MacOS Mojave with the following specs:</p>
<p>QGIS version: 3.3.0-Master<br />QGIS code revision: 9dd1406539<br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL/OGR: 2.3.1<br />Running against GDAL/OGR: 2.3.1<br />Compiled against GEOS: 3.6.3-CAPI-1.10.3<br />Running against GEOS: 3.6.3-CAPI-1.10.3 80c13047<br />PostgreSQL Client Version: 10.5<br />SpatiaLite Version: 4.3.0a<br />QWT Version: 6.1.3<br />QScintilla2 Version: 2.10.4<br />Compiled against PROJ: 520<br />Running against PROJ: 5.2.0</p> Bug report #19649 (Closed): Style loading issuehttps://issues.qgis.org/issues/196492018-08-20T12:43:54Zjoao esperidiaojoao.p2709@gmail.com
<p>Loading styles from .QML files fail when a style is stored into DB. If more than a style is stored into DB, it only changes through QGIS interface (does not work if it is managed by API).</p> Bug report #17834 (Closed): Processing Scripts don`t preserve utf 8 encodinghttps://issues.qgis.org/issues/178342018-01-10T12:18:51ZChristian Metzgerchristian.metzger@giz.de
<p>In QGIS 2.18.15 utf 8 encoding (Lao script) isn`t preserved when running a script. The same issue could be confirmed in QGIS 2.14.</p> Bug report #16658 (Closed): It is not possible to add watchers to an issue after it has been createdhttps://issues.qgis.org/issues/166582017-06-02T08:19:56ZRegis Haubourgregis.haubourg@oslandia.com
<p>Any idea why?</p> Feature request #16602 (Closed): enable sticky login (remember me)https://issues.qgis.org/issues/166022017-05-23T08:00:09ZSandro Santillistrk@kbt.io
<p>According to Jurgen there's a configuration in Redmine to enable showing a "remember me" checkbox on login, and it is (if I understood correctly) already enabled, but it does not show to me, as you can see in this screenshot:</p>
<p><img src="http://strk.kbt.io/tmp/qgis-signin.png" alt="" /></p> Bug report #16601 (Closed): commit references do not expandhttps://issues.qgis.org/issues/166012017-05-23T07:51:42ZSandro Santillistrk@kbt.io
<p>Take a look at this comment <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/15463#note-15" title="Layer "Scale dependent visibility" doesn't work anymore since 2.16 (Closed)">#15463-15</a></p>
<p>Some commits are found (see previous comments) while others are not.<br />Maybe redmine is not configured to fetch all branches ?</p> Bug report #16557 (Open): Default "Category" is blank, but cannot behttps://issues.qgis.org/issues/165572017-05-16T09:13:15ZSandro Santillistrk@kbt.io
<p>Filing tickets in this tracker requires picking a Category, but there's a single Category being "any" and it's not the default.<br />The default category is blank, which is invalid.</p>
<p>Please make "any" the default, if it has to stay, or allow blank Category...</p>
<p>NOTE: I'm assigning to Jurgen because I've been told it's Jurgen and Richard who worked on the upgrade, but Richard is not in the pull-down menu for Assignee...</p> Bug report #16556 (Closed): Commit log reference to tickets do not result in ticket updateshttps://issues.qgis.org/issues/165562017-05-16T09:11:26ZSandro Santillistrk@kbt.io
<p>Tickets are not updated to contain reference to commits which reference them.<br />Superceeds <a class="issue tracker-2 status-1 priority-4 priority-" href="https://issues.qgis.org/issues/3944" title="In-commit messages referring to tickets may be wrong (Open)">#3944</a> (which cannot be edited due to <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/16555" title=""Category cannot be blank" on editing old issues (Closed)">#16555</a>).</p> Bug report #16554 (Open): Issues summary misses "Support" requestshttps://issues.qgis.org/issues/165542017-05-16T09:04:51ZSandro Santillistrk@kbt.io
<p>The <a class="external" href="https://issues.qgis.org/projects/qgis-redmine">https://issues.qgis.org/projects/qgis-redmine</a> page shows a summary of issues, but only reports "Bug report" and "Feature request" kind of issues. This means the many "Support" issues are not summarized there.</p>
<p>While filing <strong>this</strong> issue I see that the "Tracker" selection box only shows "Bug report" and "Feature request" too, so maybe the existing tickets in the "Support" tracker are just form the previous deploy ?</p> Feature request #3944 (Open): In-commit messages referring to tickets may be wronghttps://issues.qgis.org/issues/39442011-06-05T01:49:14ZTim Suttontim@linfiniti.com
<p>We tried to preserve ticket numbers between trac and redmine. Unfortunately there were already a few hundred tickets lodged in redmine. So for maximum compatibility, the first few hundred trac tickets have now been assigned high ticket numbers, and the vast majority of tickets will resolve correctly on their original numbers.</p>