Skip to main content

Jira - NetSuite Integration App release notes (2016 - 2019)

Laya Kodam
  • Updated

Contents

2019

2018

2016

Maintenance Release notes v1.4.4, November 2019 

What’s new

Changes announced by Atlassian 

Atlassian announced major changes to Jira Cloud REST APIs to improve user privacy back in April of 2019. These changes affect your Jira - NetSuite integration:

  • Atlassian removed personal data from the API such as username and userKey and recommends that you use Atlassian account ID (accountId)to identify users.
  • Atlassian has restricted the visibility of personal data like email for:
    • Users: visibility is based on the privacy settings of a profile. 
    • Managed accounts: visibility settings that are decided by the site administrator.

Impacted flows in Jira - NetSuite Integration App

The following flows were affected by changes announced by Jira:

  • Jira User to NetSuite Customer
  • NetSuite Customer to Jira User
  • NetSuite Employee to Jira User
  • JIRA Time Tracking to NetSuite Tracking

To more about the changes refer to the deprecation notice on Jira Cloud platform Developer.

What’s fixed

With JIRA - NetSuite Integration App version 1.4.4 maintenance release, all flows are compatible with your Jira platform. 

JIRA Time Tracking to NetSuite Time Tracking

Work logs entered via the Log Work in Jira were not syncing back to NetSuite. The integration app used the Jira userKey to sync and identify previously synced records in NetSuite Employee and Customer records. Since the Jira userKey is obsolete, the integration app fails to validate the NetSuite Employee and Customer records that were synced with Jira. 

The Jira - NetSuite v1.4.4 release now identifies a NetSuite Employee and Customer using the Jira identifier accountId.

Workaround: Sync your records using “accountId”

Since the identifier that recognizes unique records between the two apps has changed from username and userKey to Atlassian account ID or the accountId, the integration app is not able to determine the records that were previously synced between NetSuite and Jira. 

You need to sync Netsuite Employee to Jira User once again. The integration app now identifies records from NetSuite and Jira using the Jira accountId. 

We’ve introduced a new custom field JIRA ACCOUNT ID in the following flows: 

  • NetSuite Employee to Jira User
  • NetSuite Customer to Jira User

You’ll be able to see the JIRA ACCOUNT ID from the Custom tab under an Employee record.

444.png

Jira Customer to NetSuite Customer flow 

Previously, the “Jira customer to NetSuite Customer” flow was erroring out because of the switch from username and userKey to Atlassian account ID or the accountId. We’ve changed the mappings in line with the changes announced by Atlassian.

New mapping

Export field (Webhook)

Import field (NetSuite)

user.displayName

entityid

user.displayName

companyname

user.key

custentity_celigo_jira_user_key

user.accountId

custentity_celigo_jira_account_id

emailAddress

email

“3”

subsidiary.internalid

 

New import lookup

["custentity_celigo_jira_account_id","is","{{user.accountId}}"]


What’s Enhanced

Atlassian introduced the Automated Log Work feature in Jira. With release version v1.4.4, the “JIRA Time Tracking to NetSuite Time Tracking” flow now syncs Automated log work data from Jira to NetSuite.

555.png

Image: You can now log your work for a NetSuite Customer using Automated Log Work.

666.png

Image: Employee record in NetSuite from where you can view the Automated log work for a Customer.



Release notes v1.4.0, October 2018

What’s new

NS customer to JIRA connector flow, we are providing a saved search feature wherein the customer can choose the exact item that needs to be synced in JIRA.

777.png

Release notes v2.2.0, November 2016

What’s new

In this version of the JIRA - NetSuite Connector we have introduced support for JIRA Service Desk and introduced more setting options to give you better control on the integration. JIRA Service Desk is a layer built on top of the core JIRA product; customized to support the needs of customer service teams. It introduces new record types such as JIRA Customer and new Issue types.

  • JIRA Customer and NetSuite Customer - With JIRA Service Desk, customers can maintain details of their customers in JIRA and create support tickets for them. This data flow syncs these JIRA Customers as Customers in NetSuite ensuring that the customer information is always updated in NetSuite. Also when support tickets from JIRA are synced to NetSuite as Support Cases they are associated with the appropriate customer. This flow is bidirectional in nature and NetSuite Customers can also be created and updated as JIRA Customers.
    aaaa.png
  • JIRA Support Tickets to NetSuite - JIRA Support Tickets are nothing but JIRA Issues of a different type (e.g. Problem, Service Request etc.). The Connector supports creating these JIRA Issues as a NetSuite Issue or Support Case based on your business processes.
    bbbb.png
  • Time tracking information from JIRA to NetSuite - In the earlier version, the Connector only supported syncing Time tracking information from JIRA to NetSuite for an Issue which is synced as a Project Task in NetSuite. We have expanded this feature and the Connector can now sync Time tracking information from JIRA to NetSuite for a NetSuite Project Task, Issue or Support Case.
    cccc.png
  • Qualification criteria for NetSuite to JIRA - All NetSuite to JIRA data flows now support an option to define a qualification criteria. By using this feature you can define complex logic on which records should be picked up from NetSuite to be synced to JIRA. e.g. using the qualification criteria you can instruct the Connector to only consider NetSuite records for which a field has a particular value. The Qualification criteria option is really powerful and can be used to define multiple business rules
    dddd.png
    eeee.png

Release notes v2.1.0, July 2016

What’s new

Many customers use JIRA and NetSuite together to serve their customers better by managing support cases using JIRA and NetSuite. In this release of the Connector we have added support for NetSuite Cases and added few more settings which provide more control on the records which are synced between the two systems. The highlights of this release are:

  • NetSuite Case and JIRA Issues sync - These new data flows allow NetSuite Cases to be synced with JIRA Issues bi-directionally. Earlier a JIRA Issue could only be synced to a NetSuite Issue record, but now a JIRA Issue can also be synced to a NetSuite Case record.
  • Case messages and Issue comments - Along with syncing Issues and Cases, you can also choose to sync the comments and messages associated with them between systems. This will ensure that the latest updates are always present in both the systems.
  • NetSuite Customer names in JIRA - JIRA traditionally does not contain end customer information, however NetSuite Cases must be associated with a NetSuite Customer. We have introduced a new data flow which will sync Customer names from NetSuite to JIRA in a custom field in JIRA Issue form. While creating an Issue in JIRA, the Customer name from NetSuite can be selected. If this issue is synced to NetSuite as a Case, it will be created under the same NetSuite Customer.
  • Filter on Issue type - We have introduced a new setting which will allow you to choose which types of JIRA Issues should be synced to NetSuite. You can also describe which Issue type should be synced as a NetSuite Issue and which type should be synced as a NetSuite Case. for e.g. JIRA Issues of type “Tasks” and “Enhancements” can be synced as NetSuite Issue and JIRA Issues of type “Defects” can be synced as NetSuite Cases.

Release notes v2.0.0, May 2016

What’s new

JIRA is one of the most powerful and flexible Project Management tool available. 30,000 companies use JIRA everyday to manage their projects and teams. Today we are excited to introduce support for Project Management integration between JIRA and NetSuite in the JIRA - NetSuite Connector. This powerful integration helps you use the best features of both systems for managing projects. The main highlights are:

  • NetSuite Project to JIRA Project sync - This data flow enables you to create a NetSuite Projects automatically in JIRA. Advanced settings and mapping options allow you to define the various characteristics of the Project in JIRA, such as the Project Type.
  • NetSuite Project Tasks and JIRA Project Tasks - This bi-directional data flow allows you to sync tasks associated with synced projects between JIRA and NetSuite. You can also specify if a project task is a service item.
  • JIRA Time Tracking to NetSuite Time Tracking -  If a part of your team is working in JIRA and logging time there, now you can automatically sync JIRA Time tracking information to NetSuite. This time tracking information gets automatically associated with the NetSuite Project and the NetSuite Employee (if specified).
  • NetSuite Employee as JIRA User - If you want an employee in NetSuite to be available as a User in JIRA then use this flow to sync it automatically. You can specify which particular NetSuite Employee gets created in JIRA or you can choose to create all Project resources in NetSuite in JIRA.

Related articles

Comments

0 comments

Please sign in to leave a comment.