QGIS Redmine (QGIS bug tracker): Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2017-10-25T10:58:11ZQGIS Issue Tracking
Redmine Feature request #17329 (Open): Send a notification from discussion I have contributed tohttps://issues.qgis.org/issues/173292017-10-25T10:58:11ZHarrissou Santanna
<p>In the user profile, you can choose different configuration to get notifications from discussions. <br />I think that there's a missing one (or at least, I am missing one);<br />I am not interested in getting notifications from all active discussions but I would be interested in feedbacks from discussion I had contributed to (created, commented). The only option I can find now is to add myself as "watching those discussions", step that I often forget (and later, it's not easy to find/remember the discussions you were part of because no notification is available).</p>
<p>Couldn't we consider that as soon as someone participates to a discussion, he's watching it and hence, according to his preferences, send notifications from that discussion? Or add a new option "discussion I commented" (needs to see how it could overlap/include any other option)?</p> Feature request #14218 (Open): ticket creator can't change "Affected Version"https://issues.qgis.org/issues/142182016-02-02T08:20:59ZD. Hiepler
<p>I created <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/14217" title="Segfault on QgsMapCanvas() creation (Closed)">#14217</a> and can't seem to be able to edit the Affected Version, just the "Target Version".</p> Feature request #10325 (Open): Redmine searches: add option to hide closed ticketshttps://issues.qgis.org/issues/103252014-05-22T01:55:38ZPaolo Cavallinicavallini@faunalia.it
<p>When searching on this Redmine, all tickets are shown, also closed ones. This adds a lot of confusion, and should be avoided.</p>
<p>Unsure where this ticket belongs to, if it's inappropriate here please tell me where, and I'll move it.</p> Feature request #8744 (Open): Allow regular users to edit the contents and title of bug and featu...https://issues.qgis.org/issues/87442013-10-01T08:13:34ZFilipe Dias
<p>Allow regular users to edit the contents and title of bug and feature requests.</p> Feature request #6570 (Open): References to commits in SEXTANTE trackerhttps://issues.qgis.org/issues/65702012-10-25T04:26:23ZAlexander Bruy
<p>Is it possible to enable references to commits (commit:sha_code) in SEXTANTE project?</p> Feature request #5414 (Open): no "New project" link in "User Plugins"https://issues.qgis.org/issues/54142012-04-19T03:04:13ZEtienne Tourigny
<p>The instructions for adding a new plugin (at <a class="external" href="http://plugins.qgis.org/">http://plugins.qgis.org/</a>) say to register a new plugin at <a class="external" href="https://issues.qgis.org/projects/qgis-user-plugins">https://issues.qgis.org/projects/qgis-user-plugins</a> , however this page does not include a "New project" link.</p>
<p>The work-around is to go to the root project page (<a class="external" href="https://issues.qgis.org/projects">https://issues.qgis.org/projects</a>) and create a new top-level project, which someone will move under "User Plugins" project.</p>
<p>This is confusing because<br />1) No "New project" link on the page where it is expected<br />2) Author can hesitate to create a new top-level project (as happened to me)</p>
<p>The solution is to allow all registered user to create subprojects of "User Plugins".</p>
<p>For my own project (Loop Visible Layers), I can create a subproject (because I am manager) and I can also set it as a subproject of "User Plugins" (but I'm not sure this option was available when I created it initially or appeared after someone made my project a subproject or "User Plugins").</p>
<p>This is a duplicate of bug <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/5408" title="plugin registration confusing - no "New project" link (Closed)">#5408</a> in django tracker. In the meantime I have updated the documentation at <a class="external" href="http://plugins.qgis.org/">http://plugins.qgis.org/</a> to create a new project and make it a subproject of "User Plugins".</p> Feature request #5149 (Open): Users can't close their issues on plugin projectshttps://issues.qgis.org/issues/51492012-03-09T19:57:56ZAlister Hood
<p>User are able to close issues they have opened on the QGIS desktop project. But they are unable to close issues they have opened on a plugin project.<br />Is this intended? Or do the owners of each plugin project have control of this?</p> Feature request #4916 (Open): [CLEAN URLS] Project name in project issueshttps://issues.qgis.org/issues/49162012-01-30T06:16:16ZSandro Santillistrk@kbt.io
<p>While opening this ticket I am at:</p>
<pre><code><a class="external" href="https://issues.qgis.org/projects/qgis-redmine/issues/new">https://issues.qgis.org/projects/qgis-redmine/issues/new</a></code></pre>
<p>But when I'll submit I'll be redirected to something like</p>
<pre><code>#1234</code></pre>
<p>I would expect instead:</p>
<pre><code><a class="external" href="https://issues.qgis.org/projects/qgis-redmine/issues/1234">https://issues.qgis.org/projects/qgis-redmine/issues/1234</a></code></pre> Feature request #4809 (Open): Formatting of the main plugin page(s)https://issues.qgis.org/issues/48092012-01-13T23:42:28ZPaolo Cavallinicavallini@faunalia.it
<p>The page:<br /><a class="external" href="https://issues.qgis.org/projects/qgis-user-plugins">https://issues.qgis.org/projects/qgis-user-plugins</a><br />lists all the plugins, without interruptions, whereas the page:<br /><a class="external" href="https://issues.qgis.org/projects">https://issues.qgis.org/projects</a><br />has a nicer list, with a short description.<br />Would it be possible to move (or echo) the list on the first page?<br />Also, each plugin in the list of the second page should be more clearly<br />separated from the following one.</p> Feature request #4677 (Open): Add "QGIS Version" fieldhttps://issues.qgis.org/issues/46772011-12-19T07:44:06ZAlexander Bruy
<p>There is a "Target Version" field in ticket metadata which interpreted as "Milestone". But there is no field where reporter can set used QGIS version. This makes tracking bugs a bit complex because developers don't know in which QGIS version this bug present.</p>
<p>Ideally this field should be mandatory and allow multiple values, because several version can be affected by bug.</p> Feature request #4264 (Feedback): Resolved issues should not appear on the default listhttps://issues.qgis.org/issues/42642011-09-05T02:00:05ZPaolo Cavallinicavallini@faunalia.it
<p>The default view lists open tickets, which include Resolved items, which seems inappropriate.</p> Feature request #4263 (Feedback): Redundant, confusing information?https://issues.qgis.org/issues/42632011-09-05T01:59:24ZPaolo Cavallinicavallini@faunalia.it
<p>In redmine, it is possible to have a ticket that is classified as Resolution:Invalid<br />(or fixed, etc.), and Status:New (instead of Closed). This is meaningless to me, and<br />causes confusion (we have many tickets that appear open, and are in fact closed. I<br />think the field resolution is useless, as the same info could be put on Status.</p> Feature request #4067 (Open): Voting support on issueshttps://issues.qgis.org/issues/40672011-07-10T14:01:17ZNathan Woodrow
<p>I think it would give devs a good indication how much support there is for a idea or how many people want a bug fixed. Not that it should be the only driver but it's still a handy metric to know.</p>
<p>There seems to be a few Redmine voting plugins floating around the net, I think using one on qgis issue list would be a good idea.</p> Feature request #3957 (Open): New tickets notifications are not sent to IRC #QGIShttps://issues.qgis.org/issues/39572011-06-05T23:18:42ZGiovanni Manghigiovanni.manghi@gmail.com
<p>Subject says it all</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>