@Joe_Makopointed out to me yesterday by a PM that the export & package tool for Alteryx has a known defect, where the nested macros (a macro inside a macro) don't export properly.
That set me thinking - what's the best way for the community to log defects, and I'm wondering if there's a place for a section on this forum for defect reports? That would also make it easier for the Alteryx team to parse out defects (which folk like @ned care very deeply about) from other types of posting.
This would have to be heavily curated though - in my experience, a large number of defects raised for systems I've managed over the years have not been defects, but actually users not understanding the tools - however these did give us very valuable insight into usability; training; etc.
So - if we had a "Potential defects" section, and if the more senior members of the community had the ability to curate along with alterxy, we should be able to do something good here:
Curate actions needed:
- move some to "Ideas" if they are new functionality
- move some to one of the discussions thread if they are actually a usage question
- Escalate some to the technical leads at Alteryx
- the alteryx team could workflow them in the same way as the ideas but with an additional step of "replicatable example pending from user"