JIRA vs. Monday
-
We are seriously considering moving to JIRA so I'd love to get more in-depth response from folks regarding what they do/do not like about it.Our goal is to use it to track Scrumban development, including developer hours and budgets. We are planning on purchasing add-ons for that. Thanks.
All in all Jira's pretty decent as long as you either have an extremely experienced and empowered Jira admin running it or strictly follow the rule that anyone proposing complex and/or extensive customizations shall be summarily executed. Jira's problem is that it was designed to be flexible enough to handle pretty near any conceivable workflow including all the weird rules teams can come up with about moving tickets from one state to another (like only when Joe the manager has moved this other ticket to state B, which requires a third ticket to be in state Z, and only when the day of the month is prime). Once you've got workflows that complex, you can't hardly change anything without the whole thing breaking down, and heaven forbid you create more than a few custom fields or worse custom fields with the same name. One of the things I do at $dayjob is Jira administration, but they didn't make any attempt to contain the complexity early on so I've seen more than my fair share of Jira horrors. Anyway, Atlassian basically succeeded at making a super-flexible ticketing system at the expense of mind-boggling complexity, although reverse engineering the class hierarchy and relationships would probably make a decent project for a 500-level OO Design class. Oh, and keep your Jira small or it gets ridiculously expensive, especially since you pretty much have to get add-ons for it to work well. VSTS/Azure DevOps seems better to me for development teams, but business-only or help-desk teams would almost certainly be better off in Jira.
-
We have been using VSTS and it works pretty well, linked with TFS and all that. I prefer it over GIT and/or Jira.
I also prefer vsts:tfs over git. It was simpler and more forgiving. Git has too many commands to remember. Also tfs integrates well in visual studio.
-
All in all Jira's pretty decent as long as you either have an extremely experienced and empowered Jira admin running it or strictly follow the rule that anyone proposing complex and/or extensive customizations shall be summarily executed. Jira's problem is that it was designed to be flexible enough to handle pretty near any conceivable workflow including all the weird rules teams can come up with about moving tickets from one state to another (like only when Joe the manager has moved this other ticket to state B, which requires a third ticket to be in state Z, and only when the day of the month is prime). Once you've got workflows that complex, you can't hardly change anything without the whole thing breaking down, and heaven forbid you create more than a few custom fields or worse custom fields with the same name. One of the things I do at $dayjob is Jira administration, but they didn't make any attempt to contain the complexity early on so I've seen more than my fair share of Jira horrors. Anyway, Atlassian basically succeeded at making a super-flexible ticketing system at the expense of mind-boggling complexity, although reverse engineering the class hierarchy and relationships would probably make a decent project for a 500-level OO Design class. Oh, and keep your Jira small or it gets ridiculously expensive, especially since you pretty much have to get add-ons for it to work well. VSTS/Azure DevOps seems better to me for development teams, but business-only or help-desk teams would almost certainly be better off in Jira.