It will be fun but it's not done in a day. Activity Dashboard Alerts/Escalation Automated Routing Customer Database Customizable Branding Email Management Interaction Tracking Knowledge Base. Its the accelerated collaboration tool for. Or reach out to a solution partner and let them help you set everything up. Create, update, edit, plan, track, analyze all in the palm of your hand with the Jira mobile app by Atlassian. I would suggest starting with Jira for managing your team's work and then expand from there. Connecting Jira applications to a database Jira requires a relational database to store its issue data. So you have a steep learning curve ahead of you if you just came across the tools. For Marketing Jira is hooked up to a well-known email marketing solution. But that Jira is enriched with lots of custom fields and calculated/scripted fields for summing up values and displaying other needed data we defined at some point. Don't forget enhanced reporting and charts as well.Īnd our Jira Service Desk (a different instance in our case but it doesn't have to be that way) is used for support and can access that data as well to display license details and other useful information in requests. Which then contains "Transactions" as sub-tasks. We have an independent Jira instance serving as CRM (pulling data from the Atlassian Marketplace) and storing everything that is related to licenses, customers, etc in a "License" issue type. Collect additional data about customers and organizations right in your Jira Service Management Ask customers for data Manage customer data at your. Let me give you a (very, very) brief outline of how my team works with customer data and support. But you could create such an access level working with permissions. Jira Core does not offer the distinctive feature of "customers". On the other side are so-called Service Desk agents working on requests and other internal users (not agents) that can collaborate (for example comment) on requests. That is important for the way it works or how it provides your service of product support (or internal self-service for example).Ĭustomers get access to the help center (sum of all service portals) and service portals (one per project) to raise requests, access a connected knowledge base (Confluence) and so on. Jira Service Desk offers native support for a user type "customer". Let me take your example about Jira Service Desk and Core. The Qlik JIRA connector lets you fetch data from your JIRA projects and project issues and load it into your Qlik Sense or QlikView apps. And that's their biggest disadvantage, too. That's their advantage: They are pretty powerful. Hi George and welcome to the community! You're not barking up the wrong tree at all! What you're trying to achieve is perfectly possible with the tools, you just have to customize them according to your needs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |