Jira Integration for Rightsizing enables organizations to integrate with Jira to get resource optimizations into the hands of those who can evaluate and act upon these recommendations. This release features the bi-directional synchronization of Jira ticket status, automated issue or request creation via Policies, Rightsizing ROI reporting, and support for Jira Cloud and the Jira Service Manager extension.
- Pre-requisite: complete steps for Jira Integration - Setup
- Step 1: Configure Policies to enable automatic creation of tickets for high-value resource optimizations
- Step 2: Triage Issues (or Requests) as tickets are created
- Step 3: Review Rightsizing ROI
- Best Practices
After enabling Jira Integration, navigate to Optimize > Rightsizing ROI. Ensure that the Policies button is enabled; if not, review the Jira Integration - Setup steps.
Figure 1- Initial Rightsizing ROI screen
To define a policy, click the Policies button. You will be taken to the Configure Policy screen. This is where you specify the filter criteria, Jira mapping, and schedule frequency.
Figure 2- Policy Configuration Screen
On this screen, please provide the following:
- 30 Day Savings Threshold - the minimum Cost Savings amount to be considered, based on a thirty-day timeline.
- Services - which rightsizing recommendations to include.
- Cost Basis - the cost basis for using when calculating the threshold.
- Actions - which rightsizing actions to include.
- Account - to filter resources to this account
- Maximum Results - the maximum number of tickets to create for each run, ranked by descending cost savings amount.
- Jira Mapping - Project - target Jira Project
- Issue | Request Type - issue type for Jira Software or request type for Jira Service Manager.
- Recurrence - select either Daily or Weekly
- Days of Week - if this policy will run weekly, specify the day of the week on which to run.
- End By - specify an ending date for this policy
Triage Issues (or Requests)
Based on the policy defined above, based on the frequency, issues (or requests) are created in the appropriate Jira project, where the organization will integrate into their existing workflows. Once the issues have been reviewed and actioned upon, the resulting status will be captured. When the resource change has been implemented and detected on the backend, the realized cost savings will be calculated and presented on the ROI reporting screen.
Once the policy has been executed based on the schedule you specified, you will see the resulting list of issues or requests in your designated project:
Figure 3 - Jira Service Manager requests
Each ticket contains a summary of the recommendation, a link to the Cloudability details page, and labels from key resource attributes, as shown below:
Figure 4 - Example Ticket
Once the policy is run, you will see the resulting list of tickets and linked resources on the Rightsizing ROI screen:
Figure 5 - Rightsizing ROI screen
The Rightsizing ROI screen provides the following summary information.
- Potential Savings - the potential cost savings opportunities from all unresolved tickets
- Realized Savings - the realized cost savings projects for the next 30 days for all resolved tickets.
Also, details are displayed for each linked ticket:
- Cloud Service - the cloud provider and cloud service
- Resource Name - the name of cloud resource
- Ticket - the ticket associated with this resource
- Ticket Status - the current status of the ticket
- Assigned To - the ticket owner
- Created - the date the ticket was created
- Closed - the date the ticket was resolved; otherwise, "N/A" if it is still active.
- Resolution - the resolution status if the ticket is closed
- Potential Savings - the potential savings identified by the recommendation
- Realized Savings - the realized savings based on the new instance type
- Review the Rightsizing recommendations for each service, being sure to select the 30-day view. From here, look at the Cost Savings opportunities to get insights into establishing the threshold amount.