Python HTML JavaScript CSS Shell
Latest commit 61db215 Sep 19, 2016 @davidread davidread committed on GitHub Merge pull request #67 from ckan/argv0-patch-1
Change redirects to use p.toolkit.redirect
Failed to load latest commit information.
bin Missing slash Apr 27, 2016
ckanext Fix one more redirect. Sep 19, 2016
.coveragerc Upgrade coveralls and exclude tests from coverage Nov 18, 2015
.gitignore some validator tests, ignore some ini files Mar 3, 2015
.travis.yml Upgrade coveralls and exclude tests from coverage Nov 18, 2015
LICENSE Tidy up readme for new home on ckan/ckanext-issues. Jan 11, 2016
dev-requirements.txt Add organization issues page and rename existing 'issues home' Jun 15, 2015
setup.cfg Initial commit May 11, 2011 Update version for good measure Jan 11, 2016
test-sqlite.ini Tighten up organization test to only lookin certain places. Also, get… Oct 1, 2015
test.ini Tighten up organization test to only lookin certain places. Also, get… Oct 1, 2015

Build Status Coverage Status

CKAN Issues Extension

This extension allows users to to report issues with datasets in a CKAN instance.

Current Status: Beta

What it does

Once installed and enabled, the issues extension will make available a per- dataset issue tracker.

The issue tracker user interface can be found at:


You can add an issue at:


Issues API

The issues extension also exposes its functionality as part of the standard CKAN Action API:




To install the plugin, enter your virtualenv and install the source::

pip install -e git+

Create the necessary tables:

paster --plugin=ckanext-issues issues init_db -c ckan.ini

This will also register a plugin entry point, so you now should be able to add the following to your CKAN .ini file::

ckan.plugins = issues

After you clear your cache and restart the web server, the Issues extension should be available.

Upgrade from older versions

When upgrading ckanext-issues from older code versions, you should run the issues upgrade command, in case there are any model migrations (e.g. 11th Jan 2016):

paster --plugin=ckanext-issues issues upgrade_db -c test-core.ini


To switch-on notifications, you should set the following option in your configuration, and all users in the group will get the email.

ckanext.issues.send_email_notifications = true

If you set max_strikes then users can 'report' a comment as spam/abuse. If the number of users reporting a particular comment hits the max_strikes number then it is hidden, pending moderation.

ckanext.issues.max_strikes = 2


By default, issues are enabled for all datasets. If you wish to restrict issues to specific datasets or organizations, you can use these config options:

ckanext.issues.enabled_for_datasets = mydataset1 mydataset2 ...
ckanext.issues.enabled_for_organizations = department-of-transport health-regulator

Alternatively, you can switch issues on/off for particular datasets by using an extra field:

'issues_enabled': True

and you can set the default for all the other datasets (without that extra field):

ckanext.issues.enabled_without_extra = false

For the extra field to work you must not set enabled_per_dataset or enabled_for_organizations options.


Please open an issue in the github issue tracker.


Normal requirements for CKAN Extensions (including an installation of CKAN and its dev requirements). Contributions welcome.

Testing with Postgres

To run full production tests on postgres run. These are the tests that the travis build will run

nosetests --ckan --with-pylons=test.ini -v --with-id ckanext/issues --with-coverage --cover-package=ckanext.issues --nologcapture

Testing with sqlite

For quick development tests run. --reset-db is necessary when running sqlite tests in memory

nosetests --reset-db --ckan --with-pylons=test-sqlite.ini -v --with-id ckanext/issues --with-coverage --cover-package=ckanext.issues --nologcapture