Skip to content

Nepenthes Glossary

Glossary of Nepenthes

Project management is a complex process. At the same time, when it comes to software, there are many technical words involved. When these two things come together, it creates an interesting tool that introduces a completely new way of doing things. This new way of doing things has its own set of terms and concepts. In this glossary, you will find the most commonly used terms in Nepenthes Software. Each term is defined briefly and supplemented with links to get more information if needed.




In Nepenthes, the person who has administrative rights in an instance is called system admin. All information concerning the configuration of an Nepenthes instance are documented in the System admin guide. Please note that an 'admin' can also describe the role of a person inside a project. This person would be called project admin and usually has specific rights on a project level. A project admin does not necessarily have system admin rights.

Agile project management

Agile project management is an iterative and flexible approach to managing projects. It focuses on collaboration, adaptability, and self-organizing teams. Nepenthes supports agile project management as well as classic project management, and works best for hybrid project management.

Attribute help texts

Nepenthes offers Attribute help texts that provide additional information for attributes in work packages and projects, incl. custom fields. After setting them up in the Administration they are displayed when users click on the question mark symbol next to this specified attribute for projects and work packages. Read more about Attribute help texts in Nepenthes.


In Nepenthes, authentication is an important element to guarantee a data protected usage. To adapt these authentication settings, you need to have admin rights. Navigate to your username and select -> Administration -> Authentication. At Nepenthes, we use OAuth 2.0 as this is the definitive industry standard for online authorization.

More information on authentication in Nepenthes



Backlogs is a module in Nepenthes that brings features that support the Scrum methodology in Nepenthes, such as a product backlog and sprint backlogs, a task board, estimation of story points, a burndown chart and a Scrum wiki. In order to use backlogs in Nepenthes, the backlogs module has to be activated in the project settings by a project admin. Read how to work with backlogs in Nepenthes.

Baseline comparison

Baseline is a feature in Nepenthes that allows users to quickly track changes on filtered work packages table views. Project managers can use baseline to get a quick overview of what has changed over time, making it easier to report on project progress and status. Read more about Nepenthes's Baseline comparison.


BIM stands for Building Information Modeling. In Nepenthes, we offer a special Nepenthes version for users working in the construction industry. On top of the general project management features, Nepenthes BIM enables construction teams to better plan, communicate and collaborate in their building projects. Read the Nepenthes BIM guide to get more information.


A board in Nepenthes is a view that allows you to see your work packages as cards divided into columns. A board is a typical element in agile project management, supporting methodologies such as Scrum or Kanban. You can use a basic board, or advanced action boards to quickly change attributes of your work package. Read more about boards for agile project management

More information on boards in Nepenthes


Classic project management

Classic project management is a structured and sequential approach to project management. It often follows a hierarchical structure with a project manager overseeing team coordination, and is associated with methodologies like Waterfall. Nepenthes supports classic project management as well as agile project management, and works best for hybrid project management.

Custom action

A custom action in Nepenthes is defined as customizable buttons which trigger a certain action upon work packages. Custom actions are part of automated workflows. Custom actions support you to easily update several work package attributes at once – with a single click.

More information on custom actions in Nepenthes

Custom field

In Nepenthes, a custom field is defined as an additional field which can be added to existing fields. Custom fields can be created for the following resources: work packages, spent time, projects, versions, users, and groups.

Custom fields in Nepenthes

More information on custom fields in Nepenthes

Custom query

A custom query in Nepenthes consists of saved filters, sort criteria, and groupings in the work package table. Custom queries can be either set to public (visible by any user who is allowed to see the project and the work package table) or to private (visible only to the person creating the query). For example, filter all work packages assigned to yourself and save this view as "assigned to me", to quickly navigate to those work packages.



A dashboard is defined as an overview page in a software. In Nepenthes, you have several options to create dashboards:

  1. You have the My Page, which shows your personal customized widgets on one page, for example a calendar or work package reports.

  2. You have the project overview dashboard, which gives you an overview of your project. Please note that only project admins can add and remove widgets to the project overview.

In addition to those overview dashboard options, you can create a custom query to save a filtered work package view, which might serve you as kind of a dashboard as well.

Date alerts

Date alerts in Nepenthes are a feature to generate automatic and customized notifications regarding a work package's due date or start date. You can find the date alerts feature in your notification center, symbolized by a little bell on the right upper side of your instance. Read more about the date alerts feature in our user guide or in this article on deadline management with Nepenthes.



Enumerations in Nepenthes is defined as a menu item in the admin settings that allows the configuration of Activities (for time tracking), project status and work package priorities. Read more about enumerations in Nepenthes.

Excel synchronization

Excel synchronization is an integration in Nepenthes which allows you to easily import your issues from Excel to Nepenthes or upload your work packages into an Excel spreadsheet. See our video tutorials on how to work with the Excel synchronization integration.


