Cons: We have been using the Cloud version of Jira.
Pros: Deploying JIRA at our company generated a lot of excitement from process-oriented people, as it worked very robustly at tracking action items within the team.
Cons: It takes a lot of set up to get it working the way you need it to.
He has it set up in a way that is easy to follow and works for our team.
At first I was having a bit of trouble understanding exactly how this should be achieved but after digging around it ended up being pretty easy.
You will need to configure local repos underneath your Redmine project that are updated fairly regularly and then after they are updated you will need to run a script that updates the any ticket that code has been associated with.
So if you only have one instance of Redmine you can remove all of the DEV labeled items from the script below.
There are numerous items that need to be changed to reflect your server environment including paths, app locations, and the log file.
Git Clone Each Project: Now below is the cron entry which in my case is again for the web user.
There are times that new updates happens and it might take a bit to figure out new functionality or GUI changes.
Great to connect the product manager, UI/UX designer, dev team, myself, etc.
Cons: The setup and administration is a bit of a learning curve and does require some work for the customization and setup.
It is a heavy software: installation demands the typical attention of enterprise software.