You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Basically all the project types are the same EXCEPT for the associated workflow/workflow schemes and corresponding default issue types.
The reason they are different is to help you determine which workflow/issue types you should start to use depending on use case (hence the names: Simple Issue Tracking, Software Development, etc). Not all users of JIRA use it for bug tracking, thus why there are more than one.
And I'm finding very difficult to have a clear list of all this differences, even after paying for the Jira administrator learning pathway. I'm setting up Jira at my new job, and all the little nuances between business and software keep throwing me curved balls. For example, forms are only available on business, you can only configure the board and have multiple workflows in one board in Software, and so it goes.
All this things should be black and white and listed somewhere to guide users on selecting the best platform. Or is there something out there and I just haven't found it?
Hi Mateus, haven´t found it neither, but one of our customers prepared pretty nice table of comparison for his purposes and I shared it here: https://community.atlassian.com/t5/Jira-discussions/comparison-of-features-of-Software-project-and-Business-project/m-p/2083571#M18234 so take a look.