This is a conversation I'm having sometimes:

User: Let's add an auto-calculated field into this ticket!

Me: Sure, but why?

User: You see, at the end of the week we export all this data into an Excel spreadsheet and run a custom calculation macro to get to the final costs. But if we implement this calculation into the ticket layer, the export will already have the final costs calculated.

Me: Understood, but what I mean is, why? What's the actual benefit here? You're asking for a few weeks of work, three people involved, and an added potential risk surface. The payoff has to be real — so, is it?

User: I think so — that Excel file is so large already that running the macro crashes my computer!

Me: Ok, that makes sense. Let's first have a look at how much your department relies on Excel, and then let's look at the calculation itself.

An integration / automation request like this is already a proposed solution to a problem.

At this point, it's good to do a little push-back and find out what the problem actually is — and if it's actually worth solving.