Blossom vs Axosoft

An update is posted to the Slack channel every time a task is created, completed, moved, or commented upon.

Design focuses on clarity.

Turn emails into support incident tickets. A brandable self-service portal can be created for customers to create and edit tickets without using paid Axosoft accounts.

Tasks are divided into categories and each category can have one or more workflows which are followed by tasks belonging to that category until their completion.

In other words, workflows are used to set each step tasks need to take in order to be completed. Axosoft lets users have extremely fine-grained control over workflows and by extension, the whole lifecycle of each task. Each step in a workflow can be named and you can choose which fields are updated when a step is complete. This way you can automatically tweak tasks as they progress (you can set tasks to belong to different users once a step is complete, you can even change workflows for a task if a certain step is taken).

Each item has a PDF button (among others) which lets you export all the information related to that particular item in PDF format.

Axosoft lets users pretty much create custom dashboards any time they want to view only a specific part of the project data and information.

You can choose which tabs to keep open and even how tasks are shown and what kind of data is shown for each task. This way you can see for example how much time is left in a sprint, or how much capacity the team has left to finish the project.