Adobe Tracker

Mike's Notes

Pipi has no way for users to;

• Search for bugs or feature requests
• Add a bug
• Add a feature request

I read in Feedspot a link to a recent post by Ben Nadel that led to a bug report using Adobe Tracker. I wrote some notes about Adobe Tracker to remind me to design and add a Pipi Tracker.

Resources

• https://www.bennadel.com/blog/4821-closures-do-not-work-in-adobe-coldfusion-custom-tags.htm
• https://tracker.adobe.com/#/search
• https://tracker.adobe.com/#/view/CF-4227145

References

• Reference

Repository

• Home > Ajabbi Research > Library > Subscriptions > Feedspot
• Home > Handbook > 

Last Updated

14/07/2025

Adobe Tracker

By: Mike Peters

On a Sandy Beach: 14/07/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Search Example

This is what I could make of a unloggedin search using Adobe Tracker

Product		(Select from a list)
Type		Bugs & Features | Bugs Only | Features Only
Version		(Select from a list)
Priority		(Select from a list)
System		(Select from a list)
Frequency
Browser		(Select from a list)
System		(Select from a list)
Title
Reported By
Description
Test Configuration
Component		(Select from a list)
Failure Type		(Select from a list)
Reason
Fixed in Build
Found in Build
Created At	= | < | >
Votes	= | < | >
Attachments	= | < | >

Bug Example

This is a copy of a search result that discovered a recent bug reported by Ben Nadel.

ID	CF-4227145
Title	Closures do not work properly in custom tags
Description	Problem Description: A closure, defined in a custom tag, does not close over its lexical scope; and fails to retain binding to custom tag page context when passed out of scope. Steps to Reproduce: My example: https://bennadel.com/4821 1. Define a closure inside a custom tag that references a closed-over variable. 2. Pass closure out of context (using `caller` scope as example) 3. Try to invoke closure from calling context. Actual Result: Error: closed-over variable is not defined. Expected Result: Closed-over variable should be available. Any Workarounds: Not that I've been able to find.
Comments
Status:	Open
Details
Date Created:	02/07/2025
Component:	Core Runtime
Version:	2025
Failure Type
Found In Build:	2021 and 2025
Fixed In Build:
Priority:	Normal
Frequency:
System:
Browser:
Reason Code:
Votes:	1