How do I report a bug in InDesign to Adobe?

Unfortunately I can't reproduce it as I have overwritten the artwork file (that had the problem) as I needed to resupply the artwork for a re-print, so it was updated last Tuesday (after the last InDesign update to 18.5). I have the previous INDD file from before the issue arose, and it views perfectly, BUT I can't replicate the issue as both items, the InDesign app has been updated from 18.4 to 18.5 and the INDD artwork file are newer versions than at the time of the problem.

no the text was hidden by the text box which had shrunk between InDesign updates.

Thank you!

I have posted my issue to Adobe.

Yes, I'm sure its an Adobe bug. I've been using InDesign since its very first version (and Quark Xpress before that, for many years) and this is the first time that this issue has ever happened.

I have recently sent a peice of artwork to print, saved as a press-ready pdf. My client got the job printed BUT three text boxes were missing the last line of the text. The missing text was visible right the way through the amends stages until I created the final artwork file, at which point three text boxes (out of a total of about 60 boxes) had shrunk fractionally in height and hiddent the last line of text.

Point one - These were not altered in any way before the PDF was created. I used the same file as before for artwork, and just changed its name.

Point two - The PDF flight check should have flagged up over-set text but it did not.

My only suspicion is the InDesign did an auto-update between version 7 of my amends and the final artwork version, and this version altered the text boxes slightly (we are talking fractions here— I literally touched the text boxes in question, and the text re-appeared), BUT even if it did shrink the text box, it still didn't flag the 'over-set text' issue up at PDF stage.

I alone have worked on every stage of this document, so its not necessarily a font issue, as I only have one cut of the font, so I can only assume its happend due to a software update. Unless you can think of any other reason that this might have happened?