More often, people create a spreadsheet with one row per bug once they encounter situations like that. It's a tool failure because these activities are of cour

More often, people create a spreadsheet with one row per bug once they encounter situations like that. It's a tool failure because these activities are of course core bug tracking tasks, yet bug tracking tools tend to be a poor fit for tracking unplanned side activities. These side activities do not match the regular state progression of bugs, so in-tool tracking requires that someone creates custom logic for the emerging separate process. Usually, there aren't resources for that. (It's also hard to get rid of the excess state and logic once the side project is done.) If you have to use free-form text fields or labels anyway, the spreadsheet option isn't so bad, despite its obvious flaws.