Bundling use case #1 – Power Scripts™ and Power Custom Fields™ 

Turn Jira into a CRM or inventory tracker

Bundling Power Scripts™ for Jira and Power Custom Fields™ enables users to use Jira to store and retrieve information, turning Jira into something like a quasi CRM or inventory tracker. Using Jira to to collect data in a central place means small businesses or agile teams don’t need to buy another system or database to house this data, allowing you to use what you already have to its full potential.


Use Power Custom Fields™ to retrieve data from issues in Jira

For example, using Power Custom Fields™, you can retrieve data from an external database or store information in Jira issues and use Jira as a database. Imagine if you were running an online store. You could create a hidden project in Jira and create Jira issues which contain data for each product that you sell. Imagine there is another project in Jira for sales of your product and you want to get a list of all the products that you are selling. You can use Power Custom Fields™ to create that list of products off the hidden project, because Power Custom Fields™ is grabbing data from the issues in Jira.


Use Power Scripts™ for Jira to add/ update information in the projects

Using Power Scripts™ for Jira, if you sold a product, you could keep track of inventory, or if it’s a new product or customer information, Power Scripts™ for Jira could automatically create the issue (containing data such as product ID, description, shipping weight, inventory account) in the hidden project. You can use Power Scripts as needed to add/ update information in this project.

Alternatively, if you were storing customer information in Jira tickets, you could use Power Scripts™ to automatically link tickets together based on the customer activity, to see a history of the customer’s transactions.

 


Bundling use case #2 – Power Scripts™ for Jira and Power Database Fields PRO™ using Jira like an ERP/inventory management system


Use Jira to create a workflow to keep business processes on track

Bundling Power Scripts™ for Jira and Power Database Fields PRO™ you are able to use Jira like an inventory management system, connecting it to a third party database. Using Jira, you can create the workflow that manages the business process of completing the sale and tracking the fulfillment to get the job done. Setting up a workflow in Jira ensures that all the steps are completed in the correct order before moving on to the next step.


Use Power Database Fields PRO™ to display data from external databases in Jira

Power Database Fields PRO™ can then be used to pull and display data coming from all the third party databases such as the purchase order, the sales order history, the inventory details etc. The benefit of bundling with Power Database Fields PRO™ is that Power Database Fields PRO™ 1) has the ability to pull new data every time so you know it’s the most current data and 2) it easily displays a lot of data in Jira tickets in the table grid format. Without Power Database Fields PRO™, it would be difficult to display so much information in a single ticket.

Using Power Database Fields PRO™, you could pull the sales order history and populate this information in Jira. Using Power Scripts™ if you completed a sale, you could update the inventory in the external system or create a purchase order. Thus, Jira becomes to central tool to integrate with all the external systems to keep processes on track and information up to date.


Power Scripts™ can help set triggers for low inventory warnings

In addition to this, you could use trigger features of Power Scripts™ to send inventory warnings. Simply include the ‘minimum inventory quantity’ as information on a Jira ticket, you can then query data based on this and find any stock that has gone below the minimum inventory will then trigger Jira to send an email notification to recipients of your choice.

 

Bundling use case #3  Issue History Collector and Surveys for Jira – ultimate tools to monitor teams and improve customer service


Use Issue History Collector to track the progress your teams are making on open issues

Combining the forces of both Issue History Collector and Surveys for Jira is a great way to actively measure your support team’s processes, identify any improvements and also target the relevant customers who will give the relevant feedback needed to improve. Using Issue History Collector, you can easily see vital stats like the assignee, the amount of time a ticket spent in each status and the total time spent on each issue.


Surveys for Jira offers custom surveys to give granular insights once an issue is resolved

After an issue has been resolved by your support teams, you can then use Surveys for Jira to deliver a survey to  your customer to gain actionable insights about what they liked, and what they thought could have been improved. Surveys for Jira offers a whole host of custom survey questions over and above native Jira Service Desk functionality. You can even add custom fields from Issue History Collector into Surveys for Jira for more granular questions.


Get the full spectrum of feedback by bundling Issue History Collector and Surveys for Jira to target the right customers

Best of all, using both of these apps in conjunction, you will be able to target certain groups to get feedback on the best customer experiences (by targeting customers whose tickets were resolved in record time using Issue History Collector stats) and the worst customer experiences (by targeting customers whose tickets had lengthy time in each status or exceeded SLA using Issue History Collector stats) to get the full spectrum of what your teams are doing well and what they should continue, and to pinpoint which areas they need to improve on.

 

Please email us at products@cprime.com with the subject line of the apps you’d like to bundle.



Tagged with: , , , , , , , , , , , , , , ,

Categorized in: , , , , , , ,