Role Based Jira, Jira Service Desk, and Confluence Training Strategy

When considering your Atlassian product training strategy, select content that’s specific to each user’s role and delivered in manageable pieces. Different types of users need different information, different levels of detail, and need it delivered at different times. It’s tempting to gather everyone in a big room for a marathon training class. But it’s much smarter to offer role-specific information in small, digestible, and progressive pieces.

Progressive, Role-based Training

Intro to Jira Cloud Agenda

In the beginning, a brand new user just needs to know the basics.  Answer questions like:  “What is this application?”, “How do I use it?”, and “How do I access it?” Take a look at the agenda in our 30 minute “Intro to Jira Cloud” online course, for example. It’s short and specifically designed not to overwhelm new users. The goal is to get them feeling comfortable in the application immediately. Consider that some employees may have used Atlassian applications before. Their previous experience, version, use, and expectations could differ from what’s expected in your organization.

As part of initial training, give new users a simple homework assignment. Here’s an example: (1) to log into the application, (2) bookmark it in the browser, and (3) create a Jira issue, a Confluence page, or a Jira Service Desk request. You can test whether their creation meets the needs of the organization. This is a great time to catch problems before they turn into bad habits. Look for future trouble like missing an important issue field, creating a page in the wrong global space, or providing vague request details.

Once the user understands the basics start adding additional content. Select new content based on user role, how they’ll use the software, and skills they’ll need to do their regular job. Time the content delivery so they can learn little by little without impacting their other work.

User Types and Roles

Here are some additional user types and content recommendations:

  • The regular or occasional user needs info about sharing and organizing their data, creating filter subscriptions, linking, and logging time.
  • The power user wants information about basic & advanced search, JQL, and bulk changes.
  • Team leads, project managers, and scrum masters want to know about views like dashboards, boards, and reports.
  • Service Desk Agents want to understand service level agreements (SLAs) and how to use JSD features to support their customers.
  • Application admins want information about configuration, performance, effective workflows, best practices, mistakes, and certification.

Delivering information progressively, and based on roles, lets you quickly and effectively train users. They can put the info into practice immediately and won’t forget everything they learned by the end of the day.

Let Us Handle Your Training

We know admins don’t always have the time or expertise to train users. We do and we’re good at it. Let us deliver your company-wide training though our efficient, 30-minute, online, skill or topic-based courses.

Please complete the form, or share it with your training coordinator, so we can recommend courses, presentations, and materials.

How can we help with your training needs?

Training Your Jira, Jira Service Desk & Confluence Users

The job of an Atlassian administrator is never done. Your list of responsibilities is endless. You’re making sure your applications are up and running so work can get done. You’re weighing the benefits and long-term impacts of customization and add-on requests. You’re assisting users with access, permissions, and restrictions. You’re helping teams get the most out of the applications. And some of you are doing all of this while performing other tasks or managing other software. With all the demands on an Atlassian administrator, where does user training fall on your to do list? If you’re like most admins, it’s probably at the very bottom.

Continue reading “Training Your Jira, Jira Service Desk & Confluence Users”

Atlassian Customer ShipIT Creates Dynamic Jira Map

Each quarter, Atlassian has a 24 hour hackathon, called ShipIt, where they stop all work duties to create something awesome.  It embodies their culture of innovation and demonstrates a sacred company value: “Be the change you seek.”

This week, 24 non-Atlassians participated in the first Atlassian User Group (AUG) Leader ShipIt.  Since we’re Atlassian customers, volunteers, and have work duties we can’t ignore, our hackathon lasted 3 weeks, instead of 24 hours.  We worked nights and weekends to bring our ideas to life and then submitted our finished products as a three minute video.

Project Planning at Atlassian Summit

We were one of 10 teams that accepted the ShipIt challenge.  Our team included six AUG Leaders from all over the country.  We named ourselves “Atlas”.  We wanted to solve a visibility issue that impacts the AUG program and we wanted to use Atlassian products to do it.

Problem Statement

As an Atlassian User Group Member, an AUG Leader, or member of the Atlassian Community Team, I’d like to:

  • See a visual representation of the active AUG locations around the world
  • Find the user groups near my location
  • View each group’s size, contact details, and the website URL
  • Encourage traveling users to connect with additional groups
  • Create a dynamic solution which will never be out of date or require manual maintenance
  • Encourage new membership by showing existing user groups
  • Encourage new group formation by showing location gaps
  • Use Atlassian tools to store the data and collaborate during the project

Our Solution

Jira Custom Fields

We built a dynamic map that pulls its data from Jira issues!  We started with a Jira project, where each user group is represented by an issue.  The project has custom fields, like “Map Location” and “Group Size”, to hold information about each group.  The project has custom workflow statuses, like “Active” and “Inactive”, to show the current state of each group.

We used Jira’s REST API to retrieve issue data for only user groups in certain statuses.  Next, we injected the JSON results into SQL 2016.  We then restructured the data for map use.  For example, we translated the plain text “Map Location” values into coordinates the Google Maps API would understand.  Finally, we created a script that automates the REST API calls and the Geocoding of the locations.  The script also generates an HTML file with all the user group data plotted.  The process of updating the HTML file on the server is automated too.  The file is uploaded to our Confluence instance and versioned through the REST API.  It is also published to an external website, demonstrating additional viewing abilities.

When a user group transitions to another status, or if any Jira issue data is updated, those changes are automatically reflected on the map!  This includes changes to the group’s name, estimated user counts, and group contact information.  The map requires no manual updates, which was a project goal.

Clicking a map pin displays city information, like the group size, the city contact email address, and a link to the group’s website.  The map also automatically centers to your current location and counts the total number of active user groups displayed.  The look and feel is fully customizable and results can be embedded on other websites, including Confluence and Jira.

Additionally, we used HipChat’s Botler service to create map entry point.  In HipChat, if an AUG Leader types “an AUG in” as in “Is there an AUG in Nebraska?” a link to the map will automatically appear.  See our creation in action with the three minute ShipIt video below.

You can also demo our proof of concept live!

Atlassian Products Used

We started collaborating in person at the Atlassian Summit user conference and used Atlassian tools to stay connected after returning home.  We used:

  • Trello to collect user stories, feature requests, and track progress,
  • Confluence to make decisions and document solution details,
  • HipChat for daily discussions and immediate feedback,
  • and Jira to store all user group location and status data.

Our Team

We’re very proud of what we built and had an awesome first Atlassian ShipIT experience!

  • Mark Livingstone, IT Director at Qualcomm and San Diego, CA AUG Leader
  • Marlon Palha, Head of Business Systems at ITHAKA and New York City AUG Leader
  • Stephen Sifers, Network Operations Center Manager at Sagiss and Dallas, TX AUG Leader
  • Jeff Tillett, Agile IT Operations Manager at AppDynamics and Dallas, TX AUG Leader
  • Justin Witz, Chief Technology Officer at FRA PlanTools LLC and Charlotte, NC AUG Leader
  • Rachel Wright, Author of the Jira Strategy Admin Workbook and member of the AUG Leader Council.
    Your Cart
    Your cart is empty. Go add some materials!Return to Shop