Jira new pricing tier to –$765,432,091.03 per user / month(atlassian.com) |
Jira new pricing tier to –$765,432,091.03 per user / month(atlassian.com) |
It takes 247 years to open the form to fill the details for the ticket.
E.g. we were forced to switch from Jira to Rally, and it turns out that Rally is much worse.
I guess someone is panicking and trying to fix it live
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.
https://www.protocol.com/bulletins/atlassian-jira-outage-wee...
https://www.bleepingcomputer.com/news/technology/ongoing-atl...
I guess someone at Jira is having a bad day.
Really, I wonder where these numbers come from...
They must be A/B testing.
You can't void for Unilateral mistake unless it's egregious, but this is egregious.
Standard $790 a year User tier: 0 - 10
Premium $1,525 a year User tier: -987654320 - 10
Atlassian would have thought they'd get a free press but instead they're rightly getting ripped apart with sarcastic references to their own product.
Standard -$765,432,091.03 per user (average) -$7,654,320,910.25 a month
Premium -$1,506,172,824.28 per user (average) -$15,061,728,242.75 a month
Like, in JS: 0.3 - 0.2 - 0.1 === -2.7755575615628914e-17 // true
However they did not state for how long is offer valid, so they will be able to change pricing tiers later.
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.
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.
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.
