logo

RedmineKanban

Login

66 questions

All questions

  • Yes. After purchase, you can use the purchased plugin version without a time limit. Updates and technical support are included for 12 months from the purchase date. After this period ends, you can continue using the already installed plugin version or renew the license to receive new updates and support. You can manage your license in your account: redmine-kanban.com/login. You can also email us at [email protected].

  • Select a plugin on the /plugins page and click "Buy" on the product page. You will proceed to checkout, where you can apply a promo code and see the final price. For purchase questions, contact [email protected].

  • This depends on the license type you choose. A temporary non-public installation for testing or development is allowed, provided it is removed after testing is complete. If you need the plugin on multiple Redmine instances, email [email protected] to find a suitable license.

  • Purchased plugins and available updates can be downloaded from your account. Sign in at redmine-kanban.com/login using the email address provided at purchase. If you cannot sign in, email [email protected].

  • Yes. To change the email address associated with your account, email [email protected] and provide your current and new addresses.

  • Yes. If plugins were purchased using different email addresses, email [email protected]. We will help merge eligible purchases into one account to simplify access to downloads and updates.

  • Updates are available during the update period included in your license. To continue receiving updates after this period ends, sign in to your account at redmine-kanban.com/login and renew your license, or email [email protected].

  • Yes. We can issue an invoice for a company. Send your company details and purchase request to [email protected] or use the contacts page: /contacts.

  • Yes. For legal entity purchases, we can prepare the required documents depending on the payment method and accepted document workflow. Email [email protected] with your company details and a list of required documents.

  • Yes. The Kanban Board documentation updated on January 21, 2026 lists compatibility with Redmine 5.0–6.1. Supported versions may change in future plugin releases, so before purchasing or updating, check the current documentation at /documentation/kanbanBoard or email [email protected].

  • We aim to support the latest major Redmine version and the two previous major versions. Supported versions may vary by plugin release. Check current compatibility on the Checklists page: /plugins/checklists or email [email protected] before purchasing or updating.

  • Supported Redmine versions depend on the specific plugin and its release. We aim to support the latest major Redmine version and the two previous major versions. Check compatibility on the relevant plugin page: /plugins or email [email protected] before purchasing or updating.

  • Yes, the Checklists and Kanban plugins work in a subdirectory.

  • Compatibility with Easy Redmine depends on its version, configuration, and whether custom plugins can be installed. Verify compatibility in your environment before purchasing, or email [email protected] with your Easy Redmine version and the plugin you need.

  • Email [email protected] with Redmine and Ruby versions, plugin names and versions, a list of installed plugins, browser name and version, screenshots, browser console errors, Network tab details, relevant Redmine log excerpts, and exact steps to reproduce the issue.

  • Place the plugin folder directly in the Redmine plugins/ directory. For Redmine Kanban, use the redmine_kanban folder and run bundle exec rake redmine:plugins:migrate RAILS_ENV=production NAME=redmine_kanban from the Redmine root directory. Folder names and migration commands for other plugins may differ, so follow the documentation for the plugin downloaded from your account: redmine-kanban.com/login.

  • This usually means the plugin folder is in the wrong directory or has the wrong name. Verify that the folder is placed directly inside plugins/, confirm the expected name in the installation guide, and restart Redmine. If the system still cannot find the plugin, email [email protected].

  • After copying plugin files and running the required migrations, stop and start the Redmine service again. For some installations, including some Docker environments, a full stop and start is required rather than a simple reload. Follow the guide for your plugin at /documentation or email [email protected].

  • Open the config/database.yml file in your Redmine installation and check the production section. The adapter value determines the database type used by Redmine. When contacting support, do not send passwords or other database credentials.

  • Verify that plugin asset files are copied to public/plugin_assets and that the Redmine system user has write permission to that directory during installation. If assets are still missing after a clean reinstall, send Redmine version, plugin version, installation steps, and relevant logs to [email protected].

  • Follow the update instructions for the plugin you are installing. For example, Advanced Workflow documentation requires removing the old advanced_workflows folder before copying the new version, running migrations, and stopping and starting Redmine. Download the latest available version from your account: redmine-kanban.com/login and check the documentation: /documentation.

  • First, ensure you installed the latest compatible plugin version using a clean update procedure. If the error persists, send Redmine version, plugin version, list of installed plugins, steps to reproduce, browser console output, Network tab details, and relevant Redmine logs to [email protected].

  • Yes. Conflicts are possible if another plugin modifies Redmine queries, permissions, issue views, or related functionality. If you suspect a conflict, send installed plugin names and versions, steps to reproduce, screenshots, and relevant logs to [email protected].

  • Open the demo from the relevant plugin page: /plugins. If demo credentials are shown on the demo page, use them to explore available features. For questions about a specific scenario, email [email protected].

  • Some administrative actions in the public demo are restricted for security reasons. If you need to verify a specific administrative scenario, describe it in an email to [email protected] or via the /contacts page.

  • No. The demo environment may include additional plugins to showcase capabilities. A paid package includes only the products listed in that package; other plugins in the demo may be free or licensed separately. See the product list at /plugins.

  • Send to [email protected] your Redmine version, Ruby version, plugin name and version, installation method, list of installed plugins, steps to reproduce, screenshots, browser console errors, Network tab details, and relevant Redmine log excerpts. Do not include passwords, access tokens, or other credentials.

  • Send to [email protected] screenshots or a short video, browser name and version, plugin and Redmine versions, browser console errors, relevant Network tab details, and exact steps to reproduce the issue.

  • We can provide general guidance, but exact installation steps depend on your server configuration. Docker is often a convenient option, but it is not the only installation method. Send your environment details and question to [email protected] or use the /contacts page.

  • Yes. If a feature you need is not in the standard plugin, we can discuss custom development. Describe your workflow and requirements on /plugins/custom_development or email [email protected] to request an estimate.

  • First, ensure the Kanban module is enabled in project module settings. Then verify that the user's role has permission to view Agile boards under Administration -> Roles and permissions, and check active board filters. If the board remains empty even for an administrator account, send screenshots, plugin version, project module settings, and filter configuration to [email protected].

  • The board supports standard issue filters and Kanban-specific filters, including sprint, Story Points, issue size, blocking reason, blocking type, and blocked parent or child issues. Quick filters apply on top of the board's main filters and affect only issues already loaded on the current board. If expected issues are missing, check main and quick filters; if the problem persists, send your saved board and filter configuration to [email protected].

  • Install the latest compatible version using a clean update procedure: remove the old redmine_kanban folder, copy the new folder to plugins/, run the redmine_kanban migration, then stop and start Redmine again. If the board still does not appear, send browser console output and Redmine logs to [email protected].

  • Yes. Issues can be moved between columns only if the user is allowed to edit the issue and set the status corresponding to the target column. Redmine workflow permissions and required field validation therefore still apply. If a required value or transition rule blocks the move, update the issue or permissions before moving it on the board.

  • The move may be blocked until the required field is filled. This ensures Redmine workflow and validation rules are respected when transitioning issues.

  • The Kanban modal supports viewing issue history and adding notes, but displaying private notes is not described in the published Kanban Board documentation. If you need to work with private notes, email [email protected] with your Redmine and plugin versions.

  • Yes. In board settings, enable "Allow drag-and-drop sorting on the board", then click "Apply" or "Save". You can then drag cards up and down within a column to set their order. The user's role must also have permission to sort issues on the board.

  • Yes. Redmine Kanban lets you configure blocking types and reasons, visually highlights blocked issues on the board, and automatically tracks the duration of blocking periods. Additional blocking reports are available in the Charts and Reports plugin: /plugins/advanced_charts.

  • Yes. Importing checklist items from a text file is listed among Checklists plugin features. See the current feature list on /plugins/checklists. If the import option does not appear in your installation, email [email protected] with your plugin version.

  • Published documentation describes importing checklist items, creating and applying checklist templates, and managing templates via API. Importing templates from a text file is not documented. If you need a template import scenario, email [email protected].

  • Yes. The Checklists API documentation describes operations to get, create, update, and delete checklist templates, and to create, update, and delete template items. See /documentation/checklistPlugin. Before integrating, ensure your installed plugin version supports the documented API endpoints.

  • Yes. Automatic checklist creation from templates is described in the documentation. Configure automatic checklist creation rules under Project -> Settings -> Checklists or Administration -> Modules -> Advanced Checklists. See /documentation/checklistPlugin or email [email protected].

  • Published API documentation provides for deleting checklist template items. If deletion does not work in the UI, install the latest compatible plugin version and check the browser console for errors. If the problem persists, send Redmine and plugin versions, screenshots, browser console errors, and steps to reproduce to [email protected].

  • Yes, if the appropriate role permissions are granted. Advanced Checklists includes permissions to manage global personal checklist templates and project personal templates, as well as permission to edit any personal checklist. Configure these permissions under Administration -> Roles and permissions. See /documentation/checklistPlugin.

  • This feature is not available by default, but it can be implemented as custom development. Describe your requirements on /plugins/custom_development or email [email protected].

  • Documentation confirms visual display of checklist completion, including progress indicators, but automatic synchronization with Redmine issue progress is not described. If you need this scenario, email [email protected] to clarify available options.

  • Sign in using the demo account shown on the demo page and try again. If the problem persists, send screenshots, browser console errors, browser version, and steps to reproduce the issue in the demo environment to [email protected].

  • Check the public/plugin_assets/redmine_advanced_checklists directory and file permissions. Missing files usually mean assets were copied incorrectly during installation. If a clean reinstall does not resolve the issue, send Redmine version, plugin version, and installation logs to [email protected].

  • Yes. The Lead Distribution Time chart shows how much time passes from issue creation to completion. The Charts and Reports plugin also includes a Cumulative Flow Diagram and reports on blocked issues and blocking reasons. See /plugins/advanced_charts.

  • The public product page confirms the Lead Distribution Time report exists but does not describe excluding weekends from calculations. Email [email protected] to confirm whether this option is available in your plugin version.

  • The public product page describes Lead Distribution Time as time from issue creation to completion, but configuring intervals between arbitrary statuses is not documented. Email [email protected] to discuss the reporting interval you need.

  • Verify that you are using a compatible plugin version, check Redmine mail settings, and ensure the Email Reporting module is enabled for the relevant projects or under Administration -> Email Reporting. Check relevant errors in production.log. If the problem persists, send Redmine and plugin versions, the full error stack, configuration details without credentials, and steps to reproduce to [email protected].

  • We aim to support the latest major Redmine version and the two previous major versions. Supported versions may vary by plugin release. Check current compatibility on the Email Reporting page: /plugins/email_reporting or email [email protected] before purchasing or updating.

  • Yes. Advanced Workflow automatic actions can change assignee, status, tracker, project, version, watchers, and other fields, and can send emails and webhooks. Actions can run on issue save or on a schedule. See /documentation/advancedWorkflow.

  • Verify that the automatic action is enabled under Project -> Settings -> Automatic actions and that Redmine mail is configured. If the action runs on a schedule, ensure the server cron job runs bundle exec rake advanced_workflows:run_actions as the user under which the Redmine service runs. If email sending still does not work, send Redmine and plugin versions, relevant error output, and configuration details without credentials to [email protected].

  • Configure permissions under Administration -> Roles, then enable the Checklists module for the project. You can configure automatic checklist creation rules under Project -> Settings -> Checklists or Administration -> Modules -> Advanced Checklists. See /documentation/checklistPlugin.

  • The API supports retrieving checklists for an issue, adding checklists and items, completing and editing items, assigning users, setting due dates, reordering items, and managing checklist templates and template items. See /documentation/checklistPlugin.

  • Email Reporting can send issue lists and time tracking reports on a schedule. For example, reminders about assigned or soon-to-be-overdue issues and time summaries by employee or project. Reports can be sent daily, weekly, or monthly. See /plugins/email_reporting.

  • Scheduled actions require a cron job on the Redmine server. Configure the action in Advanced Workflow, enable it for the project, and run bundle exec rake advanced_workflows:run_actions from cron as the user under which Redmine runs. See /documentation/advancedWorkflow.

  • Yes. Advanced Checklists can send a personal email notification to the user assigned to an incomplete checklist item. Reminders can be sent for a single item or for matching assigned checklist items. See /documentation/checklistPlugin.

  • In project settings, enable the required Kanban, Backlog, and Sprints modules. Configure role permissions under Administration -> Roles and permissions, and plugin settings under Administration -> Modules -> Kanban Board or Administration -> Kanban. See /documentation/kanbanBoard.

  • Yes. A board can be saved as a query together with its filters and display settings. Without the "Use in any project" option, the board remains tied to the project or "All projects" context where it was created. If this option is enabled, the board can be used in any project and in the "All projects" view.

  • Yes. In addition to the Kanban board, the plugin provides Backlog and Sprints modules. In Backlog, issues can be organized by fields such as tracker, priority, assignee, version, sprint, or custom fields. Sprints supports time-boxed iterations that can be shown on the Kanban board.

  • Yes. In board settings, you can set minimum and maximum WIP values for columns and a card age threshold. If a card's age exceeds the configured threshold, the "Updated" field value is highlighted. The additional "Old Paper Effect" visually emphasizes overdue or long-unchanged issues.

  • Yes. If issue creation on the board is enabled in plugin settings, you can create a new issue directly in a column. Clicking a card opens a modal where you can view and edit issue details without reloading the board; editing checklists in the modal requires the Advanced Checklists plugin.

  • Enable the "Show in application menu" option under Administration -> Modules -> Kanban Board -> Configure on the Kanban tab. Then open Kanban from the top Redmine menu to view issues from all projects you have access to.

Need help with plugin integration?

Send your Redmine version, plugin version, list of installed plugins, screenshots, browser console errors, and relevant logs to [email protected]. The support team will help identify the cause of the issue.