Plugins

A page for administrators. TaskFlow is modular: nearly everything beyond the basic tracker is a feature (plugin) that an administrator enables one by one. They are managed in Admin → Plugins.

The plugin panel

The page has two cards: Frontend plugins — the registry of everything the installation knows about — and Add plugin for connecting your own.

The registry

The table shows, for each feature:

Column	What it means
Name	The feature's technical name. The instance configuration refers to it by the same name.
Category	The area the feature belongs to — see below.
URL	Where its interface is loaded from. For built-in features it is an address inside the instance; for custom ones, whatever you entered.
Source	built-in — ships with the product; custom — added by you.
Status	The actual state, see the table below.
Enabled	The switch. For unavailable features it is greyed out and does nothing.

There are several dozen features in the box, so above the table there is a search (by name, address and category) and three filters — category, status and source. The Name, Category and Status headers sort the list, a long list is paginated, and the Table / Cards toggle switches the layout — cards read better on a narrow screen. A loaded feature that has a page of its own gets an Open button in its row, taking you straight there instead of hunting through the menu.

Statuses:

Status	What it means	What to do
Loaded	The feature is on and its interface loaded.	Nothing.
After reload	The feature was just enabled: its server side is already running, and the interface appears once the page is refreshed.	Press Apply and reload.
Disabled	Turned off by an administrator — the same state as anything that was never enabled.	Flip the switch.
Unavailable	Not permitted by the instance configuration. It cannot be enabled at all.	See Configuration → Required settings.
Error	Enabled, but its interface failed to load. The reason is in the tooltip.	Check that all parts of the installation are on the same version and reload the page.

Categories

The category tells you what area a feature covers, and the list filters by it:

Category	What's in it
Issue features	Fields, checklists, worklog, SLA, search, archive, the Create menu and everything else that lives around an issue.
Planning & releases	Calendar, roadmap, releases, release waves, portfolios.
Analytics	Reports and dashboards.
Service desk	Service Desk.
Mail gateway	Email transports.
File gateway	Storage for attachments and dumps.
Integrations & access	Automation, webhooks, messengers, import and transfer, single sign-on, per-object permissions, profile fields.
Other	Everything else — and every custom feature, since they bring no category of their own.

On a new instance everything is off

A feature counts as off until it is explicitly enabled: no pages, no tabs, no background work, no schedules. That applies to a freshly installed feature too. “We don't have that capability” almost always means exactly this.

Enabling and disabling

The switch takes effect immediately and on the running system: the feature's server side starts or stops within seconds, and its schedules start or stop firing. The interface, however, is assembled when the page loads, so after changes press Apply and reload — the button is only active if you changed something.

If another administrator is working with the same registry, your table updates by itself, without a reload.

Disabling deletes nothing. The feature's data, settings and assignments stay in the database: turn it back on and everything returns. That is precisely why disabling is a safe way to check whether a problem is caused by a particular feature.

Turn off what you don't use

Every enabled feature means its pages in the menu, its fields on cards, its background work and its events in the audit log. An instance with a dozen useful features is easier to live with than one where everything is on.

Adding your own feature

The Add plugin card connects a feature that does not ship with the product: a name (Latin letters, digits, dash and underscore) and a module URL starting with http:// or https://. The name must not clash with an existing one.

An added feature appears in the registry as custom and, like everything else, starts out disabled. Only custom features can be deleted — built-in ones have no delete button, they are switched off instead.

Third-party code runs in your users' browsers

A connected feature's interface is loaded into the same page and acts with the rights of whoever opened it. Only connect addresses you trust, and prefer your own origin. Review what you are connecting before enabling it, not after.

The permitted set of features

On top of the switches there is a list fixed when the instance is deployed: features outside that list appear in the registry as “Unavailable” and cannot be enabled. This is how the owner of the installation fixes what the product includes — on a plan where some capabilities are not offered, for instance.

If a feature is missing entirely or unavailable, that is settled not here but in the instance configuration.

Feature catalogue

Below is everything that ships with the product, with the place it shows up once enabled. The name in the first column is the one you see in the registry.

Working with issues

