Update on Subversion Commit Hooks

Feature update
Added by Jens Krämer 4 months ago

As announced before, we've continued to work on our repository hooks feature.

We have now moved the already existing SVN post-commit web hooks over to the new Repository Hooks UI, and introduced two new hook types:

  • Require valid ticket reference is a pre-commit hook which will reject commits that do not reference an existing Planio issue. This is a great way to ensure your cross references between issues and related commits are complete and that there are no "stray" commits.
  • Insert ticket subject is a post-commit hook which will extend such references to Planio issues with their subject, saving you typing work and making commit messages more informative at the same time.

You can find more information on how to use those hooks in our guide.


Please register to add a comment

Require Two-Factor Authentication for Specific User Groups

Feature update
Added by Jens Krämer 4 months ago

We're happy to announce this new feature which gives you more options when it comes to configuring Two-Factor Authentication (2FA) for your organization.

What's new?

2FA has been present in Planio for quite some time now. Until now, you could enable it in two steps - as an optional feature, leaving it up to users whether they activate it for their account or not, or as a requirement for all users.

We're now introducing a middle ground, allowing you to enable 2FA as an option for all users, while enforcing its use for selected groups of users (i.e., administrative / management users) at the same time.

How to Enforce 2FA for a Group of Users

  1. Make sure Two-factor authentication is set to optional under your avatarAdministrationSettingsAuthentication.
  2. Navigate to AdministrationGroups. Click on the name of the group you want to edit or create a new one for this purpose.
  3. In the General tab, tick the Require two factor authentication box.
  4. Add users to your group if you just created it, and save your changes.

When users of the group you just configured next sign in, they will be required to set up 2FA, if they haven't already.

Repository Commit Hooks

Feature update
Added by Felix Schäfer 9 months ago

We are currently developing and slowly rolling out commit hooks for repositories on Planio.

Initially, pre-commit webhooks are available for Subversion repositories. Project managers can influence the commit life cycles of each repository in a project, by for example enforcing a certain commit message format, limiting commit rights for certain portions of the subversion repository, or by enforcing other custom rules.

You can find more information on how to use those hooks in our guide.

We will add more hook types and extend this functionality to Git repositories in the future.

Delivering Non-Delivery Notifications for Planio Help Desk

Feature update
Added by Holger Just about 1 year ago

Using the Planio Help Desk Pro Feature, you can communicate with external contacts such as customers or external stakeholders via email directly from your Planio issues.

Sometimes however, emails can't be delivered to the final recipient, e.g. when the email account is no longer active or has reached its storage quota. In these cases, email servers sometimes send an automatic non-delivery notification back to the sender, also called a bounce message, informing them that the message could not be delivered.

Until now, Planio filtered out these types of notifications to avoid cluttering your issues with automatic responses.

Occasionally though, these notifications can be useful. Once you know a customer or external contact didn't receive your mail you can use a different communication channel to contact them, for example with an alternative email address, or even a plain old phone call.

This is why we have now made it possible to receive bounce emails in projects where you have the Planio Help Desk app installed.

To configure how Planio should handle these notifications, you can go to your projectSettingsHelp DeskIssue status for bounce mails. Here you can select either:

  • Default Status: to create an issue with the default status used by the tracker set in the field "Tracker for emails",
  • None, do not create issue: to keep the previous behavior and not create an issue at all,
  • Your Status: to create the issue and to set it to a custom status of your choosing.

Configure the status for bounce emails

Configure the status for bounce emails

