+1. The structure is very thorough. To avoid verbosity, we can suggest to leave any section not applicable to the specific issue empty, such as 'Volume', 'Bucket', 'BlockId' etc.
On Tue, Mar 24, 2026 at 1:56 AM Wei-Chiu Chuang <[email protected]> wrote: > Hi devs, > > I'd like to propose adding a bug report template to Jira for Ozone. Often, > reporters write detailed explanations of what happened, but fail to include > the bug's impact, relevant logs, or workarounds. That makes it hard for > anyone else to assess the bug's severity. > > A sample template is shown below. Is it a good idea? Is the template too > verbose? What else should be added? Please share your thoughts. > > Steps to Reproduce > > 1. > 2. > 3. > > (Include exact commands, configs, or API calls) > ------------------------------ > Expected Behavior > > What should have happened? > ------------------------------ > Actual Behavior > > What actually happened? Include exact error messages. > ------------------------------ > Logs > > (Include relevant snippets with timestamps and component context) > > Paste logs here > > ------------------------------ > Identifiers (critical for debugging) > > - > > Volume / Bucket / Key: > - > > Container ID(s): > - > > Pipeline ID(s): > - > > Block ID(s): > - > > Trace ID / Transaction ID: > > ------------------------------ > Frequency > > - > > Always reproducible > - > > Intermittent > - > > Happened once > > ------------------------------ > Regression > > - > > Yes (previous working version: ___) > - > > No > - > > Unknown > > ------------------------------ > Workaround > > (If any) > ------------------------------ > Additional Context > > Anything unusual (recent upgrades, disk failures, compaction, scaling > events, etc.) >
