Learning Hub

Use these instructions to export recommendations from the Recommendations tab and import them into a Jira project.

Prepping Your Hubbl File

Navigate to an advanced scan and click the Export to CSV button
Unzip your export and open the issues CSV in your favourite spreadsheet tool (Excel or Google Sheets)
Remove the following columns
- id
- scanScoreId
- itemId
- value
- recommendationId
- isBasic
- wellArchitectedTopicId
- wellArchitectedTopicLevel4URL
- createdAt
- updatedAt
You can optionally remove the following columns if you do not want to include the Well Architected topics, metadata categories, or namespace in your Jira stories:
- wellArchitectedCategoryLevel1
- wellArchitectedCategoryLevel2
- wellArchitectedCategoryLevel3
- wellArchitectedCategoryLevel4
- recommendationCategory
- namespace
Export the updated sheet as a CSV

Creating Jira Stories

Log in to Jira as a user with the Jira administrators global permission
Navigate to the Gear Icon (top right) > System > Import & export > External System import
Select CSV to open the CSV file import page
Select your recently created CSV document
Leave the Use an existing configuration file checkbox unchecked and select Next
Choose the project you would like to import into, and select Next (if you do want to import to multiple then follow the directions here)
In the Setup field mappings page, map the fields in the CSV file to the issue fields in the selected project. In the Jira field column, select the Jira field that you want to map to the field from the CSV file. We recommend the following but every Jira project is unique:
- apiName → Description
- Label → Description
- recommendationContent → Description
- recommendationEffort → Story Points (or related Effort field)
  - For this field select Map field value
- recommendationPriority →
  - For this field select Map field value
- recommendationTitle → Description
- relatedObject → Description
- rule → Summary
On the Setup value mappings page, specify the Jira field values for each CSV file field value that has been detected by the CSV file import wizard. If you do not want to change any values then leave this as is.
- recommendationEffort
  - 1 is high and 3 is low, map to your relevant values
- recommendationPriority
  - 1 is high and 3 is low, map to your relevant values
Select the Begin Import button when you are ready to begin importing your Hubbl Recommendation data into Jira. You will be able to see your progress and receive a success message once it completes.

🚀 Hubbl Diagnostics Tip: for additional details on importing Jira issues check out their documentation.

Use these instructions to export recommendations from the Recommendations tab and import them into a Jira project.

Prepping Your Hubbl File

Navigate to an advanced scan and click the Export to CSV button
Unzip your export and open the issues CSV in your favourite spreadsheet tool (Excel or Google Sheets)
Remove the following columns
- id
- scanScoreId
- itemId
- value
- recommendationId
- isBasic
- wellArchitectedTopicId
- wellArchitectedTopicLevel4URL
- createdAt
- updatedAt
You can optionally remove the following columns if you do not want to include the Well Architected topics, metadata categories, or namespace in your Jira stories:
- wellArchitectedCategoryLevel1
- wellArchitectedCategoryLevel2
- wellArchitectedCategoryLevel3
- wellArchitectedCategoryLevel4
- recommendationCategory
- namespace
Export the updated sheet as a CSV

Creating Jira Stories

Log in to Jira as a user with the Jira administrators global permission
Navigate to the Gear Icon (top right) > System > Import & export > External System import
Select CSV to open the CSV file import page
Select your recently created CSV document
Leave the Use an existing configuration file checkbox unchecked and select Next
Choose the project you would like to import into, and select Next (if you do want to import to multiple then follow the directions here)
In the Setup field mappings page, map the fields in the CSV file to the issue fields in the selected project. In the Jira field column, select the Jira field that you want to map to the field from the CSV file. We recommend the following but every Jira project is unique:
- apiName → Description
- Label → Description
- recommendationContent → Description
- recommendationEffort → Story Points (or related Effort field)
  - For this field select Map field value
- recommendationPriority →
  - For this field select Map field value
- recommendationTitle → Description
- relatedObject → Description
- rule → Summary
On the Setup value mappings page, specify the Jira field values for each CSV file field value that has been detected by the CSV file import wizard. If you do not want to change any values then leave this as is.
- recommendationEffort
  - 1 is high and 3 is low, map to your relevant values
- recommendationPriority
  - 1 is high and 3 is low, map to your relevant values
Select the Begin Import button when you are ready to begin importing your Hubbl Recommendation data into Jira. You will be able to see your progress and receive a success message once it completes.

🚀 Hubbl Diagnostics Tip: for additional details on importing Jira issues check out their documentation.

FAQs

Can't find what you're looking for?

FAQs

Can I view a scan that someone else has run using Hubbl Diagnostics? Can the results be shared?

How can I add users to my Hubbl Diagnostics account?

How can I import Recommendations as Jira Issues?

How do I see the amount of licenses I’ve used?

How many API calls does Hubbl consume?

On scan results, what makes "risky permissions" risky?

What access does Hubbl Diagnostics need to run?

What are Hubbl Diagnostics' trusted IP addresses?

What does Hubbl Diagnostics analyze?

What happens if I choose not to renew my subscription?

What permissions does my Salesforce user need to run Hubbl Diagnostics scans?

What type of API calls does Hubbl make on my org when performing a scan?

Why am I seeing a Tableau login screen on my scan?

Why does "Standard Object X" not show up in the Field Utilization dashboard?

Why is Field Utilization missing for some fields?

What data inputs does it need?

What can process mining do that Business Intelligence does not?

What are the outputs?