Add configurable scrum report sections, saved templates, and GitHub data filtering

[mariobehling]

The Scrum Helper Chrome Extension currently generates scrum reports using a fixed structure and automatically fetched GitHub data. This limits flexibility for different teams, roles, and reporting styles.

Actual Behaviour

• The extension automatically fetches pull requests, issues, and reviewed pull requests based on the user’s GitHub username.
• All fetched data is inserted into a fixed format scrum report.
• Users cannot control which sections appear in the popup.
• Users cannot filter, sort, or selectively include GitHub data before it is added to the report.

Expected Behaviour

The scrum report should be configurable and adaptable to different workflows.

The feature should allow users to:

1. Enable or disable individual scrum report sections such as blockers, tasks, pull requests, reviewed pull requests, and issues using simple UI toggles.
2. Save their selected layout and section configuration as a reusable template.
3. Persist user preferences using local storage and automatically reload them across browser sessions.
4. Filter GitHub data before insertion into the report, allowing inclusion or exclusion of pull requests, reviewed pull requests, and issues.

Benefits

• Increased flexibility for different scrum formats and team processes.
• Reduced manual cleanup of autogenerated scrum reports.
• Consistent reporting through reusable templates.

Acceptance Criteria

• A configuration UI is available in the extension popup or settings view.
• Individual scrum report sections can be toggled on or off.
• User preferences are stored in local storage and restored on reload.
• GitHub data can be selectively included or excluded based on user settings.

Optional Enhancements

• Support multiple saved templates.
• Add basic sorting options for GitHub items, for example by update time or status.

[Mateeb-Haider]

@mariobehling Hi, I’ve started working on this feature.
I’m planning to implement an initial version and iterate based on feedback.
I’ll keep this issue updated with progress.

[Preeti9764]

@Mateeb-Haider Can you please raise a draft pr for this so that it may be known about the work progress on this issue .

[diyasharma12]

I’ve raised a PR addressing this issue. Please have a look.

[Mateeb-Haider]

Hi @mariobehling 👋

I’ve submitted a PR related to this feature and would really appreciate it if you could take a look when you have some time. I noticed another PR was opened earlier as well, so please feel free to review them in the order you find appropriate.

Happy to make any changes or improvements based on your feedback.

Thanks a lot for your time and for maintaining this project!