Parrolabs and its predecessors have had a history of using different Tools for project management. We have used Pivotal Tracker, Asana, Trello and have in the last year made the leap over to Atlassian’s Jira.

Jira was always the more corporate focussed big brother of Asana. Where Asana to me was more a tool that anyone can use, Jira originally seems to be focussed on a corporate way of doing things. Their templates were very much Software oriented, something that our creatives or Assistants would find hard to work with.


We were reluctantly convinced by one of our clients to move over to Jira. We were just used to our at the time beloved Asana and were getting used to the fact that we had a lot of flexibility. However, as our team started to grow, people started to deviate too much inside of projects and processes  started to become too much non-standard.

So initially we started using Jira for only our client’s project and while initially we felt that we were trapped inside of a tool, soon we started seeing the benefits. Configuring Jira for your needs is a real pain. There are too many buttons and we would recommend anyone starting with Jira to consult with a specialist in Jira for the initial configuration. It can literally mean avoiding weeks and months of pure frustration. There are many different Projects and settings. Soon you will find your Creative Team working in one way and your Assistants in another as their boards aren’t the same.

We made the mistake of going it alone, but eventually hired a consultant to get us sorted in the right direction. Jira has been improving a lot as well. One thing that we love is their automation features, which allow us for example to clear tickets from our board after 1 week. Before we had to remove each ticket individually but now they are deleted automatically.

More recently we were made aware of scheduled tickets. That feature is phenomenal. It cost $0.50 Cents Per user Per month, but can safe years of our lives. Imagine any repetitive task that the team needs to complete. For example, each month we need to get our Payroll rolling where multiple people need to do tasks and things are linked together. So we are now having a template for that. Same goes for our Social Media Tickets. As a project co-ordinator, or Manager it saves us a lot of frustration and it will literally get a lot of the tasks out of our head.

These features bring Parrolabs from a Small Company to a larger one as people can work more within their role. Many of the tickets will appear automatically setting off a string of tasks for the team. That reduces workload and frustration by a lot.


While, I do feel that we have not gotten to use Jira to its full potential. I think that we have gotten very far. Every month we evaluate the usage and we increase the knowledge of our team overtime. Overall, we are very happy with how this has played out. We are now running very efficient.