Planio Support

When connecting to Planio, we always use secure and encrypted communication channels, namely TLS (also colloquially known as SSL) and SSH. The use of cryptographic algorithms in these protocols have changed over time, resulting in newer and more secure standards being used and taking the place of older standards. In the last couple of years, there have been a number of published attacks on some of these older standards such as POODLE, Logjam, or DROWN. While there have been workarounds for some of these attacks, some can not be fully mitigated without retiring the use of the affected cryptographic standards.

As a result, starting June 18, 2018, Planio will discontinue the support of the older cryptographic standards TLSv1.0 and TLSv1.1.

This applies to all HTTPS connections to your Planio account, to Subversion and Git repositories accessed via HTTPS and connections to our Team Chat servers if you are using an external IRC client.

The vast majority of connections to our servers already use the more modern standards and are thus not affected by this change at all. If you are using a reasonably modern webbrowser which was updated in the last couple of years, it likely already supports and uses the more secure and modern cryptographic standards. Reasonably current versions of Git and Subversion clients should also have no problems accessing our servers after June 18.

If you are using older versions of Java to access our Servers, e.g. with the use of plugins to your IDE or with CI servers, you might have to ensure that your version of Java is up-to-date. When using Java JDK 8 or newer (released in 2014), everything should work as before. Older versions of Java however disabled TLS 1.2 by default for compatibility reasons. Older versions of OpenSSL (which might still be used by old operating systems like RedHat 5) might not be able to access our services after June 18 anymore and might need to be updated.

Should you face any issues accessing our services after June 18, please make sure you have updated your clients to their latest version. For any questions related to this change, please don’t hesitate to get in touch with us via https://plan.io/contact/.

For some time now you've been able to import issues into Planio using CSV files. Today we have greatly improved the issue importer. Additionally we've added imports for time entries and Planio Help Desk contacts.

We've documented each import in great detail in specific guides: issues, time entries, and contacts.

But here are two of the new features:

Over the last weeks we've been busy enhancing Planio Help Desk. We've made it easier for you to keep your customers in the loop about changes to their tickets.

It's always been possible to select attributes, which should be visible to the contact. They are shown on the tracking page of each issue. Now we've enhanced the list of available attributes further. Additionally it's now possible to select an email template for automated update notifications, which will be sent to your contacts whenever one of the selected attributes is changed.

This keeps your contacts up to date and saves you from writing the same update messages to your contacts over and over. We've added a default update notification template to your account as an inspiration.

Furthermore attributes, which are visible to your contacts, are now highlighted within the issue form. In the project's help desk settings you may select which fields should be public and which ones are considered internal.

Along with these new features we've also improved the management of companies and contacts. You may now directly create and edit these records from within the issue form. This will be especially useful for contacts which have been created automatically via Planio Inbox.

Up until now, the handy Atom feeds Planio provides for repositories would always include all commits on all branches. It wasn't possible to get notified for new commits that happened only on a certain branch, like your production branch for instance.

Well, now it is. The screenshot above shows how you can get your Atom feeds for individual branches. So, yes, now you can get notified about commits directly in your Slack channel via their RSS integration.

Or, you could simply use Planio Team Chat where all Planio events feed into your channels automatically.

Warning: Be careful when sharing your Atom feed URL, though. Unless your repo is public, the feed URL will include your individual Atom access key! It may be a good idea to create a separate user with limited permissions for your integrations.

日本のお客様向けのアップデートです。 の一環として、日本の提携先の ファーエンドテクノロジー と共に準備をおこない、新規のアカウントにおいて planio.jp TLD（トップレベルドメイン）が利用できるようになりました。

今日2017年11月15日より、Planioの日本語サイトから無料お試しを行ったアカウントは、新TLD planio.jp がデフォルトのTLDとなりました。以前からPlanioをご利用いただいている日本のお客様も、画面右上のアイコンをクリック→「管理」→「設定」からTLDを変更できます。

今後、さらなるTLDの追加と、近隣でのデータセンターの利用ができるようになる予定です。ご期待ください!

This is an update for our Japanese users. In the spirit of moving off of plan.io, we have been working hard with our friends from Far End Technologies to make planio.jp available for new account registrations.

Starting today, any new Planio account registered via our Japanese web site will already get the new TLD by default. Existing users from Japan can switch their TLD via your avatar → Administration → Settings.

Stay tuned for more new TLDs and Planio coming to a data center near you soon.

我々はPlanioをセキュアに保つための活動を継続的に行っており、すべてのアカウントは最先端のセキュリティ技術で保護されています。先日、ユーザーアカウントの保護をより一層強化するために、 多要素認証 に対応しました。