Pro Tip: You could create a new status called Bounce via your avatarAdministrationIssue Statuses and set it up to be a closed status. Then, select this status in your project's Help Desk settings. This way, you'll never see bounces (because they're closed immediately), but you'll be able to check them on demand by filtering your issues by that status.

Head branch name in Git repositories

Feature update
Added by Felix Schäfer about 1 year ago

In light of efforts in the Git community to change the name of the default Git branch to main as well as to support more inclusive naming in the tech sector, Planio changed the name of the default (HEAD) branch for newly created Git repositories to main. Note that this change will only affect newly created repositories and is compatible with older Git versions, no action is required on your part.

Along with this change in the default head branch, Planio introduces the possibility to change the head branch of existing repositories. This means our customers can change from a master to a main (or any other existing branch) head branch now. Project managers will find this option in the project's SettingsRepositoriesEdit of the desired repository.

New Guide: Making bulk changes to issues and time entries

Guides and Support
Added by Ema Raven over 1 year ago

We have prepared a new guide to help you use Planio more efficiently. Using our bulk editing feature, in just a few clicks you can reassign a category, modify an assignee, change the due dates of multiple issues and much more!

Check out our step by step guide and learn all about making bulk changes to your issues and time entries here:

Opening the bulk edit menu

Planio Issue usage improvements

Improved features and updates
Added by Ema Raven almost 2 years ago

We are proud to bring a new Planio update to our customers with usability, configuration and speed improvements in many key Planio functions.

Issue improvements

Issues are one of our central features and have received a lot of updates. The most visible change is the issue history, which can now be viewed either as a unified history or as only Notes, Property Changes, and where applicable only Time Entries, Associated Revisions or Chat Logs. Using those new tabs you can now focus on only the parts of the Issue History that are important to you.

New Issue history

The editor for formatted texts also has been improved in several ways. A new toolbar button allows for quick and easy creation of tables and formatted texts can now be previewed in place. Quick and easy also best describes the new autocomplete helpers for issue numbers (just type # followed by an issue ID or some part of the title text) and for web pages (just type [[ and some part of the wiki page name or title).

Improved formatted text editor with an issue autocomplete menu

All those improvements to the formatted text editor are also available for all formatted text editors in Planio, not just for those in issues!

Default Queries

Keeping in line with improvements to the usability of Issues are Default Queries. Administrators can now set a global Issue Query as a global Default Query, and project managers can choose a Default Query at a project level that can override the global Default Query. You can now configure which columns, filters, sort order and groupings are used by default in the Issues Tab for each project and globally!

Many more small improvements

While those are our favourite new features there are many more across the board. The project list for example can now be filtered. You can create new users by importing users from a CSV file. Groups can now be added as Watchers to Issues. You can now download all attachments from an Issue at once instead of downloading each Issue attachment individually.

One security improvement we would like to make Administrators of Planio accounts that use LDAP authentication aware of is certificate checking. Up until now connections to an upstream server using the LDAPS option would benefit from strong encryption for connections made to the LDAP server, however the validity of the LDAP server's certificate would not be checked. The new default for LDAP servers is to check the validity of the LDAP server's certificate, and we would encourage existing Administrators of Planios with LDAP authentication to switch to LDAPS with certificate validation available in the LDAP connection's configuration.

Upgrade to Redmine 4.2

Everyone who’s keeping an eye on Redmine development as well, will have noticed that many of the improvements in Redmine have either appeared on Planio first or have been integrated in Planio throughout the last couple of months already. Today’s update marks the “official” upgrade of the Planio code base to Redmine 4.2 though, meaning that Planio is now up to date with all the small and minor code changes and quirks of the latest Redmine release.

We hope these improvements will make using Planio more productive for everyone and would love to hear your feedback. If you have any questions regarding those new features or anything Planio related please get in touch.

Allow managers to invite new users via email

Feature update
Added by Jens Krämer over 2 years ago

As an administrator of your Planio account, you can now allow non-admin users to invite new users to their projects via email. For example, you can allow project managers to add new members in order to streamline the onboarding of new users.


The whole feature is opt-in and must be enabled under Your AvatarAdministrationSettings in the Authentication tab, where you can choose who is Allowed to invite new users via email:

Global setting to enable the feature

Once you have set the field Allowed to invite new users via email to Administrators and authorized project members, you will then need to give the relevant roles the permission Allowed to invite new users via email. Please be aware that, in order to be usable for this purpose, a role must have the Manage members permission, as well as User visibility set to All active users. You may create an additional role for this purpose, or modify an existing one accordingly.

Role configuration

If you created a new role, don't forget to assign it to the relevant users in those projects, where they should be allowed to add new users.

Adding new users to a project

With all things set, your project managers can now invite new users to their projects by going to the project's settingsMembers . All they have to do is to enter the email address of the new user in the search field, and select the roles for the new project member.

Inviting a new user via the 'New member' function in project settings

New users created this way will have a random password set and receive an email with instructions for activating their account.

Configurable life time of tracking pages in Planio Help Desk

Feature update
Added by Jens Krämer over 2 years ago

As you might already know, Planio Help Desk allows customers to view the past communication on an issue via a public tracking page. This page shows all previous communication with the customer which was either sent to or received by them.

Although each tracking page can only be accessed through its secure individual link, which is only known to the parties involved in this communication, some of our customers expressed the desire to disable the tracking pages entirely, or to turn them off after some time, i.e. once an issue was resolved or had gone inactive.

Whether you are handling really sensitive data, or just generally want to reduce the amount of information that's exposed externally, you can now fine-tune the tracking pages visibility on the project level. To do so, navigate to the Help Desk settings of your project, where under Update notifications and tracking pages, you can configure the number of days of inactivity after which tracking pages will expire and become inaccessible. Selecting Never will entirely disable all tracking pages for this project.

Tracking page visibility setting in Planio Help Desk

Please note that only external comments sent to the customer by a logged-in user will count as activity in the context of this feature. A mere change of issue attributes for internal reasons will not affect tracking page visibility.


Also available in: Atom