Planio Support (english)

Planio Team Chat now fully supports all the advanced IRC features of Palaver, including mobile push notifications and IRCv3 style timestamps as well as chat history playback on connect.

Simply use the credentials you find in the sidebar of your project → Chat logs to sign in with Palaver.

Due to the recent disclosure of a security vulnerability with the long-deprecated DSA key signing algorithm (CVE-2016-2178), we will be turning off DSA support for Planio's Git access via SSH this Friday, June 10, 2016 at 16:00 UTC.

Should you still be using a DSA key, please generate a new key pair to maintain access to your Git repositories. You can find out if you're using DSA by navigating to Your avatar → My account → Public keys. Make sure that all your keys start with ssh-rsa. Should you find any keys starting with ssh-dss, please remove them from Planio and generate a new key pair on the respective client, e.g. by executing ssh-keygen -t rsa -b 4096 on a command line. After that, please upload the new key to Planio.

Should you not use Git or DSA keys, you will not be affected by this change.

Any README files in your Planio repositories written in Markdown or Textile will now be rendered automatically on the main repository view. Markdown and Textile files and file attachments in issues and other Planio objects will also be rendered.

Wiki pages may now be exported to OpenDocument text files (ODT). They can be viewed and edited with Microsoft Office 2010 and later, OpenOffice, LibreOffice as well as a number of other word processing applications.

At the bottom of each wiki page, you will find the ODT link, next to the other supported export formats. The resulting document will map the most common formatting to default formats within Word, embedded attachments will be included in the export.

Issues and journal entries which involve external contacts using Planio Help Desk or are marked as private now sport a new look making them more coherent with the new design we've launched for Planio a few months ago.

You can now receive Planio push notifications on the desktop with current versions of Safari, Chrome and Firefox, even when you're not currently using Planio. In addition to the Planio mobile app, Chrome on mobile devices can now receive push notifications as well.

This change replaces our previous in-browser notifications which supported less browsers and were more resource-intensive for servers and clients.

We fixed a bug where the Planio Team Chat IRC server would not respond properly to a /WHO command when the requested user had a login name that wasn't all lowercase.

The repository web hooks we're sending whenever new commits get pushed to your Git repositories hosted on Planio now contain the pusher, i.e. the user pushing to the repository as well as the ref, i.e. the branch or tag that has been pushed to. Should you push several braches or tags at once, we will now call your web hook URL several times – once for each ref that has been pushed to.

The format and behavior mimics GitHub web hooks very closely. So, should you wish to integrate Planio with a 3rd party service which accepts GitHub-style web hooks they will most likely also work with Planio now.

Please note: Due to the changes, calling /sys/fetch_changesets manually or from external services will not trigger the web hook configured in your Planio repository anymore.

Links to the incoming email source of an issue have been made more prominent and been moved to the right and the OpenPGP encryption/signature details have been restyled to be in line with Planio's new flat look.

Within Your avatar -> Administration -> Roles and Permissions -> select a role -> Issues visibility, you now have a new option Issues watched by, created by or assigned to the user.

Users with a role having this issue visibility will also see issues in a project if they have been set as a watcher. You can therefore easily involve restricted users in individual issues on a per-case basis.

Please note: Be careful with assigning the Add watchers permission to roles using this setting, because that will effectively allow those users to extend the permission to other users as well.