Export topics to your JIRA instance and automatically push comments back to the community.
This integration allows community managers to export community topics to their JIRA instance where product and development teams can investigate and evaluate. All replies to community issues within the JIRA interface are automatically posted to the topic page, along with the status of the issue. Topic statuses in Get Satisfaction are automatically updated when JIRA issues are resolved, so customers know their feedback has been addressed without adding extra work for your team.
In order to integrate your Get Satisfaction and JIRA instances, you’ll need the following:
- A paid Get Satisfaction community
- An on demand or on premise JIRA instance
- Admin access to both your Get Satisfaction community and JIRA instance
To set up this integration you’ll need to configure from both the Get Satisfaction community and JIRA instance. There are quite a few steps to fully setting up the integration, so please read through this set-up guide carefully.
Part 1: Configuring Get Satisfaction
- Log into your Get Satisfaction community
- Click “Admin” from the grey community tools bar
- Click “Integrations” on the left hand side of the page
- Click on the JIRA icon and fill out the credentials for your JIRA instance
Note: Make sure the JIRA user you assign for the Get Satisfaction integration has appropriate permissions to create issues in JIRA. Before you enter the user here, log into JIRA with this user and try to create an issue in the appropriate JIRA product to confirm the user can create new issues. Use the correct JIRA username (not your email address).
Part 2: Configuring JIRA
Once you’ve configured the integration on the Get Satisfaction side, log into JIRA to finish the set up process.
- Log in to JIRA as an administrator
- Create a JIRA project for your Get Satisfaction community if you have not already done so
- Navigate to the gear drop down in the upper menu bar and choose the “Add-Ons” menu option
- Choose “Connections” from the left hand side of the add-ons page
- Under “Cloud Connections” choose the Get Satisfaction cloud connector and name the new connection. Click through to the next page
- Click “Manage Application Links” and fill in the details around this application. Replace “/getsatjira” with your community’s domain for both the RPC and display URLs. Then click “Add”
- Once you’ve added the appropriate application link details, click “Configure Authentication”
- Complete the authentication form with your Get Satisfaction credentials Keep Going! Once you’ve completed the authentication form go back to the Connections page (step 4), and continue:
- On the Connections page, enter the name of your connection and connection type
- Choose the application link that you built in the Manage Application Links step (step 6), and click “Add”
- On the next page, click the Launch Wizard button
- Associate the Topic object (drop-down) with the JIRA project that you want to associate to your Get Satisfaction community. Click “Yes” to automatically associate fields, and then click “Create Configurations”
- Once you’ve completed the Default Configuration Setup, click the “Click Here” link to the Mappings section
- Click on the “Field Mapping” page, and add the following 2 options
- Once both mappings have been added, click on “Map Values” for the Status Field
- Add the following status mappings:
- Go back to the connections page and click “Product and Style Mappings”
- Add a mapping between the Get Satisfaction Product and JIRA Project. Then click “Add”
- Add a mapping between the Get Satisfaction Style and JIRA Issue Typ. Then click “Add”
- Click on “Mapping Schemes,” in the configuration under Cloud Connectors
- Configure the existing Schema
- Make sure all unassigned issue types are associated with the topic mappings you created above
- Go to your project page in JIRA
- Click on Administration , then Project Mappings
- Select your Get Satisfaction mapping from the dropdown, and then click “Associate”
Once both the Get Satisfaction and JIRA sides of the integration have been properly configured, you’ll be able to export topics from your community into JIRA simply by clicking the “Export” link that now appears on the community topic. In order to export topics, the community employee must have a Management Seat enabled for their account.
Successful exports will have a “Success!” message appear at the top of the topic page
Please ensure that your entire development team is aware that all comments added to the imported JIRA issue will automatically be pushed back to the public community topic. However, new replies posted to the community topic will not push into to JIRA once the topic has been exported. Topic statuses in the community will update when the JIRA issues are marked as resolved.
If you try to configure your integration and encounter one of the following errors, try the troubleshooting tips provided.
1. Robot Error: Petite Vermillion Kangaroo Suspects
If you encounter a server error with the code: “petite vermillion kangaroo suspects” it’s likely due to an HTTP / HTTPS conflict. Make sure you use HTTPS when configuring the integration on the Get Satisfaction side.
2. Robot Error: 50x!!
The 50x!! server error could mean one of two things.
1. The username entered in the Get Satisfaction side authentication is wrong
2. The connection to JIRA hasn’t been added properly (see steps 3-10 under JIRA configuration)
3. Robot Error: Venerable Jade Egret Communes
If you encounter a server error with the code: “venerable jade egret communes” it’s likely that the password you entered during the Get Satisfaction side configuration is wrong.
4. Robot Error: Cerebral Purple Urchin Kibitzing
The robot error: “Cerebral Purple Urchin Kibitzing” is the general error for a bad configuration in JIRA.
The most common error for this is caused by a misconfiguration in the mappings you configured in your JIRA instance. To avoid this error, go to JIRA and click on Add-ons from the tools drop-down menu. Then click Connections, and then Product Style and Mappings
Ensure both of your mappings have been set appropriately. If you’re unsure if your mappings have been set appropriately, or are just generally stuck, the easiest thing to do is to delete all mappings, application links, and add-ons, and start over.
5. Google Apps Sign In
The current version of the Get Satisfaction and JIRA integration does not support Google logins. To get around this issue, create a new JIRA user with a full email address. Make sure this user has full JIRA issue creation permissions. Use this user when you authenticate in the Get Satisfaction configuration steps.