About this software
Commercial Backlog Integration subscription for JetBrains IDEs that connects the IDE to Backlog issue tracking. It enables browsing, searching, and linking Backlog issues from the IDE and associates issue references with code changes. Licenses are sold as one-user, one-year subscriptions through JetBrains third-party plugin licensing. The plugin is distributed via the JetBrains Marketplace and maintained by the integration vendor.
Purchase
JetBrains 3rd Party Backlog Integration
In Stock
Delivery: 1 working day
Loading...
€11.80
Free and without obligation
Do you need more information or looking for another license?
Benefits
- IDE issue access: View and search Backlog issues without leaving the IDE.
- Create and link issues: Create and link Backlog issues from code and commit messages.
- Traceability to code: Associate issue IDs with commits for traceable changes.
- Marketplace distribution: Delivered and updated through the JetBrains Marketplace.
- Commercial licensing: Sold as a per-user yearly subscription via JetBrains sales.
Available languages
- English
Support information
- Documentation: User and setup documentation is available on the Marketplace plugin page.
- Vendor support: Functional and integration support is provided by the plugin vendor.
- License management: Licensing, renewals, and invoicing are handled through JetBrains sales channels.
- Updates delivery: Plugin updates are published through the JetBrains Marketplace.
- Issue reporting: Report bugs or feature requests via the plugin vendor's issue tracker linked on Marketplace.
Frequently asked questions
What is JetBrains 3rd Party Backlog Integration?
JetBrains 3rd Party Backlog Integration connects JetBrains products with external backlog systems to exchange issue and task data, enabling synchronization of items, status updates, and comments based on configured mappings.
How does data synchronization work between JetBrains and external backlogs?
Synchronization is configured with selectable field mappings and sync directions; changes are propagated according to rules and schedules, with conflict handling defined by integration settings.
What authentication and permissions are required for the integration?
The integration requires credentials and access tokens with sufficient permissions to read and write backlog items; exact credentials depend on the external backlog's authentication methods.
How are field mappings and workflows handled during integration?
Field mappings and workflow transitions are mapped between systems during configuration; custom fields can usually be mapped to equivalent fields or stored in designated locations.
What troubleshooting and logging options are available?
Integration typically provides logs, error reports, and retry mechanisms to diagnose sync issues; review logs to identify mapping conflicts, permission errors, or connection failures.