[trelliscoded]

I wouldn't be worried about Jira so much, I'd be worried that management is going to implement New Processes to Keep an Eye on the developers.

Above a certain scale you kind of need an issue tracker, but when you're serving it instead of it serving you, it's the implementor's fault, not yours.

One of the reasons Jira comes up so much is that it's so customizable that it will merrily allow you to construct the most Byzantine nonsensical workflow you can think of, and fairly quickly too. It's not Jira's fault that someone told it to do so.

It really sounds like they couldn't find a manager capable of handling both teams, so they're going to throw technology at the problem instead of investing in their people to grow them into the position. It might work if they are willing to pivot quickly based on user feedback instead of just dropping New Process on you, but it's always slower to manage that way instead of just hiring a competent manager.