Project

Profile

Help

Blog

New Guide: How to use the Planio Inbox

Guides and Support
Added by Ema Raven 3 months ago

Ever wondered how the to use Planio Inbox and update issues in Planio via email? With our new guide, you can learn exactly that!

Every project in Planio has a built in project inbox, allowing you to create and edit issues via email and on the go.

Email inbox in each project in the sidebar

Check out our step by step guide and learn all about how to create and update issues on the go with the Planio inbox: https://plan.io/using-the-planio-inbox/


Comments

Please register to add a comment

Seamless Visualization: Embed Mermaid Diagrams in Planio

Feature update
Added by Jens Krämer 4 months ago

You can now embed Mermaid diagrams in Planio - on wiki pages, in issue descriptions and notes, basically in all places that support Markdown formatted text.

What is Mermaid?

Mermaid is a simple markdown-like script language for generating charts and diagrams from text. With its intuitive syntax, it allows you to create flowcharts, sequence diagrams, Gantt charts, and more, making complex information easily digestible.

Elevate Your Project Documentation

Effective communication is at the heart of successful project management. Now, with the ability to embed Mermaid diagrams in task descriptions and comments, you can provide clearer context, streamline information, and enhance the overall understanding of your project's intricacies. Whether you're brainstorming ideas, explaining processes, or seeking feedback, visual aids can significantly enhance the quality and efficiency of your team's communication.

Your project's wiki is a central hub for information. Now, you can enrich it further by embedding Mermaid diagrams to illustrate workflows, system architectures, or any other visual representation that enhances comprehension. This feature ensures that your team has a holistic understanding of the project's structure and processes.

How to Embed Mermaid Diagrams in Planio

Simply wrap the Mermaid syntax in a mermaid code block directly in issue descriptions, notes, and wiki pages. For example, you can create a flowchart with the following syntax:

``` mermaid
graph LR;
    A-->B;
    A-->C;
    B-->D;
    C-->D;
```

which results in this diagram:

graph LR;
    A-->B;
    A-->C;
    B-->D;
    C-->D;

You can use the Preview tab to check the diagram state while you're editing it. These code blocks can as well be generated using the </> icon in the formatting toolbar (be sure to add mermaid to the Code highlighting toolbar languages list under Your Avatar -> My Account).

Using Textile?

If your Planio account is still using Textile as the formatting language, you can embed Mermaid diagrams using this code block syntax:

<pre><code class="mermaid">
graph LR;
    A-->B;
    A-->C;
    B-->D;
    C-->D;
</code></pre>

As an administrator of your Planio account you can also contact us to have your account converted to the more modern Markdown syntax free of charge.

This new feature is now live in Planio, and we can't wait for you to explore the possibilities it opens up for your projects. Be sure to check out the Mermaid documentation to learn more about the many different kinds of diagrams you can create.

Update on Subversion Commit Hooks

Feature update
Added by Jens Krämer 8 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.

Require Two-Factor Authentication for Specific User Groups

Feature update
Added by Jens Krämer 8 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 about 1 year 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 over 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 over 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 almost 2 years 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: https://plan.io/bulk-editing-issues/

Opening the bulk edit menu

Planio Issue usage improvements

Improved features and updates
Added by Ema Raven over 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.

(1-10/80)

Also available in: Atom