Abacus - Calculator for Jira

[6/14/18] We've been using Abacus for a couple years now with good success. Abacus is a flexible, easy-to-use app at a very affordable price that does exactly what it says. Great for project-based calculations, especially at Epic and other Issue Type levels (think a Bug score calc). Have not found another add-on that can do broad field calcs in the JIRA Cloud environment without diving into something much more complex (and expensive) like a ScriptRunner. What pushes this review from 3 to 4 stars is the Mumo team. I've had a number of interactions with them, both over email and phone (even a couple in JIRA), and they are extremely responsive. 2 of the 3 suggestions I raised in my original review from 2016 have been implemented to some degree, which is pretty impressive to me. They've also not just responded to my inquires but made suggestions to me about how I could better implement Abacus to make it faster and less of a resource hog. A few remaining suggestions: 1) Create a better global control for enabling scripts across projects. The new "shared" formulas are really nice for updating a script across multiple projects, but they still have to be added to new projects one at a time. That can take a long time when adding to dozens of projects. 2) Shared execution plans or (even better, imo) execution plans that are linked to the shared formula and copy automatically with the formula. 3) Combine numeric calculation and rollup calculation options. For example, I'd like to create a formula that rolls up custom estimation field (in days) and then converts that (to weeks). Right now, I'd have to rollup to the Epic and store in field A, then do a custom calc that saves in Epic field B. This wouldn't be so bad except you can't use hidden fields to store Abacus calcs [maybe another mini-suggestion right there]. 4) Would still like to see Read-only field support added for Epic rollup formulas. it's already there for Generic formulas. Thanks Mumo for a useful add-on! Edit [4/18/17]: RE: Delays, thanks for the response. Bulk edit actually works quite well; the changes are almost instantaneous. What I've seen are some calcs that simply never go through, no matter how long you wait. The only way to trigger a calc is to go in and manually change the Result field (e.g., to zero), update the issue, and then a few seconds later the calc actually works. Have not figured out the logic of why some issues calc fine from the get go, but others using the same calc in the same project require this follow up step. Edit [3/30/17]: Have seen some temporary delays (15-20 minutes is longest reported so far) with the destination total field being updated after the source fields have data. Causes some confusion to users when the total does not update immediately.

• 

  Mumo Systems

  Thank you Zack. We appreciate the feed back.

  As for delays, are your users doing gigantic bulk edit of issues? If so, processing will not be instantaneous. Just like when you do a bulk edit in JIRA, it takes time to process each issue.

  #update 7/1/2017

  We discovered some client instances WebHook are delaying calling Abacus to do calculation. That is why there are some delays. We tested and verified this by turning on the WebHook on the said instance to call https://requestb.in. Our average response time is 110ms. Let Atlassian know that the WebHook in your instance is slow and they will take appropriate steps to fix the issue for your instance.

Abacus is wildly extensible and allows us to really customize our workflows to our needs. Any time I've ran into issues, they've been there to help and support our needs.

Had an issue with an existing configured Execution Plan. Raised this to the helpdesk, and the Abacus team assisted in finding out the root cause of the issue and an alternate solution. Furthermore, the team provided assistance in making the configured Execution Plan's more efficient. Much appreciated.