File: BUGS

package info (click to toggle)
qgis 2.18.28+dfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 1,007,948 kB
  • sloc: cpp: 671,774; python: 158,539; xml: 35,690; ansic: 8,346; sh: 1,766; perl: 1,669; sql: 999; yacc: 836; lex: 461; makefile: 292
file content (31 lines) | stat: -rw-r--r-- 1,438 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
´╗┐Help I think I found a bug!
---------------------------

If you find a bug in QGIS, you can search for it 

http://hub.qgis.org/search/index/quantum-gis/issues

If you can't find an exisitng ticket, report it using the QGIS ticket/bug database at:

http://hub.qgis.org/projects/quantum-gis/issues/new


Some hints about when you should file a bug:


 - Just because a bug is filed doesn't always mean we can or will fix it.
   Sometimes people ask for things that will require many man hours to do and
   offer little reward to work ratio benefit when compared to the other issues
   in the queue. Also some things are simply not fixable due to whatever
   technical reason.
 - Sometimes we don't fix a bug because the user's vision of how QGIS should
   behave doesn't match ours. Hey we are all humans it can happen...
 - Always check that your bug has not already been filed by someone else since
   dealing with duplicate tickets causes a lot of time wasting.
 - Always provide contact details and make sure you are subscribed to the
   ticket entry (either by adding yourself to CC field or by logging in before
   filing the ticket).
 - Don't be offended if we don't see tickets as having the same priority as you
   do. While we appreciate it's inconvenient if some issue prevents you doing
   your work, we need to take the big picture view of things and focus on
   things that affect the largest proportion of our user base.