We are using it for internal issues related to our ERP system. We are tracking these issues and, more importantly, linking them to development tasks. So, if we've written an extension and there is a bug, and somebody opens a help desk case with it, we can link it directly to a bug ticket in Jira. We then know when this bug is fixed. We are cloud-based, so we are always on the latest version.
We are using JIRA for accessing our help desk when other companies have problems with programs and to let them login when somebody needs to create a new ticket.
We're a service provider. We implement the solution for our clients. Typically clients use Jira more around incident reporting management and resolution of queries, or SLA management. Then, sometimes, they need a range of compliance SLS's such as knowledge management.
One of the main advantages of JIRA is that it can be customized for our solutions. I live in Iran and we translated some parts of it into Persian and customized it with extra features. We hid other features to customize it right to the point. We provide this solution for our customers. It helps us shape it for our project management workflow. We are a software development team, a software company. Internally, we also use Microsoft Team Foundation, or TFS, for our development team, while we use JIRA Service Desk for our contact points. We use JIRA for the CRM and Microsoft Team Foundation for internal use.
Quality Engineering Lead at a computer software company with 51-200 employees
Real User
2019-09-15T16:43:00Z
Sep 15, 2019
The primary use case for this solution is project management. The deployment model we used was cloud-based. Depending on the project your deployment model would be using a hybrid cloud or a private cloud.
JIRA Service Desk is used as a support solution with the support team to manage support service delivery to customers. I coached a big banking company using JIRA Service Desk to record customer incidents that require support. With the product, we have two different layers of incident management. Level one is for the call center and level two is for the agents who repair or try to resolve the incident using a software team. If their team can't resolve the problem, we create particular bug issues in JIRA software, and the development team creates a plan to correct the issue and confirms the experience in order to provide a resolution. The issue is returned back to layer two, and layer two discusses the problem with layer one. After that, layer one speaks to the customer and explains the status of the problem.
Technical Solutions Consultant at a tech services company with 51-200 employees
Consultant
2019-06-23T09:40:00Z
Jun 23, 2019
One of the primary things we use JIRA for is the Kanban Board feature. We use it for managing our projects and issues as well as accountabilities within the company. We have a homegrown — I suppose you could call it a Six Sigma type — approach. We identify the six main projects and the six areas where you can make the biggest difference within the company. Then we identify six projects that we're going to work on within those areas. We use the Kanban Board extensively. We use the Confluence facility on the backend. Really, we use Confluence and JIRA both together: Confluence for global planning and JIRA for issue and project management.
JIRA Service Management is Atlassian’s IT service management (ITSM) solution. It unlocks all teams at high velocity by:
1. Accelerating the flow of work between IT teams, development teams, and business teams
2. Empowering teams to deliver their service more quickly
3. Bringing visibility to their work
Built on JIRA, JIRA Service Management enables best practices across request, incident, problem, change, knowledge, asset, and configuration management so that teams can streamline...
We are using it for internal issues related to our ERP system. We are tracking these issues and, more importantly, linking them to development tasks. So, if we've written an extension and there is a bug, and somebody opens a help desk case with it, we can link it directly to a bug ticket in Jira. We then know when this bug is fixed. We are cloud-based, so we are always on the latest version.
I'm the vice president of digital strategy and executive delivery.
We are using JIRA for accessing our help desk when other companies have problems with programs and to let them login when somebody needs to create a new ticket.
We implemented workflows for incident management, interaction management, and problem management.
We are using Jira Service Desk for supporting both internal and external clients.
The primary use case is for support. I open, support, and service a request. There is also some follow up with the activities.
We're a service provider. We implement the solution for our clients. Typically clients use Jira more around incident reporting management and resolution of queries, or SLA management. Then, sometimes, they need a range of compliance SLS's such as knowledge management.
One of the main advantages of JIRA is that it can be customized for our solutions. I live in Iran and we translated some parts of it into Persian and customized it with extra features. We hid other features to customize it right to the point. We provide this solution for our customers. It helps us shape it for our project management workflow. We are a software development team, a software company. Internally, we also use Microsoft Team Foundation, or TFS, for our development team, while we use JIRA Service Desk for our contact points. We use JIRA for the CRM and Microsoft Team Foundation for internal use.
I'm primarily trying to use the solution as an IT Service Management solution.
The primary use case for this solution is project management. The deployment model we used was cloud-based. Depending on the project your deployment model would be using a hybrid cloud or a private cloud.
JIRA Service Desk is used as a support solution with the support team to manage support service delivery to customers. I coached a big banking company using JIRA Service Desk to record customer incidents that require support. With the product, we have two different layers of incident management. Level one is for the call center and level two is for the agents who repair or try to resolve the incident using a software team. If their team can't resolve the problem, we create particular bug issues in JIRA software, and the development team creates a plan to correct the issue and confirms the experience in order to provide a resolution. The issue is returned back to layer two, and layer two discusses the problem with layer one. After that, layer one speaks to the customer and explains the status of the problem.
The primary use case of this solution is for storing project data on the cloud. The deployment model we are using is on the cloud.
One of the primary things we use JIRA for is the Kanban Board feature. We use it for managing our projects and issues as well as accountabilities within the company. We have a homegrown — I suppose you could call it a Six Sigma type — approach. We identify the six main projects and the six areas where you can make the biggest difference within the company. Then we identify six projects that we're going to work on within those areas. We use the Kanban Board extensively. We use the Confluence facility on the backend. Really, we use Confluence and JIRA both together: Confluence for global planning and JIRA for issue and project management.