At the end of the day, performance defects are bugs – plain and simple. When new performance defects are introduced it’s important to log those bugs in a way that’s seamless with your current workflow for reporting and resolving other issues.

This is why we’re especially excited to share our latest addition to the Rigor Optimization product: a new JIRA integration!

If – like us – you use JIRA to track bugs and defects for your web application, now you can log performance defects directly from the Rigor Optimization product into your JIRA instance using our new native integration.

To get started, log into your Rigor Optimization account, then select Settings > Tools from your account menu in the top-right. Click Enable under the JIRA settings section and you’ll find a form to create the integration along with some text explaining How It Works.

Jira1

The Jira Base URL field is the root URL to your Jira installation. Usually this is something like https://(yourcompany).atlassian.net (if you use Atlassian’s cloud-based JIRA). If you’re not sure, copy paste the URL you use to log into JIRA and we’ll auto-detect your base URL from that.

In addition, specify a JIRA user and password that can be used by Rigor Optimization to log JIRA tickets. We recommend creating a new set of login credentials with minimal permissions – although it must have “create issue” permission to work with the integration! When you click ‘Save and Validate’, we will encrypt and securely test these credentials against your JIRA installation to make sure the connection is valid.

Once validated, you can directly log JIRA tickets for any performance defect you find from inside the Rigor Optimization application.

To get started, open any performance snapshot, click the Defects tab, then click into a performance defect of interest. Now click the Export button in the top-right corner, and you’ll see a new Create Jira Issue option.

Jira2

Select this, and you’ll see a rich modal display with the appropriate JIRA fields pre-filled with publicly accessible share links and verbose details about this performance defect.

Jira3

Customize the options as you see fit, then hit Create Issue to log the ticket in JIRA. You’ll immediately see a link to the newly created ticket which can easily be opened or copy-pasted to embed in the format of your choosing.

Jira4

That’s it! We hope you find this new integration with JIRA makes it even easier to log and resolve performance bugs detected by Rigor Optimization.

Suggested Blog Posts

The Perception Gap for Poor Web Performance

E-commerce revenue continues to grow,as consumers turn away from shopping in brick-and-mortar stores to shopping online.  However, many businesses are not prepared for this growth because they do not fully understand the market and how to invest in...

Read More

Using Browser Trends to Maintain a Better Site

Because of the multifarious nature of web clients today, it’s important to consider the usage statistics when designing, implementing, and managing your site. However, misconceptions often arise when determining what browsers to design...

Read More

Finding Causes of Intermittent Errors from Google Webmaster Tools

Google Webmaster Tools is a web service that allows webmasters to view the status of their sites as seen by Google and the Googlebot crawlers. In addition to indexing your site structure and content, the Googlebot crawlers also record data on perform...

Read More

Optimization Options not Always Optimal

Web designers and developers are always looking for ways to speed up their page load times. Yahoo has an excellent article written on the best practices for speeding up your page. How do you know if implementing one of their suggested practices will...

Read More