Archives for the tag: JIRA

We're creating documentation spaces for each of our Atlassian Cloud apps to make it easier for you to find the product documentation you need. After all, if you only use Confluence Cloud, we don't want you to have to wade through a lot of JIRA docs to find what you're looking for. The Atlassian Cloud space still exists, but will be focused on helping Atlassian Cloud site admins with admin, billing, and user-management tasks that fall outside of specific applications. JIRA Cloud, JIRA Service

Continue reading »

Like hoodies and startups, peanut butter and jelly, cats and laptops, sriracha and everything, software development and IT support are better together. Incidents, feature requests, and bugs in the form of support tickets often need to be escalated to development. When developers prefer working in JIRA, and IT teams are in other systems, linking support tickets is often a broken process. The options are double handling with third-party apps, manual entry, and clunky integrations, which often leads

Continue reading »

This is a guest blog post from Lars Broden of LB Consulting Group the maker of Bulk Clone Professional. JIRA is a tool that enables development teams to plan and build amazing projects. When I began to use JIRA in my everyday work, one of the features I used frequently was the cloning function. I quickly realized I would be able to save a lot of time if I had the ability to clone multiple issues in one go.

Continue reading »

In JIRA Service Desk 2.4, we've built an intelligent engine under the hood that automates common tasks and knows the next step so you don't have to. This update includes: Automation: With a simple, intuitive UI, the automation engine performs actions based on specific events and conditions defined by you. Create action-based rules to do things such as update your customers and notify your team about issues that are about to breach SLA. Live queues: An improved way for your agents to keep

Continue reading »

First, it's important to remember that change is an evolution. It doesn't just happen overnight. Having realistic goals means it will be more exciting once your team hits them out of the park. After JIRA Service Desk is set up, customers can contact support by either emailing requests (which then become tickets) or through the customer portal. Ideally, all customers would use the customer portal so the right information is given from the start and so their requests can be categorized easily.

Continue reading »

We often collect feedback and requests from people outside of our team. If they find a bug, need something done, or have a feature request – somehow and some way, they need to reach us. As an Atlassian, I prefer working in JIRA. It’s my favorite place to plan, track, and get things done, however, I find that sending colleagues (who are often non-technical) to JIRA introduces them to an unfamiliar interface they don’t necessarily know how to navigate.

Continue reading »