A few weeks ago, we launched the latest enhancement for TRS (Tracked Resource Set) in OSLC Connect for Jira. This update is especially relevant for teams already leveraging the IBM Engineering Lifecycle Management (ELM) suite. Whether you're a Jira administrator or a systems, software, or QA engineer, this release is all about making your data integrations more robust, scalable, and manageable. Now, let’s jump into the details of the TRS enhancements.
What is TRS and Why It Matters?
TRS (Tracked Resource Set) is an interface provided by OSLC Connect for Jira that exposes a list of Jira artifacts and their changes. These artifacts are pulled by two different types of indexers used by IBM ELM—LQE for reporting (via Report Builder or Engineering Insights), and LDX for link discovery and tools like DOORS Next and ETM.
Maintaining an accurate, up-to-date TRS feed ensures that your Jira data is correctly represented in ELM's applications. For organizations relying on traceability and compliance, TRS is a key mechanism to allow ELM tools to access Jira data.
The Challenge: TRS at Enterprise Scale
We know that at enterprise scale, TRS indexing can be a bottleneck. When dealing with thousands or even millions of artifacts, the load on Jira and the indexers can become significant. Bulk events, such as mass project changes or imports, exacerbate this load.
Our goal with this release is to:
- Increase confidence in the accuracy and freshness of indexed data
- Minimize performance impacts during peak usage times
What’s New: Key Enhancements in the TRS Release
1. Improved Jira Cluster Performance
We've optimized how membership is calculated and validated. This leads to faster operations and better responsiveness within clustered environments.
2. Deferred Bulk Operations
Project additions or removals are now scheduled for off-peak hours. This reduces user impact and balances data access with enterprise responsiveness.
3. Enhanced Administrative Tools
- Repair vs. Rebuild:
→ Rebuild: Still available, but reserved for forcing full re-indexing (remote applications re-reading ALL artifacts) when absolutely necessary.
- Forced Update:
- Artifact Status Check:
- Scheduled Repairs:
- Audit Logging:
Track when changes occur and what modifications were made for better transparency.
Testing TRS resources for visibility and update times, one of the key enhancements of this new Release
What Does This Looks Like in the Product?
The updated admin screen provides:
- Clear indicators if permissions are misconfigured (e.g., non-admin access warnings)
- Tools to test TRS resources for visibility and update times
- Manual validation and repair options per project or globally
- Rebuild and forced update buttons with informative prompts to guide best practices
- Real-time feedback by watching remote indexers process the updated feed
These visual and functional improvements provide greater control and insight into TRS behavior, reducing reliance on support while improving self-service capabilities.
📺 Watch the full feature walkthrough and demo here
CONCLUSION
The TRS enhancement release is a significant step forward in making your Jira-to-ELM integration more scalable and maintainable. With better scheduling, more granular control, and performance improvements, you can now manage large-scale indexing with confidence.
Whether you're ensuring reporting accuracy in Report Builder/Engineering Insights or maintaining traceability links in the ELM Suite, these enhancements will help your teams work smarter.
Next Steps...
- Explore technical documentation: docs.sodiuswillert.com
- Reach out to our support team with any questions
- Stay tuned for more updates aimed at optimizing your engineering workflows
✨Thank you for using OSLC Connect for Jira! ✨
Leave us your comment