it's because these products aren't consumer products - they are business products. You often won't find business products run off ads, because business products have a value proposition which is positive, and thus the business would pay for it.
Now someone should open a Jira ticket, refine the task, estimate it, define its priority, push it to the backlog and maybe the next sprint (if it is important enough), someone will be assigned, checking all the DoD and DoR boxes, submit a PR, getting it approved and then it will be fixed.
I wish it was that easy! You are missing the 'triage' state after the ticket is opened, the 'review' state after priority, and the 'approval required' state after moving to backlog, sprint and fixed.
Plus all the other steps in the custom workflow some upper management spent weeks putting in place without speaking to the actual workers who need to follow it.
I'd say first try for yourself instead. I have, for over a decade, and while it's pretty slow and has some annoyances: it's not quite bad enough to hate for me, the alternatives aren't that much better and mostly have other annoyances, and it can get the job done.
Jira is much better than a lot of similar products and people in this post seem to think that their dislike of their job is caused by their tools and not crappy PM process.
Jira's main problem is that for most developers, this enormous piece of enterprise software is strictly inferior to a swimlane app they could build in a week. Lots of features in there for the benefit of managers and PMs that ultimately amount to more administrative work and process for developers.
Some places it's bad enough that Jira is used to appease the people with the purse strings, and the inputs have no bearing on reality at any given moment, while all the real workflows are tracked using paper note cards pinned to a cork posterboard that sits on Joe's desk behind his monitors.
Jira's slowness became worse and worse in the past ~5 years. I used to remember the Jira hate and not understanding it because it indeed got a bad rap because people blamed Jira for a shitty PM process - with a proper process, Jira itself wasn't bad and I enjoyed using it.
However the last few times I've used it, it wasn't the PM process that sucked - in fact I loved my PMs because I got to offload most of the Jira upkeep to them and never touch the tool myself. However every time I have to use the pile of shit myself I end up mumbling quite colorful language.
I think people just hate all the administration that needs to happen when dealing with large task backlogs in general. This hate gets projected onto Jira, but it's not clear to me that there is a good alternative.
E.g. we were forced to switch from Jira to Rally, and it turns out that Rally is much worse.
OK I recognize that, currently dealing with a salesforce product that is painfully slow. Seems the company that purchased that solution can't do anything about it.
"Fix it live" or "Fix it in production" is basically JIRA's entire MO.
I get that move fast and break things is supposed to, in the end, ensure better code, better debugging and ultimately a better experience.
But the way JIRA does it (And a few other companies) is, quite frankly, painful to see, even on the sidelines.
Like that time they just straight locked folks out of their tenants if their tenant name started with number or something. They do thing, often without any aux plans to revert. Its pants on head crazy imho. How key executives listed in their stock portfolio pages didnt lose their jobs over that is beyond me.
I wonder if any legal minds here could comment on whether they owe me $1.5billion if I sign up for this. Technically it's an offer with consideration that I'm accepting, and happy to pay $-1.5billion for this service, even though I know that trying to get this to stand up in court would be a fools errand.
There are all sorts of things in law about “reasonable persons” and contracts needs to be beneficial for both parties. I am sure this would not be binding.
The only thing is though that the "reasonable persons" have seen it fit and reasonable to let an algorithm set their pricing. This will generally work in their favour but why shouldn't I as a customer be able to take advantage if they've purposefully chosen to let an automated process set the pricing of their contract?
I'm not a big Atlassian hater, but the other day I spent 7 hours trying to fix an account migration error. Two users had access rights and all, but couldn't see any repository. I ended up deleting them and adding other accounts. It was ... odd. Oh, and there's that thing of joining an empty workspace. And that other thing. Yes, there's quite a bit wrong under the hood. Feels like teams working on small features that don't work well together (either the teams or the implementation).
Is that the case? I was under the impression that Decimals were used in financial contexts because (besides preventing floating point error) you can define how to handle things such as rounding behavior.
For instance, at least in Python, 3//2 == 1 while -3//2 == -2; integer division is rounded down, and not towards zero as one may expect. Decimal lets you pick how you want that to go.
Generally decicents (10 decicents = 1 cent) makes all normal currency calculations much easier/reliable. If you need lower resolution use millicents or microcents
OK, so this is hilarious, buy I'd be really interested to know where that figure comes from? (obviously an error since its not pulling in the normal cost, but what's it pulling in instead?)
