Portfolio for JIRA (Server)

Aggregate financials, project

Hippobyte makes it easy to replicate your Portfolio for JIRA data to one of many supported databases to centralize your organization’s data for deeper insights.

Getting Started

Hippobyte connects to Jira Server utilizing Jira’s Application Link and OAuth. To connect Hippobyte Jira for Portfolio Connector to Jira Server, the following is required:

• a Jira Application Link must be configured by a Jira user with administrative privilages
• a Jira username and password with sufficient API read privilages to Portfolio for Jira and Jira Issues

Gather required information

As part of creating an Application Link you will need a consumer key, and a public key. Both the consumer and public key can be found within the Hippobyte console by navigating to the Jira for Portfolio (Server) connector from the Connect Catalog.

1. Consumer Key
   asd
2. Public Key
   asdasd
3. Username
4. Password

Configure a JIRA Application Link

Aa a Jira Administrator user:

1. From the Administrative menu, navigate to the Applications section
2. Under the Integrations section in the left menu, click on Application Links
3. Enter https://www.hippobyte.com in the URL input field and click the Create new link
4. Acknowledge the ‘No response was received from the URL’ by clicking the Continue button (do not add or update the URL, it is not needed)
5. Enter Hippobyte in the Aplication Name field
6. Select Generic Application in the Application Type field (or leave it as default)
7. Check the Create incoming link box, then click Continue

Refer to Gather required information section above.

1. Enter the consumer key in the Consumer Key fild
2. Enter Hippobyte in the Consumer Name field
3. Enter the publick key in the Publick Key field, then click Continue

Security

TLS

All connections between your Clarity PPM instance and the Hippobyte platform are secured utilizing Transport Layer Security (TLS), a cryptographic protocol designed to provide security over a computer network.

Credentials

Hippobyte has minimum requirements for passwords utilized with our platform. The Clarity PPM password must be at least eight (8) characters long, and cannot contain commonly used words, admin, xog_admin, password, niku2000, etc.

Best Practices

FAQs

Which versions of Clarity PPM are currently supported?

All Hippobyte features are supported for Clarity PPM versions 14.2 and up. Some features may incompatible with previous versions, please reach out with your specific version for additional detail.

How does Hippobyte extract data from my instance?

To provide you unfettered access to all data stored within your Clairty PPM isntance, We utilize standard APIs offered by Clairty PPM, specifically the XOG protocol.

Can XOG handle extraction of all data within my Clarity PPM instance?

Yes! The XOG protocol is capable of extracting any data within your Clarity PPM instance. While XOG has throughput restrictions, Hippobyte architecture overcomes most of these limitations.

How do I ensure deleted object instances do not show in my data?

While Clarity PPM does not offer a mechanism to identify all deleted data, it does offer the ability to audit most objects. Hippobyte is capable of reading deleted isntances from the audit object to allow you to identify deleted instances.

Is Hippobyte used by companies with large Clarity PPM deployments?

Yes! Hippobyte is currently utilized in production environments within retail, finance, and utility companies to synchronize millions of data events every day.

Troubleshooting

Connectivity Issues

The user associated with the Hippobyte platform must have XOG Admin rights. In addition, the Clarity PPM instance must be accessible to the cloud-based Hippobyte platform.

Timeouts

To prevent from opening uneccessary connections, Hippobyte terminates connections which run longer than 30 seconds. See best practices above.