Did you know you can file bug reports or feature requests not only against CF or CFBuilder, but also for things related to CF like the CF docs, the CF2018 PMT, the CF Docker images, the API Manager, the CFFiddle.org site, and even Tracker itself? Read on.
You may know that you can file bug reports or feature requests for ColdFusion and CFBuilder (and search for past ones or track their status) at https://tracker.adobe.com. But did you know you can file those against related things (not “inside CF”) such as the CF docs, the Adobe ColdFusion Docker images, the CF2018 PMT (Performance Monitoring Toolset), the CF API Manager, the cffiddle (online code execution/demo) site, and even the Tracker site itself!
It may not be quite so obvious how to report against those things, so in this post I help you see how.
And Adobe really does pay attention to those bug reports: you may have noticed that each CF and CFBuilder update generally includes many, many listed bug fixes, including ones drawn from this reporting mechanism.
But many never knew or noticed that they could file bug reports and feature requests against these other things that are not really “inside of” ColdFusion or CFBuilder. One challenge is that the choices in Tracker are not as obvious as they could be. Let’s take them in reverse order of simplicity (in my opinion):
- For the CF docs:
- You need to first choose “ColdFusion” as the product, and then in “component” (once CF and its version are selected, and in the very long list that appears) choose “Documentation”, or one of the few prefixed with that. (More about that long list, and my hope it may be improved, later here.)
- For the PMT:
- Again choose “ColdFusion” as the product (it’s not technically one of its own), and then in the component list choose one of the “components” that are prefixed with “PMT” (there are nearly two dozen). (This is an update from when I originally posted this. These component values were until yesterday mis-labelled as “APS”, the old name for the PMT.)
- For the CF Enterprise API Manager:
- Again choose “ColdFusion” (it’s also NOT its own product name) and then in “component” choose “API Manager”, or again any of the few prefixed with that. Like the tracker and docs points above, I agree that the names are pretty self-subscribing. I am simply pointing them out as some might presume that only “CF” issues could be raised, not these related things
- For the CF Docker Images:
- Choose “ColdFusion” and then in “component” choose one of the items starting with “Containers:”. Not quite so obvious, but ok. (Perhaps they’re preparing for a day when they offer containers in other than the Docker format.) For more on the CF Docker images, if that’s new to you, see this post when they were announced
- For the cffiddle site:
- Choose “ColdFusion”, and then in “component” choose the not-so-obvious value, “CFApps : CFFiddle”. Again, the implication seems to be that there will be other “CFApps” in the future, which is encouraging. Note you can do that for either CF2016 or 2018, the two versions currently supported in CFFiddle
- For tracker itself:
- Finally, for this note that it is indeed listed as a separate “product”, labelled “Adobe Tracker”, because there are in fact other products not related to CF whose issues are to be filed in Tracker (and we all benefit from improvements made to it)
- For the CF portal site (coldfusion.adobe.com):
- There is currently no option in the tracker site for filing bug reports or feature requests for the CF Portal. I will file a feature request for that (so meta). In the meantime, you can report portal concerns by clicking the “contact us” link at the bottom of the portal. Rather than going to some generic Adobe bitbucket, that currently triggers an email href link:<a href=”mailto:firstname.lastname@example.org?subject=ColdFusion Community Portal &body=Hi, This is regarding the ColdFusion Community Portal.”>Contact Us</a>
And speaking of filing issues against Tracker itself, I DID happen to file two yesterday related to the above. First, I filed a bug report complaining about that nomenclature of using APS for the PMT. See (and add your vote if you agree) https://tracker.adobe.com/#/view/TKR-231.
Update: Great news: I can report that as of today (Aug 2, 2019) that has been addressed. Thanks, Adobe: and it’s another testament that it really is worth filing bug reports. (Don’t anyone presume that I might somehow get special treatment: trust me, there are plenty of issues I’ve raised that remain unresolved. I appreciate that they get hundreds, if not thousands per year to be considered.)
Then I also had filed a feature request pointing out how challenging it is to choose from that “components” list for CF, as there are over 300 items! I’m sure many pick the wrong one, as it’s not easy to find the right one. I’ve asked if they might add some sort of ajax search feature, to help us filter the list down. Again, please see/vote at https://tracker.adobe.com/#/view/TKR-232. I do hope to come back and modify this post if Adobe may address that.
Finally, I filed another feature request to add the Portal as an option in Tracker, under “CF”, so that we can file bug reports or feature requests for that, at <a href=”https://tracker.adobe.com/#/view/TKR-235″>TKR-235</a>. If you agree with the concerns I’ve raised here, please do go add your votes. Adobe does take votes into consideration when prioritizing items.
But again my main goal in this post was just to let folks know that yes, you CAN file bug reports or feature requests not ONLY against CF and CFB, but also things related to CF, like the PMT, the docs, the CF Docker images, the API Mgr, the CFFiddle site, and even against Tracker itself. (Trust me, I know how painful Tracker can be as a UI. have in fact filed several other items about it.)
Hope that helps some folks.