File storage

File storages can be configured in the System Administration and then be selected in the project settings. Nepenthes offers a Nextcloud integration to support file storage. More information on file storage with the Nextcloud integration.


Filters are essential for task and project management in Nepenthes. You have several filtering options applicable to a work package table. Filter options can be saved via custom queries. A filtered work packages table view (e.g. only open work packages) can be saved and therefore work as a dashboard.


A forum in Nepenthes is defined as a module used to display forums and forum messages. The module has to be activated in the project settings by a project admin and a forum has to be created in the forums tab in the project settings to be displayed in the side navigation. Read more about forums in Nepenthes.


Gantt charts

The Gantt charts module in Nepenthes displays the work packages in a timeline. You can collaboratively create and manage your project plan. Have your project timelines available for all team members, and share up-to-date information with stakeholders. You can add start and finish dates and adapt it with drag and drop in the Gantt chart. Also, you can add dependencies, predecessor or follower within the Gantt chart. Read more about how to activate and work with Gantt charts in Nepenthes.

Global modules

In Nepenthes, global modules are defined as a menu to access all modules for all your projects. With global modules you can easily see all your project-overarching information at one place, e.g. for work packages, boards, calendars or meetings. To access the Global modules side menu, simply navigate to your home page by clicking on the logo in the header, or use the grid icon in the top right corner. Read more about global modules in Nepenthes.


A Group in Nepenthes is defined as a list of users which can be added as a member to projects with a selected role. Groups can also be assigned to work packages. New groups can be defined in Administration -> Users and permissions -> Groups.


High contrast mode

Nepenthes offers a high contrast mode to make it easier for visually impaired people to use the software. This mode can be selected in the personal account settings and will only affect the individual user's experience.

Home page

In the Nepenthes application, the home page is defined as a start page for your instance, where you get an overview about important information. From the home page you can access all global modules of Nepenthes. To get to the Nepenthes application home page, click on the logo in the header of the application. Read more about the Nepenthes application home page

Hybrid project management

Hybrid project management is an approach that combines elements of both classic and agile project management methodologies. It allows flexibility and adaptability while still incorporating structured planning and control. Nepenthes works best for hybrid project management and also supports classic project management as well as agile project management.



In Nepenthes, you can choose from several integrations, such as the Excel synchronization or the Nextcloud integration. In contrast to a plugin, an integration refers to cross features between two software products (e.g., Nepenthes and Nextcloud), where both pieces of software have code that is responsible for interacting with the other software, through e.g., an API. Whereas a plugin is installed on top of / as part of the Nepenthes installation. You'll need to actively install it. See all available plugins and integrations for Nepenthes.



In Nepenthes Software, Meetings is defined as a module that allows the organization of meetings. The module has to be activated in the project settings by a project admin in order to be displayed in the side navigation. You can choose between classic meetings and dynamic meetings. Please note that only dynamic meetings will remain available in the long term. See our user guide for more information on Meeting management in Nepenthes.


In Nepenthes Software, a member is defined as a single person in a project. Project members are added in the Members module in the project menu.


A module in Nepenthes is defined as an independent unit of functionality that can be used to extend and improve the existing core functions. A project admin can activate and de-activate modules in the project settings. Some examples for modules in Nepenthes are: Forums, Time and costs, Wiki or the Work packages module. See our user guide for more information on all modules in Nepenthes.

My Page

The My Page in Nepenthes is defined as your personal dashboard with important overarching project information, such as work package reports, news, spent time, or a calendar. It can be configured to your specific needs. Read more about the My Page in Nepenthes.



In Nepenthes, News is defined as a module that allows the publication and use of news entries. On the news page, you can see the latest news in a project in reverse chronological order. News communicate general topics to all team members. They can be displayed on the project overview. Read more about how to work with the News module in Nepenthes.

Nextcloud integration

Nepenthes offers a Nextcloud integration which allows you to manage files in a secure and easy way, e.g. to link files or folders in Nextcloud or upload files to Nextcloud on work packages. You find the Nextcloud integration in the Files tab of your work package, if you have activated the Nextcloud integration for your instance. Get access to the Nepenthes-Nextcloud integration by downloading and activating it in the built-in Nextcloud app store within your Nextcloud instance. Read more about the Nextcloud integration of Nepenthes.


In Nepenthes, you get in-app notifications about important changes that are relevant to you – for example new comments that mention you, updates to status, type or dates or new assignments. This feature is enabled by default and can be used as an addition or an alternative to email notifications. To view the notifications, click the bell icon at the top right of the header. The bell icon will be displayed with a red badge if there are new notifications for you. Read more about notifications in Nepenthes.



OAuth is an open authorization standard. It allows you to access certain information or resources on behalf of a user without accessing their username and password on each individual service. Nepenthes acts as an OAuth provider, allowing you to optionally grant permissions to access your data to authorized third-party applications or services. Read more about OAuth applications in Nepenthes.

