@Mark Takata (Adobe) when I search the bugbase for Product: ColdFusion Type: Features Only Status: [all selected except "Closed"] Reported by: Cameron I would expect the results to be raised by someone with "Cameron" in their name. First one on the results list: https://tracker.adobe.com/#/view/CF-4215050, raised by... "Robert S." Erm...?

The reported by filter has never worked for me.

Ah!

Thank you for reminding me that the Tracker needs to be thrown in a wood chipper lol

I seriously don't understand why when the dev(s) concerned first stepped back and looked at what they'd produced they didn't just look at each other and go "nah we fucked it lads", and threw it out and started again.

I'm just gonna sit here and quietly nod.

First time I've known you to be quiet, Mark? #KettleMeetsPot

I'm speaking softly but wielding a big stick behind the scenes.

This is how I like it.

I've said it before and I'll say it again. Adobe can completely replace the tracker with a new one, but what I don't understand is why they would want to spent 10s or 100s of thousands of dollars on new software licensing and/or development when they could invest just a few hours a week of someone's time into making these small improvements in the existing tracker. And furthermore, if Adobe can't invest in tiny little fixes in the current tracker, what makes anyone think they'll spend any more time improving their next tracker software? I know everyone loves to chant, "_She's a witch, burn her!_" when the tracker comes up, but I think the current tracker, as crusty and odd as it is, could be made 300% better with just a little love here and there in the mean time.

This is all just a front for Jira anyhow, isn't it? Pretty sure someone said that in the past. But yeah, even if it is... just fix the bugs. Rewriting from scratch is not a good real-world plan (am sure Mark was just indicating shared irritation more than suggesting it as an actual action?)

Yes Brad. I know you've said it. And as I've told you in the past, if it really was that easy, I would have made sure to get it done. So, unless you think I am really that incompetent, try to understand that getting things done in an enormous enterprise like Adobe is just a touch more difficult to pull off than in a small, lean, agile company.

As someone who worked at Macromedia for ~6 years and Adobe for ~1 year, I can attest that Adobe is truly enterprise-grade corporate and trying to get anything change is a bleedin' nightmare. It's why I quit after just a year.

To be clear, I'm not calling anyone's competence into scrutiny here. In fact, it's because of the sea of red tape at Adobe that I hold my current view. Given the level of effort in getting anything done, budgeting time to incrementally improve the current tracker is the clear winner over pushing for a totally new tracker! I never said either of those options were simple, quick, or easy. I said it's a fools errand to be pushing for a new tracker, especially if the prospect of getting a new on in the future is keeping Adobe from wanting to put an resources into the current one. My point is, until some glorious day in the future when Adobe decides to make some monumental move off the current solution, let's continue to make those small incremental improvements to what we have, because if we do, I think most people will stop complaining about it as much. And when I met @Aditya Nema recently, he brought up the idea of a new tracker, and I told him exactly the same thing. It's not really that bad, it just needs love, which is a significantly smaller ask than a rewrite.