Feature Groups and Themes Renamed to Backlog Groups
In the Winter 2015 release, the feature group (or theme) asset was renamed to backlog group. The functionality remains the same and any company-specific localization changes will override this update.
Who Uses This Information
- Product Owners and Scrum Masters: Understand the terminology change when working with existing backlog group data or reviewing historical documentation.
- System Administrators: Manage terminology preferences and company-specific localization that may override the default "backlog group" naming.
- Team Members: Recognize that references to "themes" or "feature groups" in older exports, reports, or documentation refer to backlog groups.
Permission Requirement
No special permissions are required to understand this terminology change. Standard permissions for viewing and managing backlog groups remain unchanged (Read access for viewing, Edit access for managing).
What Changed
The Winter 2015 release renamed:
- Feature Groups → Backlog Groups
- Themes → Backlog Groups
All functionality remains identical:
- Hierarchical functional groupings still work the same way
- Parent-child relationships and rollups unchanged
- Filtering and reporting capabilities preserved
- Historical data automatically carries forward under the new naming
- API references updated to use "backlog group" terminology
Company-Specific Localization
If your organization has custom terminology configured, those preferences override the default "backlog group" naming. System Administrators can manage terminology in Administration > Configuration > Localization. Custom terminology appears throughout the application interface, reports, and API responses.
Troubleshooting
Why do I still see "themes" or "feature groups" in my system?
Your organization may have company-specific localization configured that overrides the default terminology. Contact your System Administrator to review terminology preferences in Administration > Configuration > Localization.
Why do exported reports show "feature groups" instead of "backlog groups"?
Older exports or reports generated before the Winter 2015 release show the previous terminology. The underlying data remains the same—"feature groups" in historical exports refer to what are now called "backlog groups". If generating new exports, they will use current terminology (or your company's custom terminology).
Does this terminology change affect integrations or API calls?
API endpoints were updated to use "backlog group" terminology. If you have integrations created before Winter 2015 using "theme" or "feature group" endpoints, review API documentation and update integration code to use current endpoint naming. Historical data remains accessible through updated endpoints.