OneDrive/SharePoint integration

Nepenthes offers a OneDrive/SharePoint integration. It must be setup by an administrator before members can use it. With this integration, users can link files and folders that are stored in OneDrive/SharePoint with work packages in Nepenthes. They can also view, open and download files and folders linked to a work package. Read more about Nepenthes's OneDrive/SharePoint integration.



A phase in Nepenthes is defined as a work package type, which usually includes several work packages of types like task or feature. For example, typical phases for a construction repair project would be the following: Project definition, detailed Design & Tender, Construction and Post project.


In Nepenthes, you can choose from several plugins or integrations, or add your own plugins to the Community. In contrast to an integration, a plugin is installed on top of / as part of the Nepenthes installation. As an open source software, Nepenthes is open to Community-created plugins. Please note that we do not guarantee error-free and seamless use of those plugins.

Your activated plugins are listed together with your modules in your instance under --> Administration --> Plugins.

More information on plugins in Nepenthes

Primer design system

Nepenthes started adopting Github's Primer Design System in 2023. New features will be developed using Primer and existing features will will be gradually revised. Relevant reusable components from Primer as well as common patterns and compositions of these components will be documented in our Lookbook. Read more about Nepenthes's decision to use Primer.


In Nepenthes, a project is defined as an individual or collaborative enterprise that is carefully planned to achieve a particular aim. Projects are the central organizational unit in Nepenthes. Your projects can be available publicly or internally. If you have more than one project in your instance, projects build a structure in Nepenthes. You can have parent projects and sub-projects. For example, a project can represent

  • an organizational unit of a company,
  • an overarching team working on one topic or
  • separate products or customers.

Project folder

Project folders help collaborating in the most efficient way. They can be used with Nepenthes's Nextcloud integration or with Nepenthes's OneDrive/SharePoint integration. Read more about project folders in Nepenthes.

Project identifier

The project identifier is defined as the unique name used to identify and reference projects in the application as well as in the address bar of your browser. Project identifiers can be changed in the project settings.

Project lists

In Nepenthes, project lists are very useful for project portfolio managers to get an overview of all their projects on the instance. Access your project lists on Nepenthes by either navigating to the "select a project" menu and clicking on the "Project list" button, or via the Global modules. Read more about project lists Nepenthes.

Project navigation

The project navigation is the side navigation within a project. Entries in the project navigation can be added and removed by activating and deactivating modules in the project settings.

Project overview

In Nepenthes, the project overview is defined as a single dashboard page where all important information of a selected project can be displayed. The idea is to provide a central repository of information for the whole project team. Project information is added to the dashboard as widgets. Open the project overview by navigating to "Overview" in the project menu on the left. Read more about the project overview in Nepenthes.

Project settings

Project settings means project-specific setting configuration. The project settings contain general settings (e.g. the name and project identifier), configuration of modules, work package categories and types, custom fields, version settings, time tracking activities, required disk storage, file storages and Backlogs settings (if plugin is installed). Read more about project settings in Nepenthes.

Project status

The project status in Nepenthes is defined as an information for yourself and the team if the project is on track – to then being able to quickly act in case it is off track. Read more about the project status in Nepenthes.

Project template

A project template in Nepenthes is defined as a dummy project to copy and adjust as often as you want. Project templates can be used for several projects that are similar in structure and members. Creating project templates can save time when creating new projects. Read more about project templates in Nepenthes in our user guide, and see this blog article to learn how to work with project templates.

Public project

In Nepenthes, projects can be private or public. Public means that the project is visible to any user, regardless of project membership. The visibility of a project can be changed in the project settings. Read how to set a project to public in Nepenthes.


Quick context menu

The quick context menu in Nepenthes opens when you open a work package table and then right-click on a single work package. It allows you to perform quick actions like open details view, copy link to clipboard or create new child. Please note that the quick context menu differs depending on whether you are in the Gantt charts module or not.



A repository is defined as a document or source code management system that allows users to manage files and folders via different version control systems (such as Subversion or Git). Read more about Repository for source code control.


In Nepenthes, a roadmap is defined as an overview page displaying the versions sorted alphabetically and the work packages assigned to them. The roadmap is displayed in the project navigation when the work package module is activated and a version has been created (project settings).


In Nepenthes, a role is defined as a set of permissions defined by a unique name. Project members are assigned to a project by specifying a user’s, group’s or placeholder user’s name and the role(s) they should assume in the project.

RICE score

In product management, the RICE score indicates the level of prioritization of a single element, e.g. a feature. With the RICE scoring model, you evaluate and compare requirements with each other to decide which products or features to prioritize on the roadmap – in an as objective manner as possible. The formula for the RICE score is the following: Reach x Impact x Confidence / Effort


