The JIRA >> Canny implementation came at the worst possible time, while we're attempting to integrate PBR into the mainstream and there are literally dozens, if not hundreds of tiny edge cases, weird anomalies, and full on render glitches that need to be tracked, matched, and addressed. I'm in the process of trying to track 3-4 issues, of "stuff that renders as an errored monochromatic color". Some of these are GL-drawcolor fails ( solid pink ) some of these seem to be environment-divide-by-zero problems that may have existed before PBR was ever introduced. But I can't associate any of these variants with their potentially related prior reports since I don't have access to JIRA anymore. I keep getting told "the old JIRA issues were backed up". Well, I don't have access to them, and neither does anyone else as far as I'm aware, so how exactly are we supposed to link knowledge together? I can't even look at my old JIRA issues anymore to refresh my memory about the exact circumstances that something occurred. This is very important to me. Even if we managed to re-report every old JIRA issue on Canny, there's no way to "Mark as Duplicate", or for that matter, Mark as Non-Duplicate. As often with graphics related issues, you can get two behaviors that are nearly identical, that are from two completely distinct causes, and it's important to be able to reference the other issue, and say "this error is visually similar, but it's NOT caused by the same problem as 'this other thing' ". Currently I can't even associate potentially related issues, because Canny Search doesn't have enough adequate filters, so unless I want to go digging through every issue reported since the launch of the platform, I can't even filter my search by a reporter ( unless this is user error on my part? I can't even figure out how to filter it down to issues I've reported myself!! ) How is anyone trying to do meaningful bug-tracking supposed to work with this? Canny's great for people who go "I'd really like it if the viewer let me automatically hide unused poseballs" and just wish-upon-a-star for a new feature without actually caring if anyone else has wished for the same thing, but for reporting ACTUAL bugs, and tracking them, this is nearly useless, to the point where I've resorted to just writing them down in text documents and discord servers so I have some reference point that I can keep stuff organized in. This platform doesn't even have convenient text formatting unless you know some magic asterisk voodoo ( which I literally just figured out I can do ... but why isn't this an option in the text header box? ) !! if ( user ) { displayFormattingOptions = 1; // For most people: // Having undocumented features is functionally- // identical to not having the feature // to start with. // FYI :: surrounding text in // one asterisk gives *italics* // two asterisks gives **bold** // three asterisks ***bold italics*** // You're welcome random person // who searched 'formatting' // https://xkcd.com/979/ } Apparently I can post code blocks too, but while some of standard markdown formatting works __some does not__ ~ but more importantly none of this is documented anywhere ! Why aren't there buttons??! I figured it out by flinging symbols at the wall and seeing what sticks. At least Discord lets me conveniently highlight stuff and coordinate things. I can even reference a prior post and go "Hey this is related, click this little link thing and read it." Also in Discord, I can "Filter by user" and store relevant data like I could on JIRA. When your new bug reporting platform is getting outperformed for bug-reporting purposes by just "let's make a Discord channel and paste stuff into it", there's a serious problem. Please give us access to a tool that is functional for actual issue reporting and tracking. Thank you~ -- Liz ( formerly Polysail ) PS: Canny is great for just yeeting ideas onto the internet and then forgetting about them. It's Twitter, without a character limit and less X's. While that notion is potentially appealing in some capacity, it's not practical for bug-triage.
