This resource is for you if you've read Atlassian's documentation but are still confused on how to import linked issues.

Our partners at Puppet and Splunk recently released the State of DevOps Report 2018 which mirrors many of the same observations that we see when working with our customers. DevOps isn't a sprint, it's a journey, depending on the organization's size, that can take organizations months or years to master. Instead of focusing on statistics like in prior years, this year's report introduces the five stages of a successful DevOps evolution and identifies and describes the practices successful, mature organizations have implemented during their journeys. The report has something to offer to organizations no matter where they are in their process. Even if your organization has employed DevOps for some time, you may be missing a critical component of your implementation.

As with life, the only constant in DevOps is change. To position your teams to seamlessly flow with the changes and to empower them to innovate, some of the old ideas on Operations and Development practices must be left behind. An integral component of DevOps is culture. An iterative approach to a collective ownership should be taken when planning your move toward a DevOps environment. You can start your DevOps journey by advocating for the adoption of a consolidation of tools designed specifically for DevOps, which provides an environment of transparency and ease of use.

Leveraging Atlassian's dashboards and gadgets can provide teams within an organization the visibility and transparency into their work they may be lacking. The use of these tools gives greater insight into work in progress and completed work for individual teams or team members as well as providing top-level views of all the work across teams. Dashboards can be configured in many ways and be custom tailored to surface whatever information is desired. Dashboards are made up of gadgets as they are the driving force behind the data. These gadgets are embedded into the Dashboards and the information within them is determined by the JQL in the filters.

In an age where there’s a tool for every toil, we’re fortunate at Praecipio Consulting to be able to work with the best tools available. As an Executive Assistant who survives on staying organized, ahead of the game, and juggling with an exceptional attitude is just part of the day-to-day. If you hear “How do you do it?” you are not alone. How do I do it? The right tools.

One of the most powerful integrations in the Atlassian ecosystem is the native link between Jira and Confluence. For users working in both tools, the transition can be seamless if you do it right, but clunky if you don't. 

Now, what if I told you there was just one Confluence macro you could start using today that will immediately make reporting in Confluence easier and help you (and your team) keep track of your work? The Jira Issues macro is the go-to when reporting in Confluence.

Here are some tips to get your team to live their Atlassian life-to-the-fullest.

While service desk agents do everything they can to avoid firefighting, they are often focused on extinguishing one fire and moving to the next. This usually causes tickets to smolder in some status of "not quite done" until months later when they will finally be closed out (thanks bulk edit!). The good news: there is a way to keep things moving using out-of-the-box functionality. No longer will your metrics be inaccurate because people aren't "moving their tickets through the system." Jira Service Desk can help do the moving for you with automation.