The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
+1 for post-it notes. I have found it to be a very effective workflow to write my assigned Jira tickets onto post-it notes, work off the post-its, and then reconcile my work back into Jira the day before the PM does reporting.
As for Monday, I haven't tried it, but I don't like them because I keep seeing ads for it almost every day.
VSTS is OK, but in preferring TFS over Git makes you quite a rare find.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself."
Have not used Monday - but also found Jira to be slow and clunky. Asana is another option that is quite usable. Teams has some limited capability with a good UI. My recommendation would have to be silolog.com which is simple and effective.
My problem with post-it wall is that eager cleaning lady buzzing around with her vacuum cleaner while leaving the windows open to get some fresh air...
And another minor issue might be when you have one or more remote teams. Sending the pictures of your post-it wall whether during stand-ups or each time after you move a ticket can be a bit ehm 'funny'
We use Redmine - I've always found it pleasant to use & stays out of my way. It allows enough customisation to be useful for our needs and information can be extracted using a REST API, which makes collating things into reports for management easy enough.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
My imprevision of JIRA is it is first a ticketing system, then development workflows added on.
Monday.com is similar, a ticketing system for any work type.
VSTS (or Azure DevOps for the year old naming) - does a lot, same as Jira, but is first a development ticketing system. Out of the box link code changes with work items. More hassle if you want 1 subscription account, but 10 other people that just need basic view options.
Yes, we use JIRA. I wouldn't say it's the greatest ever, but most of our problems come from the people using it, not from the software itself. It does seem as if I've noticed some problems here and there though.
I agree. Tech tools related to processes should be geared for the team's process, not the other way around. If the team has a bad process, then they will just port that into the tool. The tool will get blamed, and the team continues to suffer under bad processes.
Keep all things a simple as possible, but no simpler. -said someone, somewhere
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.
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.