We’re excited to share that Strongpoint’s Jira Integration, built on Atlassian’s Forge platform, is relaunching today.
Want the full details? Click the link below!
Netwrix Strongpoint Jira Integration 2.0.1 Released
Jira Integration, built on Atlassian’s Forge platform, keeps your NetSuite and Jira workflows in sync automatically. Create a Jira ticket, and Strongpoint generates the matching NetSuite change request, with existing or proposed customizations attached.
What that means for your team:
- Eliminates double entry between Jira and NetSuite
- Automatic status sync between environments
- Create change requests for any connected NetSuite account
- Stronger traceability and audit trail between tickets and changes
Here’s what’s changed
Our team has run extensive fixes and testing cycles to address the issues reported after the initial launch, and we’re confident this version is significantly more stable and reliable.
The Jira Integration connects your NetSuite and Jira workflows to save your teams real time on every change request.
Action required to get the fixes: This update won’t apply automatically, you’ll need to manually update on both sides:
- NetSuite: Update Bundle 311231 to the latest version.
- Atlassian Marketplace: Update to the latest Strongpoint app package.
Both updates are quick, but the integration won’t reflect these fixes until you’ve done them, so please update as soon as possible. If you’d like to test things out first, you’re welcome to update your Sandbox environment before rolling the update out to Production.
Bug fix list
| Description | Case # | Escalation # |
|---|---|---|
| Added fix to support JIRA API integration tokens with configurable scopes. | 426253 | 474767 |
| Fixed characters overriding each other when typing quickly in JIRA Forge fields. | 423382 | 473326 |
| Fixed JIRA statuses not syncing correctly with the Forge app. | 422540 | 472882 |
| Fixed automatic synchronization issues between the Change Request and JIRA ticket using the Forge app. | 433252 | 476091 |
| Added fix to support special characters in JIRA status values. | 418517 | |
| Fixed inconsistent behavior of the Push button. | 418518 | |
| Loading indicator now displays when opening the JIRA Forge tab. | 418520 | |
| Fixed Lookup Customization returning values from a previous filter instead of clearing them when closed. | 442514, 444142 | |
| Fixed Impact Analysis record links to Netsuite Customization records. | 442524 | |
| Fixed proposed customization not pre-populating prefixes as expected. | 442525 | |
| Fixed Approved CR status not transitioning correctly to other mapped statuses. | 444667, 450664 | |
| Fixed Lookup Customization sort-by-name column not sorting correctly. | 444143 |
Enhancements in 2.0.1
- User Story 418510: Locked user interface while Change Request (CR) is being pulled into JIRA.
- User Story 444145: Loading indicator now displays when opening the Netwrix NetSuite Settings page.
Need help with this update?
| Situation | Action |
|---|---|
| If you feel the product is broken and not working as intended… | Contact Support |
| If you have a question you’d like to ask other experts… | Create a discussion in the community: Strongpoint for NetSuite > Discussions & Questions |
| If you have a feature request… | Let our product team know directly: Strongpoint for NetSuite > Ideas |
| If you have something cool to show… | Show everyone what you built: Strongpoint for NetSuite > Show & Tell |
What are your thoughts?
We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!