Create feature request template with utility class dropdown and Solenopsis use case

[sfloess]

Problem

Current feature_request.yml template is generic. Need jcommons-specific fields to understand which utility class is impacted and Solenopsis framework usage.

Proposed Template Enhancements

Add Utility Class Dropdown

Help categorize feature requests:

• SoapUtil
• StringUtil
• FileUtil
• ArrayUtil
• ClassUtil
• LoggerUtil
• ObjectUtil
• UrlUtil
• New utility class
• Other

Add Use Case Field

Question: How does this feature assist with:

• Solenopsis Salesforce SOAP operations?
• Session management?
• General utility handling?

Rationale: jcommons is foundation for Solenopsis framework - need to understand downstream impact

Keep Existing Fields

• Problem Statement
• Proposed Solution
• Title: [FEATURE]:

Benefits

• Better categorization by utility class
• Understand Solenopsis ecosystem impact
• Prioritize features aligned with framework goals
• Faster maintainer triage

Template Location

.github/ISSUE_TEMPLATE/feature_request.yml (currently exists)

Implementation

Update existing template with:

1. Add utility class dropdown (required)
2. Add use case textarea (required)
3. Update description to mention Solenopsis context

Related

• Part of v2.0 migration preparation
• Aligns with Solenopsis framework goals
• Improves feature request quality

[sfloess]

✅ Fixed in commit 27c5119 - See 27c5119 for details.