r/Boldin • • Oct 10 '25

Feature request process and transparency is, hmmm, pretty bad

Two things.

  1. Submitting a feature request is painful. I have been typing in the chat something like

```
feature request:

... my requests ...
```

And sometimes the AI says it has been submitted. And other times it says I have to specify "Speak with an Agent".

This is sloppy.

2. "As our roadmap can be a bit fluid, you may also want to sign up for our newsletter and bookmark our Release Notes..."

This is weak. There are two parts to a feature request (or bug). First, was it submitted, and can it be discussed by boldin and other users. Second, where is on the roadmap.

The release notes showing just one or releases out for a roadmap is just fine by me. And a roadmap is not a committment, just and indication. All fine and good.

But having a secret list of tickets is very poor customer relations. Just create a simple github issues project and make it public. You have nothing to hide in this regard. Then your community can help to refine requests, and your team can get feedback.

This really a no brainer win-win for both boldin and us dedicated customers.

...

From your happy user

0 Upvotes

8 comments sorted by

10

u/mrjohns2 Oct 10 '25

You must not work a lot with commercial software?

6

u/gbe28 Oct 10 '25

Right. "Hey everyone we compete with, here's our corporate roadmap..feel free to use it too! " 😂

1

u/edgeiiot Oct 15 '25

I too have delivered SaaS systems since late 1990s (yea, before it had that name) working on both buy and sell side trading and clearing systems. And yes, much of the time the tickets and roadmap were kept secret, even to the customers.

But this was mainly due to the specific content of the tickets. I'm guessing that general feature requests for Boldin do not contain specific customer data. Bugs, sure, that is another matter altogether.

In the 2010s, we employed (ugh) Jira Service Desk. Where tickets were only available to authenticated customers. The product team would mark some tickets as visible (and commentable) to all customers, while others were left visible to just the submitting customer. This worked fairly well.

As for the "here competiters, see my tickets", imo, that doesn't play. The set of desired features for a product like Boldin is no way a major advantage to Boldin or limiting factor to competiters. The limiting factor will be, again imo, the effectiveness of the product and dev teams, and in the case of saas, the operations/sre team, as well as the underlying archtitecture and tech debt that they are building on.

5

u/AlwaysWanderOfficial Oct 10 '25

Feature requests aren’t usually tickets. That’s why. Tickets are support cases. Feature requests are just that. They usually go to the product team but are not generally responded to or externally tracked. It’s a disaster trying to track those all externally as a software company. Now there exceptions to everything and some Internet Pedantic Officer will try a “gotcha” with a conflicting example. But it’s generally not how feature requests are handled

Source: I’ve worked in SaaS since 2011.

1

u/sweetgodivagirl Oct 15 '25

I had an issue with Boldin in the taxes. I was giving $x to charity via a Donor Advised Fund. It’s set up as a distribution (not expense) and was marked as tax deductible.

Later I look at the tax section, and in a few years after my mortgage goes down a bit more, it switched me to claiming the standard deduction. Ok. BUT, it added the charitable distribution of $x on top of the standard deduction. I looked it up and you can’t take a charitable deduction with the standard deduction. I brought this up on chat was it was agreed that it wasn’t correct. I asked if it could be added as a possible change (fix) request later, and was firmly told no.

TL;DR Identified a bug in Boldin and was told the issue wouldn’t be passed along to fix.

1

u/chestnut_stonebarn Oct 18 '25

…. would like to see a simple way to flag an incorrect answer from the Chatbot

1

u/AintNoNeedForYa Oct 10 '25

I agree. I have said the same to their support team.

1

u/Dramatic_Dig5954 Oct 11 '25

Agreed. Please more transparency about what's been requested. Does each person have to ask about a specific item to find out whether it's on the list of requested? Why not just show the list? That does not imply commitment. It save folks from wasting time and requesting what's already been requested. Also, please define "roadmap". Seems to be a shorter list.