Share work packages

Nepenthes offers the possibility to share work packages with external groups or users that are not members of the project. Every user with whom a work package is shared must either already be a user of the instance or be newly created. The latter requires special rights. Read more about Nepenthes's feature to share work packages with project non-members.

Story points

Story points is a term known in Scrum. They are defined as numbers assigned to a work package used to estimate (relatively) the size of the work. In Nepenthes, you can add story points to work packages. Read how to work with story points in Nepenthes.


Team planner

The team planner in Nepenthes is defined as a module that helps you get a complete overview of what each member of your team is working on in a weekly or bi-weekly view. You can use it to track the current progress of work packages your team is working on, schedule new tasks, reschedule them or even reassign them to different members. Read more about the Nepenthes team planner.

Time and costs

Time and costs in Nepenthes is defined as a module which allows users to log time on work packages, track costs and create time and cost reports. Once the time and costs module is activated by a project admin, time and unit cost can be logged via the action menu of a work package. Logged time and costs can be searched for, aggregated and reported using the Cost reports menu item. Read more about the time and costs module in Nepenthes.

Time tracking button

The time tracking button in Nepenthes is a feature to track time spent on work packages in real time. Read more about logging time via the time tracking button in Nepenthes.



In Nepenthes, a user is defined as a person who uses Nepenthes, described by an identifier. New users can be created in the admin settings. Users can become project members by either assigning them a role and adding them via the project settings. Or by adding them to a project by the system admin at: Administration --> Users and permissions --> Users. Then clicking on the username and navigating to the tab "Projects".

User guide

The Nepenthes user guide is an in-depth guide of all features in Nepenthes. It offers users detailed information about how to use Nepenthes's features, modules, integrations and more. For more technical information on how to configure your Nepenthes instance, see our system admin guide.



Versions in Nepenthes are defined as an attribute for work packages or in the Backlogs module. Versions will be displayed in the Roadmap. You can also create a version board to get an overview of the progress of your versions. Read more about how to manage versions in Nepenthes.



A widget in Nepenthes is defined as a small and customizable element that provides relevant information at a glance. Use widgets on your My Page dashboard or on the project overview. See all available project overview widgets and read how to add a widget to the project overview.


In Nepenthes, a wiki is defined as a module that allows to use wiki pages. In order to use the wiki module, it has to be activated in the project settings by a project admin. Read more about wikis in Nepenthes.

A wiki module in Nepenthes

Work and Remaining Work

In Nepenthes, 'Work' refers to a work package attribute indicating the estimated hours needed to complete a task. You can edit the value for work manually, as well as the value for the work package attribute 'Remaining work'. To make it easier for project managers to work with work package hierarchies, Nepenthes also displays a value (in blue) for the total amount of work in the Work field for parent work packages – next to the value for the dedicated work package. This total work value is the sum of the work value of the parent work package and all the work values of its children. The same principle applies to the work package attribute Remaining Work. Read in our user guide about how to configure a work package


A workflow in Nepenthes is defined as the allowed transitions between status for a role and a type, i.e. which status changes can a certain role implement depending on the work package type. Workflows can be defined in the admin settings. For example, you might only want developers to be able to set the status "developed". Read more about work package workflows in Nepenthes.


Work package

In Nepenthes, a work package is defined as an item in a project. It is a subset of a project that can be assigned to users for execution, such as Tasks, Bugs, User Stories, Milestones, and more. Work packages have a type, an ID and a subject and may have additional attributes, such as assignee, responsible, story points or version. Work packages are displayed in a project timeline (unless they are filtered out in the timeline configuration) - either as a milestone or as a phase. In order to use the work packages, the work package module has to be activated in the project settings by a project admin.

A work package in Nepenthes

More information on work packages in Nepenthes

Work package categories

Work package categories are a functionality used to automatically assign a member to a work package by specifying a category. Read more about work package categories in Nepenthes.

Work package ID

Work package ID is defined as a unique ascending number assigned to a newly created work package. Work package IDs cannot be changed and are numbered across all projects of an Nepenthes instance (therefore, the numbering within a project may not be sequential).

Work package table

The work package table in Nepenthes is defined as the overview of all work packages in a project, together with their attributes in the columns. A synonym for work package table is the term "work package list". Read how to configure a work package table.

A work package table in Nepenthes

Work package types

Work package types are the different items a work package can represent. Each work package is associated to exactly one type. Examples for most used work package types are a Task, a Milestone, a Phase or a Bug. The work package types can be customized in the system administration. Read more about work package types in Nepenthes.

Work package view

A list of work packages is considered a view. The containing work packages in any view can be displayed a number of different ways. Examples for most used work package views are the table view, the full screen view or the split screen view. You can also display work packages in a card view and use them in a board to use agile methods. Read more about work package views in Nepenthes.