Earlier quoted context omitted.
Wow, that sounds like the most communist thing I've ever read in a ToS
Probably because you have absolutely no idea about what communism is.
Jira Is a Microcosm of What’s Broken in Software Development
161–170 of 182 posts
Re: Jira Is a Microcosm of What’s Broken in Software Development
#162OP sounds like someone who's unhappy working on big software projects. That's understandable. But once you're on a big project, you can't keep it all in your head. You can't make your own clever adjustments when problems arise without documenting everything and then taking it through channels. For what it's worth, sales people have the exact same complaint. They can get testy, too, about executives using software-ove…
Is not the process, it's the broken tool. Broken file uploads, general wonkiness and all the minor irritations that just don't get fixed.
Managers choose jira. Developers will create a process but will choose tools that work.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#163Earlier quoted context omitted.
> performance By Atlassian’s ToS, you are not allowed to « comment on the performance of the products ». I know no-one thinks this would be enforced here, but I just want to highlight that it doesn’t help a company to improve if they know they can just lawyer-up a problem away and avoid benchmarks and being compared on that topic.
This is from Atlassian's ToS (d) incorporate any Cloud Products into a product or service you provide to a third party; does this mean that I can't integrate JIRA into a ticket tracking workflow that I build for my product with IFTTT that creates a new ticket when someone sends an email to a support alias? (e) interfere with or otherwise circumvent mechanisms in the Cloud Products intended to limit your use; (f) reve…
Re: Jira Is a Microcosm of What’s Broken in Software Development
#164Hi Sean here. I work on Jira at Atlassian and I also met with Justin and the Jira Admin for his company prior to this article. I've also heard from him since. He was not consulted re the use of his comments. Generally, I'd encourage vendors to seek permission when citing a customer in marketing in this way. It's a simple respect that can be paid with low effort. I thought it might be helpful to share a few thoughts o…
It would be more helpful to share your thoughts here.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#165Usually Jira sucks because it's not setup correctly to support teams' workflows, instead it's used to impose workflows on teams. Jira can be as heavy or lightweight as you make it, but most of the suffering I see is because the way teams work isn't being supported by the Jira owners/admins.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#166Earlier quoted context omitted.
But at what expense? Does Jira ever frustrate you? Imagine how it frustrates developers that hate working with overly complex time-sink software. I can change my email client. I can change my text editor to my liking. I can change nearly any other tool I use, but when a company uses Jira, I'm trapped using something that mostly gets in my way.
I don't have the choice. I am just a cog in the wheels and it helps us do our job. It's not really in the way, if that's the case it sounds like your processes or workflows are messed up. I've had days where I don't want to see it, but that's because I'm tired of working. In those times it quick to blame Jira.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#167Usually Jira sucks because it's not setup correctly to support teams' workflows, instead it's used to impose workflows on teams. Jira can be as heavy or lightweight as you make it, but most of the suffering I see is because the way teams work isn't being supported by the Jira owners/admins.
Sounds like a microcosm of what's broken in software development.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#168I recognize that this is a marketing blog, but it blames Jira for what are really culture problems and/or bad management practices. This is an emblematic quote: Take subtasks, for example. The invention of Jira subtasks is an affront to dev teams. Clearly someone who has never spoken to an engineer on a dev team created it. It’s the least dev-friendly way possible to get insight into what’s happening with a Jira stor…
This. Jira is a framework for building something which approximates your actual processes. > Justin said “I wish Atlassian would sit down with real-world developers and design this product the way we need it to work.” The way 'you' need it to work. The process 'you' use. I suppose it's possible to build a business on creating a completely bespoke ticketing system for each company which uses one. Over time, that busin…
Re: Jira Is a Microcosm of What’s Broken in Software Development
#169Earlier quoted context omitted.
If you are not a developer, spreadsheets are a tool that lets you get similar capability in many cases. It is basically no-code for accountants, portfolio managers, and non software engineers.
Cool. If you have a spreadsheet that's longer-lived than a few hours, you should probably evaluate whether you're adopting the best approach. You can replace a blown fuse with a penny, too, but you should probably call an electrician instead.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#170I recognize that this is a marketing blog, but it blames Jira for what are really culture problems and/or bad management practices. This is an emblematic quote: Take subtasks, for example. The invention of Jira subtasks is an affront to dev teams. Clearly someone who has never spoken to an engineer on a dev team created it. It’s the least dev-friendly way possible to get insight into what’s happening with a Jira stor…
P.S. Look at this discussion for example https://jira.atlassian.com/browse/JRASERVER-4446 , subtasks concept is hard.