Name	What it adds	Where it appears
custom-fields	Custom issue fields: text, number, date, select. Required ones are checked on creation, take part in automation rules and drive Service Desk portal forms.	Admin → Custom Fields; a tab on the issue card
checklists	Checklists inside an issue: several lists, per-item assignee and due date.	A section on the issue card
worklog	Time logging and effort estimates, a start/stop timer with a warning and auto-stop for a forgotten timer, a daily timesheet (your own and your team's), a summary report for a period and CSV export.	Admin → Time Tracking; Timesheet; a tab and a “Timer” panel on the issue card
templates	Project templates (spin up a project with boards, a workflow scheme and starter issues) and recurring issues on a schedule.	The Templates section
archive	An archive instead of deletion: archived issues and projects disappear from lists but are kept, and can be restored or removed for good.	Admin → Archive; a panel on the issue card
quick-create	A configurable Create menu in the top bar: your own entries, labels per language and visibility conditions.	Admin → “Create” menu
mention-button	An @ User button in the comment editor toolbar.	The comment editor

Planning and analytics

Name	What it adds	Where it appears
calendar	Issues on a monthly grid by due date; on a phone, an agenda by day.	The Calendar section
roadmap	A roadmap and Gantt chart: issue bars from start to due date, milestones, finish-to-start dependencies that shift dependent issues, the critical path and release markers.	The Roadmap section
releases	Project versions with a date, description and scope; publishing fixes the release.	The Releases section; a tab on the issue card
release-waves	Release waves across several brands: an issue × brand matrix with a readiness status per cell. A wave schema can be duplicated, and changing a brand's status is available to automation rules.	The Release waves section; Admin → Wave schemas
portfolios	Project portfolios: a portfolio → program → project hierarchy, milestones, a risk register with a probability × impact matrix, a status traffic light (computed automatically, can be overridden by hand with a comment), a timeline and CSV export.	The Portfolios section; a “Portfolio” tab in the project
reports	A reports section in eight categories: project overview, flow (cycle and lead time, a cumulative flow diagram), workload and blockers, work completed in a period, SLA, backlog, sprints (velocity, burndown, burnup) and a custom-slice builder. CSV export, printing and scheduled report emails. Stores no data of its own — it computes over issues, and takes hours and SLA from the matching features.	The Reports section
dashboards	Dashboards built from widgets provided by other features: a user can have several, and any of them can be shared read-only — with everyone, a group or a project. Its own widgets are "Open issues", "Sprint progress" and "Filter result" (a saved filter's result as a list or a number).	The Dashboard section

Search, notifications, support

Name	What it adds	Where it appears
search	Full-text search over issues plus saved searches. Needs a search service; the filters are shared with the core condition builder, so field-based selection works even with this feature off.	The Search section
notifications	Notifications in the app, by email and to an external gateway; each person chooses what reaches them and where. Email templates, due-date reminders and the “Notify issue participants” automation action.	The Notifications section; Admin → Notification gateways
messengers	Notification gateway types for messengers and SMS: Telegram (direct messages and chats), WhatsApp, VK, MAX, Slack, Discord, Mattermost and Rocket.Chat, SMS.ru; each with an optional proxy. Of no use without notifications.	Admin → Notification gateways → Messenger types
service-desk	The help desk: request types, queues, customers, approvals, a knowledge base, CSAT and the customer portal.	Admin → Service Desk and its nested sections; the customer portal
sla	Response and resolution targets measured against work calendars: a weekly schedule, holidays and moved working days (by hand, from ICS or CSV, or from ready-made presets). Timers are visible on the request.	Admin → SLA; a panel on the issue card

Users and access

Name	What it adds	Where it appears
user-fields	Extra profile fields (phone, job title, messenger) with a soft or hard prompt to fill them in.	Admin → Profile fields; the user profile
advanced-permissions	Object-level rights on top of schemes: grants on a single object, explicit denies and a “what can this person do here” check.	Admin → Access permissions
sso	Single sign-on through a corporate provider over OIDC or SAML 2.0; several providers can be configured.	Admin → Single sign-on

Integrations and data exchange

Name	What it adds	Where it appears
automation	Rules of the shape “event → conditions → actions”: schedules (including a walk over a saved issue selection), inbound webhooks and emails as triggers, deferred steps, templates, dry runs, a log and a diagram view.	Admin → Automation
webhooks-out	Outbound webhooks: sending events to external systems with a delivery log.	Admin → Outbound calls
devlinks	Git hosting branches and commits on the issue card; the issue key is read from branch names and commit messages.	A panel on the issue card
import	A one-way import from Jira (users, groups, projects, issues, comments and attachments) and transfer of projects between TaskFlow instances — through files or directly over the network.	Admin → Import; Admin → Data transfer

File storage

Name	What it adds	Where it appears
storage-s3	File storage in any S3-compatible service. The product has no storage of its own — without such a feature attachments will not work.	Admin → Storage → S3-compatible storage

In detail — File storage.

Email transports

The product carries no mail code of its own: messages are sent by a transport that you enable and assign to the kinds of mail it should carry. Transports do not exclude one another.

Name	What it sends through
mail-smtp	Any mail server over SMTP: Exchange, Postfix, your hosting provider's mail, an internal relay
mail-jmap	A JMAP server (Stalwart, Fastmail, Cyrus). The only one that can also receive mail
mail-ses	Amazon SES
mail-sendgrid	SendGrid
mail-google	The Gmail API on behalf of a user in your Google Workspace domain
mail-relay	The platform mail gateway: the instance holds no provider keys. The default for cloud instances

In detail — Email.

Next

• Administration overview — a map of every admin page, including those brought in by features.
• Features & settings — instance-wide parameters.
• Configuration — the permitted set of features and other deployment parameters.

See also

• Automation — what the automation feature gives you.
• Agent guide — what service-desk and sla give you.
• Reports & analytics — what reports, dashboards, roadmap, releases, release-waves, portfolios and worklog give you.
• Search & notifications — what notifications and messengers give you.
• Webhooks → Outbound — what webhooks-out gives you.
• Single sign-on — what sso gives you.