I would definitely recommend using this solution. 

Overall, I would rate it a nine out of ten. 

My first recommendation would be to think about what you want to use the data modeling for? Do you want to have organization per project, per customer, per product, per business? This is my recommendation, think about how to make the modeling work with what you want to do.

The scheduling feature is too complex. They should make the project management part of the course plan activity easier.

I would rate it a nine out of ten.

Atlassian is a market leader in this segment and I would definitely recommend this solution. I would just like to see more of the features available at a more reasonable cost, which would keep more people from going to the community version.

This is a good solution, but the main thing we want to see is better traceability between epics, features and stories. As it is now, there are only two levels. The link is between an epic and a story or an epic and a feature.

I would rate this solution an eight out of ten.

Atlassian is talking to me about starting to try and think about their products working together as I mentioned before. It's like an ALM-like stack.

As a general purpose tool, JIRA and Confluence are still ahead of the competition. I'd say, your first decision is to try and figure out whether you can get away with using the Atlassian On-Demand versions of the products. If you can, go that route rather than hosting your own. Just get the thing up and running, get a few users, get one team on there, and get a couple of projects.

Launch with an MVP of your Atlassian suite and then iterate. It's pretty easy to manage and enhance the configuration of the thing while it's live and users are using it.

Bitbucket's great.

Simplify how you use JIRA as much as you possibly can. Make sure you have a workflow that fits your organization and make sure the people in the organization understand the workflow.