OK folks heads up. Some of you might be seeing a L...
# adobe
m
OK folks heads up. Some of you might be seeing a LOT of activity in tracker today. I'm going to tell you what is going on so you can act on things if you want to. We are exploring options for Tracker replacement or repair to make it a better experience for devs, but it is CHOCK FULL of old tickets. Stuff that has been there for years. Yes, it is our fault, long term. These are items we were never able to get around to. And SOME of these are things that either no longer matter, or the community has worked around, or were fixed in some other way. In any case, we are sorting through the very old tickets and closing each, WITH an explanation of why. IF YOU DISAGREE w/ the closing reason and still feel the ticket is worthy of pursuit, and can both show a repro of the issue and make your case, please CREATE A NEW TICKET with the information. It is impossible for us to properly sort these without doing something like this. I apologize, these should likely have been sorted and handled long before I (or much of current engineering leadership, to be fair) were here. What this does is provide us an opportunity to pull up those still critical ERs and bugs, refresh our understanding of why you might want the changes AND get current, working code samples. If you want to yell at someone about this, yell at me. After many hours of knocking our heads together, this was the most effective and optimized way to really get to the heart of which items matter most from a very, VERY large stack. Just remember, I love you all. Let the hazing begin. ❤️
1
👍 4
☝️ 1
❤️ 5
👍🏼 1
a
I was wondering. It's good to see some action of any sort on these.
❤️ 1
m
Apologies ahead of time also for the dent in your inboxes lol.
😅 1
a
It's interesting that the fix version for a bunch of mine are being set to
15
. That'd be CF2023 according to my reckoning. Should it not be
16
? These are things that aren't fixed.
(ie: so they are NOT in 15, and that ship has sailed)
m
Adam can you dm the ticket numbers that have that. That seems incorrect, unless they were repaired in the latest patch
But this is EXACTLY why I wanted to highlight this, I want to catch items like this and make sure we are accurately building out a planned vector for culling and executing against these bugs and ERs
👍 1
t
@Mark Takata (Adobe) I have a bunch of those too -- you want 'em?
m
Tim, yes please. DM me or email takata@adobe.com with them, whatever is easiest for you. Thank you!
c
All the ones I've gotten (over a dozen) have shown 15. Before I forward them to you, I'll wait to see if perhaps there may be news or some change, unless you still end up wanting to get them. (And thanks for the news/heads up on the situation.)
👍 1
m
Thank you all, I'm in communication with the team.
g
Hopefully users that submitted the ticket will get the email that their ticket was closed. I checked a while back and noticed that many were "closed due to inactivity/non-response", but I don't have any record of having received any comments or a notice to close. It seemed like they were all "silently closed without any notice" IMHO.
I noticed that statuses changes aren't logged, so I've been taking the automated status change emails that I receive and manually add them as comments so that there's a history of actions (or inactions) taken. Hopefully the new ticket system will maintain a log of changes to a ticket's status.