Apache Subversion vs Jira Software

• Revision control done properly - you have end to end visibility of all changes in the project.
• Conflict resolution - visually highlighting the differences helps to track down the problem.
• Being open source and very popular.
• We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years.
• Rollbacks are made simple and easy to use.

Read full review

• JIRA offers a lot of integrations that really improve our work. For example, the Salesforce integration makes it really easy to link Salesforce product roadmap cards (relevant to the entire product team) to an individual JIRA issue (one specific task-relevant to that team).
• JIRA offers very good search and filter functionality. The quick filters make it very easy to immediately see only my own issues. You can create custom views, which are especially helpful for my team during our daily standup, allowing us to only see relevant issues.
• JIRA issues come with lots of customizable fields. Due dates, assignees, labels, priority level, epic link, etc. -- makes it very easy to organize and find specific issues.

Read full review

• Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
• Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
• Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.

Read full review

• Make certain the full end to end processes are documented - changing flows will impact the lineage of your data
• Make certain someone on the team has JIRA experience or have a vendor support you in the implementation
• Look at full functions offered out of the box and understand additional plug-ins that may be needed.

Read full review

• I cannot speak on ROI but Apache Subversion is definitely the best version control tool for a project of any size. It serves the user's purpose in a complete satisfactory way.
• As it is open source, there is no need to spend any amount on it, which makes it an even more easier choice.
• The most negative impact Apache Subversion can have on you is that you will not want to use any other version control tool after using it.

Read full review

• Sprints management is relatively simple and straightforward.
• As our organization matures, we will be able to take more advantage of JIRA's reporting tools to help us refine our processes.
• By keeping things relatively simple and transparent (everyone can view all tickets -- no crazy permission schemes), the entire org has visibility into our development process.

Read full review