Hi Atlassian Community 👋
I’d like to introduce iConfig, a new Marketplace app currently available in Beta.
iConfig was created for teams using Jira Service Management and Assets who need a practical way to collect hardware inventory data from endpoints and keep that data updated inside an Assets object schema.
The idea came from a very common challenge we have seen for years in customer projects, community discussions, and implementation conversations:
Many teams want to use Atlassian Assets as their source of truth for hardware, endpoints, and virtual servers, but they struggle to automate the discovery process in cloud environments, especially when devices are distributed, remote, or outside a traditional corporate network.
How iConfig is different from Assets Discovery
This is not meant to replace every use case of Atlassian Assets Discovery.
Assets Discovery is useful, especially in environments where network-based discovery and infrastructure scanning make sense.
iConfig focuses on a different approach:
| Area |
Assets Discovery |
iConfig |
|---|
| Discovery model |
Primarily network/server-based discovery |
Agent-based endpoint discovery |
| Cloud scenario |
May require additional setup, infrastructure, or connectivity considerations |
Designed to send data directly to Jira Assets Cloud |
| Endpoint support |
Depends on discovery configuration and reachable environments |
Agent installed on Windows, Linux, and macOS |
| Remote/hybrid environments |
Can be harder to manage when devices are not always on the same network |
Better suited for distributed endpoints |
| Data control |
Discovery output depends on scan configuration |
Focus on controlled collection, filtering, and synchronization |
| Real-time device queries |
Not the main use case |
Includes additional Power Query capabilities for retrieving live data from a specific device |
In short, iConfig is focused on the agent-based scenario many Assets Cloud customers have been asking for: install an agent, collect hardware and configuration data, and sync it into Jira Assets.
What iConfig does today
With iConfig, teams can:
- Install an agent on Windows, Linux, or macOS devices
- Collect hardware inventory and configuration data
- Send discovered data to a Assets schema
- Keep inventory information updated over time
- Apply filtering and control before synchronizing data
- Use Power Query capabilities to retrieve real-time information from a specific device
Beta program
iConfig is currently in Beta, and we are looking for teams willing to test it in real scenarios and share feedback.
The Beta program includes an incentivized participation model based on contribution levels, including feedback, testing effort, and collaboration during the beta period.
We are especially interested in feedback from teams that:
- Use Jira Service Management with Assets
- Manage hardware, endpoints, laptops, desktops, servers, or virtual machines in Assets
- Have struggled with keeping inventory data current
- Need an agent-based approach for remote, hybrid, or distributed devices
- Want more control over what data is synchronized into Assets
Marketplace listing:
https://marketplace.atlassian.com/apps/380331023/iconfig-hardware-inventory-discovery-agent-for-assets
Documentation:
https://idevsolucoes.atlassian.net/wiki/spaces/ICONFIG/
Support and beta contact:
https://idevsolucoes.atlassian.net/helpcenter/iconfig/
I’d love to hear your thoughts, questions, and feedback from anyone who has worked with Assets Discovery, hardware inventory, or endpoint discovery in Jira Assets Cloud.
Thanks!
Paty / iDev Soluções
