Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jira new pricing tier to –$765,432,091.03 per user / month

atlassian.com

Post reply on HN
Print view View original

71–80 of 86 posts

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#71

Post by gizajob »

wodenokoto wrote: post #15
gizajob wrote: post #6

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?

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#72

Post by heywire »

oaiey wrote: post #62
stinos wrote: post #56

Earlier quoted context omitted.

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.

it is actually one of the better ones in the field.

Get stuck using Mercury, err, HP, umm, I mean Micro Focus Quality Center for 15+ years and JIRA will feel like a breath of fresh air.

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#74

Post by Ensorceled »

Dionakra wrote: post #61

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.

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#75

Post by pedrovhb »

cube00 wrote: post #20
HelloNurse wrote: post #17

Earlier quoted context omitted.

Under the hood they might prefer to do accounting in floating point. BigDecimal isn't meant for true programmers.

My life got infinitely easier once I learnt the financial world all use integers in cents to do their money calculations.

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.

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#76

Post by wcoenen »

Maxburn wrote: post #18
anotherhue wrote: post #5

“JIRA acknowledges that it is a net negative to humanity”

So much hate everywhere for this product, I'm glad I don't use it.

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.

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#77

Post by Haydos585x2 »

stinos wrote: post #56
Maxburn wrote: post #18

Earlier quoted context omitted.

So much hate everywhere for this product, I'm glad I don't use 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.

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#78

Post by girvo »

Ensorceled wrote: post #74
Dionakra wrote: post #61

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.

Re: Jira new pricing tier to –$765,432,091.03 per user / month

#79

Post by Nextgrid »

Haydos585x2 wrote: post #77
stinos wrote: post #56

Earlier quoted context omitted.

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 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.

Post reply on HN