QRコードを読み取って二要素認証を有効化

本機能により、ユーザーは2つ目の認証要素として、TOTP(Time-Based One-Time Password Algorithm)によるワンタイムパスワードをアカウントに追加できます。ワンタイムパスワードを生成するためのTOTP対応アプリはPCやスマートフォンなど多くの環境で利用できます。TOTP対応アプリの一例としては、 Google Authenticator 、 Authy 、 IIJ SmartKey などがあります。

ユーザーは「個人設定」画面で本機能を有効にできます。必要があれば、システム管理者は全ユーザーに対して二要素認証を必須にできます（画面右上の自分のアイコン → 管理 → 設定 → 認証 → Two-factor authentication）。この設定を行うと、全ユーザーは次回のログイン時に二要素認証の設定を求められます。

最後にはなりましたが、重要なことを一つお伝えします。二要素認証の設定を行ったTOTPアプリが利用できなくなった場合（例：スマートフォンの紛失・故障など）に備えて、バックアップコードを生成・保管することができます。二要素認証の設定を行ったユーザーは、バックアップコードの生成・保存も行うことを強くおすすめします。

Up until now, your Planio account would always have a URL in the form of yourcompany.plan.io. Starting today, we're enabling users to choose other top-level domains as well. Beginning with yourcompany.planio.com and ihrefirma.planio.de (for our German customers), we will be adding more local TLDs in the coming months.

Feel free to navigate to your account → Administration → Settings to select a new domain for your account. You will also be able to choose a new subdomain if you so wish.

Yes, that means that we're gradually moving off of plan.io as our primary domain. However, your Planio account will always remain available on plan.io in addition to your new Planio domain - if you choose one - so no links will be broken.

Pro Tip: You can also get your own domain (how does projects.yourcompany.com sound?) including a custom SSL certificate for a small monthly charge. Get in touch if you're interested.

We're constantly at work to make sure the Planio platform and all accounts are protected by state-of-the-art security techniques. Today, we are introducing two-factor authentication to further improve the security of user accounts.

With this feature, users can add a second authentication factor to their account using an app supporting the TOTP (time-based one-time password) scheme. Such apps are available for most major platforms, for example Google Authenticator, Authy or Duo Mobile.

Users can activate this feature in their My account area. If required, administrators can make two-factor authentication mandatory for all users in their Planio account via your avatar → Administration → Settings → Authentication → Two-factor authentication. All users will then have to set up their second factor at their next login.

Last but not least, users can also generate and print backup codes to use should they lose access to their TOTP App. We highly recommend that administrators who activate two-factor authentication for their account also generate and print backup codes.

Many of our clients are using Planio Inbox and Planio Help Desk in their projects to handle and centralize incoming and outgoing email with external project partners.

Today, we're improving how incoming emails are handled by Planio with 3 small new features/changes:

Regular expression support for mail body delimiters¶

Most email clients will include the entire previous email thread with every single new email reply. After a while, emails get longer and longer and become hard to read. Luckily, Planio keeps the issue history clean by cutting off that email thread, adding only what's new. In order to do so, it uses a set of delimiters to detect when the main email is over and the rest of the thread starts. You can set your own delimiters via Your avatar -> Administration -> Settings -> Incoming emails. By default, Planio includes delimiters like:

--- Please write your response above this line ---
-----Original Message-----
Sent from my 

Now, you will also be able to add regular expressions here to detect patterns used by some email clients. One that makes sense for instance would be On .+ wrote: as it would match lines like On Wed, 11 Oct at 1:05 PM, Jon Smith wrote:

Regular expression support for excluded attachments¶

Another challenge with incoming emails are file attachments from signatures. Many emails contain an image file that's part of the sender's signature. After a bit of back and forth, you'd end up with a bunch of file attachments on a single issue all displaying the logo of that company the contact works at. Until now you could filter out these attachments by filename and we've added regular expression support here as well. Adding something like .*footer.*\.(gif|jpg|jpeg|png) should effectively remove all images having the word footer in their name.

No more mandatory field checks for emails from external contacts¶

Up until now, all incoming email to issues in Planio would be checked against mandatory (custom) fields as set for your trackers. For emails from external contacts, this made little sense in most configurations as external contacts aren't allowed (or wouldn't know how to) set issue attributes in the email body. Hence, we're now ignoring these checks when an email is received from an external contact and Planio Help Desk is active. In all other cases, mandatory fields remain mandatory of course and will be checked against.