2 min read

Should my Jira Service Management instance be separate from Jira Software?

By Morgan Folsom on Jan 29, 2021 2:04:24 PM

Blogpost-display-image_Should my Jira Service Desk instance be separate from Jira Software-As companies grow either organically or inorganically, many are faced with the decision of whether they should consolidate or keep their Jira instances separate. Today I'm going to address one specific flavor of this conundrum that I am often asked about, specifically with regards to separate instances of Jira Software and Jira Service Management. Some organizations choose to have separate instances for Jira Service Management and Jira Software, but I am here to tell you that is probably not necessary!

Although Jira Software and Jira Service Management are different products, there is no need to keep them separate. The most efficient companies use both in a single instance, so that teams can collaborate much more easily. As organizations adopt DevOps or start to think about it, one of the first things that is looked at is how IT interacts with the development organization. If these two groups are working in separate Jira instances, collaboration and clear understanding of ownership and handoffs is much more difficult. For example, It is much easier to link an incident that was submitted to the service desk to an associated bug if all of those tickets live in the same instance. While you can link to tickets in other instances, that requires users be licensed in both and have a clear understanding of where the work lives. Working in a single instance removes the need for potential duplicate licenses and ensures teams can communicate clearly. 

Occasionally teams use separate instances due to security considerations. However, in almost all situations your security concerns can be addressed by project permissions, application access, and issue security. There are few cases that Jira's native security features won't account for. 

Finally, let's look at this from a user experience perspective. One of the most prominent complaints that we see as organizations undertake their digital transformations are that users have to keep track of too many tools, a pain that I've felt in my career as well. Trying to remember where to log in for a specific subset of your work can be a headache. If your Jira Service Management and Jira Software instances are separate, they'll have two separate URLs that users have to navigate to. Signing into multiple locations and using different URLs adds an extra step where there need not be one.

Since you've already made the great decision to use both Jira Software and Jira Service Management, you might as well reap the benefits of the easy connection between the two so your teams can focus on what matters, rather than managing their tools. 

Are you looking to merge your Jira instances? Contact us, we know all about how to do that, and would love to help.

Topics: jira atlassian blog optimization tips integration project-management jira-core merge jira-service-management
2 min read

How Confluence and Jira Work Together to Make Your Life Easier

By Cindy Smith on Sep 10, 2019 11:46:00 AM

An essential part of a successful organization is communication: open and direct lines of communication ensure that team members react swiftly and effectively. In regards to software and applications, different teams have different needs and collaborating can sometimes feel like speaking in different languages. The reality is, development teams live in one application and business teams live in another.  

The good news is, it’s ok. Your teams can live in different applications. 

How Does Jira Integrate with Confluence?

Atlassian Confluence and Jira integrate effortlessly to address the persistent problem of working in different applications. Through the use of macros, Confluence gives you the ability to display Jira issues on a page, making it simple to create release notes, status reports, etc. You can also write product requirements in Confluence and quickly create Jira issues in seconds.  

Confluence-Jira-work-together

How Does Jira and Confluence Work Together? 

We commonly hear statements such as, "Our company is doing a great job tracking tasks through their lifecycle with Jira, but it's incredibly difficult to find the product requirements and the test cases being tested”, or “HR processed a new hire but we can’t find the original job posting or any of the received resumes associated with that new role”. Finding the associated documentation requires emails to be sent to numerous people (including but not limited to: product managers, product owners, HR personnel, administrators, etc) and digging through emails, GoogleSheets or even <gasp> Microsoft Word documents! And for times that you couldn’t find the original, how many times have you re-created the documentation or found an old version and hope that it would suffice? These are everyday problems in most organizations: Time is wasted duplicating efforts or searching for things that should be easy to find. Imagine what you could’ve completed if you had that time back. 

The integration between Jira and Confluence is much more than a pretty face:

  • It's seamless, making it easy to create automatic linking between the feature and the product requirements.

  • It allows for documentation to live perpetually and not be stuck in a comment box with a stale feature or HR requisition. 

  • It gives you one place for everything - no more searching your inbox, chat history, internal drives. 

  • It allows collaborative editing: multiple people editing a document together. 

  • It has Page and Space restrictions to allow for additional security when needed. 

  • It breaks down the barriers between teams when everyone is using the same overarching suite for working.

Jira and Confluence Better Together

Imagine being able to release with confidence, knowing your project is tracking on time, and ultimately giving your users the ability to find what they are looking for - faster. If you’re frustrated with disparate applications, contact us and let us make your life easier with Confluence and Jira. 

Topics: jira confluence how-to integration
4 min read

Reporting on Jira in Confluence with the Jira Issues Macro

By Morgan Folsom on Aug 27, 2018 11:00:00 AM

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.

Insert an issue count for a Jira filter

Let's start small. Insert a link to Jira with the number of issues returned from a Jira Query Language (JQL) query.

This is useful to pull up basic metrics for a high-level overview. The macro becomes a link to the filter, so if you want to review the issues in-depth, you can quickly hop over to Jira's issue navigator. The table below is an example of how our marketing team tracks employee blog post submissions.

 

To insert an issue count:

  1. Insert the Jira Macro
    1. Select the  in the top menu bar and select Jira Issue/Filter, OR
    2. Type { on your Confluence page, search and select Jira
  2. Enter in your JQL query
    1. To input an existing filter, type "filter = "Filter name", OR
    2. Type in the JQL directly
    3. Be sure to click on the Magnifying glass to execute the query
  3. Select 'Display Options' at the bottom of the dialog box to expand the options.
  4. Select 'Total issue count'
  5. Click Insert, and Voila!

Insert a single issue into Confluence

This macro can also link to a single Jira issue to a Confluence page. That means not only can you see what issues are important (and what status they're in) in your documentation, but you can also see who's talking about the issue when you're in Jira.

Take, for example, this blog post. My progress is tracked on a Jira issue, linked to this very page in Confluence. Below you can see how it looks on the Confluence page I'm writing in. 

If I click on that link, I'll move over to Jira where I can see all of pages in which the issue has been mentioned under Issue Links. Right off the bat, I can see that the issue has been mentioned on this page as well as another tracking Blog Content. 

To insert one issue:

  1. Insert the Jira Macro and enter in your query (steps 1 and 2 above)
  2. Select one issue from the list
    1. If you know exactly which issue, you can simply type the Issue Key into the search bar and hit enter. 
  3. Expand the Display Options and select 'Single Issue'
  4. Select 'Insert'

Use the Jira macro to insert a list of issues in a page in Confluence

Remember that filter you entered in above? You can insert that filter into your page, too. Filters inserted with this macro are dynamic - that is, as the issues are updated in Jira, the Confluence page will reflect the most up-to-date information. You can customize which columns appear in the macro just like you can in Jira. To head into Jira, you can select the individual issues, or click on the total number at the bottom ('2 issues') to pull up the query in Jira.

To insert a filter:

  1. Insert the Jira Macro and enter in your query (steps 1 and 2 above)
  2. Expand the Display options and select 'Table' 
  3. Edit the maximum issues and columns to display.
  4. Select 'Insert' to add to the page!

Create a Jira Issue from a Confluence page

If your issues don't exist in Jira yet, don't worry. This macro can create new issues in Jira if inspiration hits while you're editing a Confluence page. The issue will be created and you won't even have to leave the page. 

Additionally, you can also create issues from Confluence while viewing a page - simply highlight some text and then click on the Jira icon that appears.

  1. Insert the Jira Issue Macro
  2. Select 'Create New Issue' on the left panel
  3. Complete the form
  4. Select 'Insert'

This one macro can solve many of your reporting needs in Confluence. What's more, you can provide context around the data instead of just straight data. The Jira Macro is a great way to keep team members informed without navigating from Confluence to Jira and back again. 

Interested in learning more tips? Check out our blog Guide to Import Linked Issues into Jira from CSV.

Topics: jira blog confluence optimization process-consulting integration
4 min read

Ideation to Implementation with Lucidchart and the Atlassian Trio

By Praecipio Consulting on Feb 22, 2017 11:00:00 AM

Guest post by Lucidchart

As the first third-party app to integrate with Confluence, Jira, and HipChat, Lucidchart allows you to add diagrams to each of these Atlassian tools in order to clarify your ideas and foster collaboration. The Lucidchart add-on will feel like a natural extension of your Atlassian apps. Using Lucidchart in conjunction with this powerful trio can improve the effectiveness of your team collaboration all the way from ideation to implementation.

Start your brainstorm in HipChat

How many times have you kicked off a project with a team brainstorm consisting of a stuffy conference room, a single whiteboard, and a designated scribe? And how many times have you failed to take a photo of that whiteboard and lost your entire brain dump to the eraser?  

Forget the whiteboard and the conference room. Start a brainstorming discussion within a HipChat room and use a Lucidchart diagram as your virtual whiteboard. By typing /lucidchart in the message bar of any HipChat group room, you can get your whole team collaborating visually. Every member of your team, regardless of physical location, can add ideas to the diagram in real time. Ideation is documented in an editable format for easy reference. 

Any time you need to resurface a particular diagram for further discussion, simply use the Lucidchart share button to post your document to a HipChat room to invite more real-time collaboration.  

Store your ideas in Confluence

Once you have all your ideas documented and organized in a mind map, flowchart, or other diagram, use the Lucidchart Confluence add-on to ensure safekeeping. Share your diagrams on a centralized platform that anyone at your company can access. Add your diagram to an existing Confluence page to clarify the ideas already there, or start a new page for your diagram and add necessary context—both help to ensure employees have the right information for streamlined project completion. 

Even if you make edits to your diagrams in Lucidchart, those changes will be updated in Confluence without you having to re-upload a single diagram. Confluence can become a centralized platform serving as a single source of truth as you begin to carry out ideas.

Take action in Jira 

As you begin implementation, you can plan, track, and report on your projects within Jira. Add Lucidchart diagrams to supplement complicated ideas with eye-opening visuals—make it easy to understand what action is needed. 

Attaching your diagram to a Jira issue eliminates the hassle of emailing documents back and forth and trying to keep track of the most updated version. It’s the most efficient way to communicate with your team. 

Start using Lucidchart and the trio

Lucidchart and Atlassian can save any department time and money as they develop innovative solutions. Here are a few ways you can start using the combination of Lucidchart and Atlassian within your organization. 

  •  Product: Start with a Lucidchart document in HipChat to brainstorm product design with your team. Add the diagram to a Confluence page containing other crucial data that the whole team can reference. Once you start building the product, attach the diagram to the appropriate Jira tasks to communicate work that needs to be done.
  •  Engineering: If you’re dealing with a project involving previously documented architecture, post the existing UML or network diagram back to HipChat for further discussion. Edit the document to reflect proposed changes and then embed it in a Confluence page or attach it to a Jira issue to convey the underlying architecture.    
  •  Marketing: Create a flowchart in your marketing HipChat room to map out the different email campaigns currently running. This chart will help you identify areas where you need additional emails or where you need to cut or consolidate emails. Embed the diagram in Confluence so you can easily reference it as you make the proposed changes to your campaign flows. Then add it to Jira to track the emails being adjusted.

Pairing Lucidchart with your favorite Atlassian workplace applications can improve the efficiency and communication of your team. Make visual thinking a key part of moving a project from the whiteboard stages to a finished product. Learn more about Lucidchart’s Atlassian integrationsIf you would like to use Lucidchart with your Atlassian tools, please contact our friends at Praecipio Consulting.

Topics: jira atlassian blog confluence hipchat implementation lucidchart product-services integration
8 min read

The 4 Phases of Agile DevOps with Atlassian

By Praecipio Consulting on Aug 15, 2016 11:00:00 AM

As Development and IT Ops teams look to be more efficient, decreasing their time to market and increasing product support, DevOps has become the predominant industry solution. There are many resources that paint a picture of the ideal processes for Development and Operations working harmoniously together- but how do we actual get there? Where should we start? 

We need to begin with the end in mind. Our end goal is to deliver customers the software they need as fast as possible. The software industry is faster and more dynamic than the businesses of physical products. We need to get our customers features so they can give us crucial feedback while beating our competitors to market. The faster release development goes from concept to code, the quicker we can make customer happy. DevOps is a broad term with a variety of meanings, but at the end of the day, it seeks to increase the collaboration and automation between Development and Operations so we can get more frequent and higher quality releases into the hands of our customers.

When it comes to collaboration and automation, a focus on process and the use of the Atlassian suite are the best way to get there.

 The infinite loop of developing and supporting products that customers need and want with DevOps and the Atlassian Suite.

Image source: Atlassian 

Selling DevOps

The pain of hectic firefighting and troubleshooting make the need for DevOps obvious on the frontline, but getting alignment and investment at the organization level can be pretty difficult. Successful implementation is going to require buy-in and support from a variety of stakeholders and many levels. Before we can get our hands dirty, we need to convince everybody to spend the time and money to get these processes and tools in place.

Here are three ways to get the ball rolling:

One for the Book Club: Phoenix Project

Everybody has those business books that revolutionize the way they manage their work and companies. The Phoenix Project by Eugene Kim narratively addresses and exposes the gaps in processes between teams and points to a DevOps prescription to unblock cross-team work. We highly suggest recommending it to your teams, as it's a great way to get everybody on the same page and really see the value of DevOps.

Build a Business Case

At the end of the day, businesses exist to make money. To invest time and effort, we need to calculate the business return. The 2016 DevOps report from Puppet Labs does a brilliant job showing the financial reasons to adopt this shift.

The ROI of reducing excess work with DevOps according to 2016 DevOps report from Puppet Labs

Image Source: Puppet Labs

Phase 1: Go Agile

To get the real benefits of DevOps, it requires a shift in mentality and how we manage work through our teams. As we break down our requirements into smaller individual user stories, we can flow the work through the features through the process faster. By having the structure, ceremonies and processes in place to accommodate smaller pieces of work, we can get our customers the features they need and incorporate their feedback to iterate the next, improved release faster.

Here are some helpful ideas to help your teams go more Agile: 

  • Get Up, Stand Up | Simply doing stand-ups doesn't mean you're all the way agile, but it's a great way to get our teams into the mindset. Keep them short and reduce the headaches of status updates and emails. Fill everybody in on what you did yesterday, what you're doing today, and what pesky blockers are in your way. It's facilitates more agile and responsive team collaboration and support (the heart of DevOps).
  • Iterate Everything! | Speed up that Agile transformation, breaking down your waterfall projects into smaller sprints so you can always reprioritize and adjust as needed. Start with your software teams and spread out to your IT Ops projects and even marketing projects. Start in your own department: find the planning spreadsheets with those idealistic due dates, set up a backlog, and start sprinting!
  • Agile Boards | Once you're planning and executing in sprints, track and visualize it on a Jira Software board. Avoid those dreadful status meetings and send out the link to the board to keep everybody informed. Also, throw some wallboards up around the office so everybody can see your team killin' it. 

You'll know you're a lean, mean, agile machine when your software teams are cranking out stories in a steady cadence of sprints. Over time you'll see that velocity stabilize - then you can accelerate!

Phase 2: Get with Gitflow 

Git and Gitflow is a great way to help our dev teams increase velocity. As we're working with smaller stories, we need to be able to collaborate effectively with on our code base so we're not stepping all over each other. Version control systems of the past aren't going to be able to keep up with our blazing fast development teams. Bitbucket and the underlying technology of git are going to let our teams build user stories and merge them into the code base without wasting time messing with annoying versioning issues and costly code conflicts. 

  • Start with the Basics | Start by learning (allthethings) about how to effectively manage your branches and build in code quality with Atlassian's Git Tutorials and the Git Getting Started guides. Share them with your team so everybody's on the same page and knows the difference between a commit and a pull request.

  • Move to Git | If you haven't made the cutover to Git quite yet, get your team and managers onboard by sharing the benefits and how it will help ship more code. Once folks are convinced, learn why Bitbucket is the Git solution for professional teams and helps with pull requests, branching strategies, permissions and scalability. When it's time to actually move all that code over, see how we helped Splunk get git and 4 times the number code reviews completed. 
  • Start Branching | With the tools in place, it's time to start branching! Learn more about some common workflows to better handle branches here. Utilize those pull requests to build in code quality as you go. Eventually your Dev team will be humming with full Gitflow and your Ops teams will be in love with the clearly designated branches.

  • Automate, Mate | The marvelous integration between Bitbucket and Jira Software lets us automatically update the Jira issues based on what's going on in Bitbucket. Developers don't need to switch context anymore to keep the ticket up to date, and the whole team gets an accurate idea of what's actually going on. Check out our Automation Webinar to learn more about the powerful workflow triggers that make this possible.


The Gitflow branching strategy shown above utilizes different branches for specific roles like hotfixes and releases to help manage larger and more complex projects. 

 Image Source: Atlassian

Phase 3: CI/ CD

The next phase is how we define the crucial handoff between Dev and Ops. When our units of work and code changes are smaller, we're going to need to deploy more often to get those features to our customers. Before we ship it to the ops team and production, we need to ensure quality as our individual features come together. This is where good Continuous Integration/ Continuous Deployment practices along with Atlassian's Bamboo are vital to successfully shipping our product. Catching bugs and issues before they go to production is going to help both the Dev and Ops teams sleep better at night.

  • Learn about Bamboo | For on-prem Atlassian users, Atlassian's Bamboo is the CI/CD solution that allows professional teams to build their CI/CD pipeline. You may be using Jenkins or other open source teams, however the deep integration points and improved build management make it the right choice for professional teams.
  • Integrate with Jira | Once you have Bamboo up and running, leverage the integration between Bamboo and Jira Software.
  • Bitbucket Pipelines | If you're an Atlassian cloud user, Bitbucket Pipelines is a new, powerful solution in Beta that lets developers build, test and deploy directly from Bitbucket. Developers have the power as they can define the environment and tests for their specific branch with YAML file style configuration.
  • Dockerize Everything! | Docker and containerization is the latest craze sweeping the IT world as teams look to deploy applications to any environment faster and easier. Check out our Docker +Atlassian webinar to learn more about how. As partners with Docker, we love to helping teams harness this cutting-edge technology.
  • Automate Testing | Automating testing with tools like Charlotte, QA Symphony, and Zephyr (which integrate with Bamboo and Jira) gives your development team an even more agile edge. Get efficent, high-fidelity testing to expedite the finding and squashing of bugs to ensure your next iteration is the best version.

Phase 4: Harmonize with Support

Once the story is shipped, the process does not end. Now it's time to keep the product working and collect that vital feedback we need.

  • Check out our webinar, DevOps with the Atlassian Suite, for a full picture of how development and operations are going to work in harmony.
  • Set up a product feedback service desk in Jira to really hear your customers and integrate directly with development teams.
  • Learn how to set up your Service Desk teams for success with our ITSM webinar.


By implementing the right DevOps tools and processes, you'll see the faster shipping of higher quality and better supported releases. As your Development and Ops teams continue to execute these lock-step processes, you get more agile by good practice. Take the steps to start implementing DevOps today by contacting us to get up and sprinting.

Topics: jira atlassian blog scaled-agile automation bitbucket bugs continuous-delivery bamboo branching devops docker distributed-version-control-system process-consulting qa-symphony sdlc selenium software sprint testing version-control-system workflows tracking continuous-integration cloud development integration it operations release-management marketplace-apps
3 min read

How to Expedite Approvals with DocuSign for Confluence

By Praecipio Consulting on Aug 4, 2016 11:00:00 AM

According to IDC's 2015 report, The Document Disconnect, 76% of executives and managers in sales, HR, procurement, legal, and other departments estimate that fixing the “document disconnect” can lead to document process issues impact revenue recognition or create auditor issues. As process improvement experts, we at Praecipio Consulting love saving our clients money by mitigating wasted time and helping them do work faster. With that in mind, we've compiled our top 4 tips to get faster approvals leveraging DocuSign for Confluence to integrate your mission critical document tools. 

1. Maximize Your Macros 

Confluence macros add significant value to your document drafting process with their features and functionality. Just select from your macro options and voìla - your desired information appears! By utilizing the out-of-the-box DocuSign for Confluence macros, you can simply drop the macro for your DocuSign tabs (ex. signature, initials, date, title, and more!) into your document right inside of Confluence. Adding this functionality to your document drafting allows you to save time otherwise spent selecting and adding these approval actions outside of Confluence, and also ensures that your document collaborators can see the macros you're adding and where.

Select from the menu of macros to inform your signee of what do provide.

2. Template-ize It! 

Think of the documents you create the most frequently. From sales and marketing to HR and legal, every department has documents that need signatures and approvals on a daily basis (often multiple times a day). Save your team countless hours by creating Confluence templates for these frequently used documents and reduce unnecessarily wasted time. Your Space administrator can add these templates (including the aforementioned DocuSign macros) to your instance, in the spaces you need them, so you can now spin up your next contract with the click of a mouse. 


In Confluence, click 'Create' and get prompted with both custom and out-of-the-box templates.

3. Streamline Sending 

It's simple logic: the faster you send your document, the faster you can get approvals. However, cumbersome sending processes can keep you from firing off that contract as quickly as you'd like. Leverage DocuSign for Confluence to send documents from Confluence (including all the attachments and pages your heart desires) to not one, not two, but as many recipients as you want! Set action type and order in this same step to determine who needs to sign, who needs to receive a copy, and the sequence in which these actions will occur. 

When adding recipients inside your organization, names are pulled from your Confluence user directory so you can send even faster.

4. Track in Real-Time  

Being able to see where your document is in the approval process is invaluable when you're waiting for that proverbial ink to dry. DocuSign for Confluence provides real-time status notifications so you can track your documents, from sending to completion. By simply clicking the DocuSign lozenge at the top of your Confluence page, you see what stage your document is in and who has completed what action. Additionally, clicking the status to see approval actions on the document in DocuSign. This level of visibility allows you to see when you're DocuSign envelope has been created, sent, and signed to give you the most accurate document tracking. 

View the status of all your DocuSign Envelopes in one streamlined view.

Improving processes relies heavily on cutting our unnecessary intermediary steps that can become blockers. It's these steps that, unchecked, can cost a company thousands of hours that could otherwise be spent focused on core competencies. As process experts, we recommend to all our clients- from 20 person startups to Fortune 5 enterprises- to ask themselves the following questions regarding their processes:

  • Can it be repeated? 

  • Can we automate it?

  • Can we eliminate unnecessary steps?

By optimizing your repeatable e-signature processes with DocuSign for Confluence, your organization not only saves time, but also reduces document processing issues that cut into profit or jeopardize compliance with auditing agencies. 

Ready to expedite your e-signatures? Get DocuSign for Confluence and start getting your fastest approvals.

Topics: atlassian blog confluence experts hipaa marketplace process-consulting regulation sign service-level-agreement tracking compliance docusign e-signature fda integration productivity atlassian-products marketplace-apps bespoke
3 min read

Three Reasons Why Developers Love Docker

By Praecipio Consulting on May 6, 2016 11:00:00 AM

A smooth running production environment is a beautiful thing. But how do we get there? And how do we ensure that all of our production, staging/test, and development environments stay in sync in order to get there? Today, it seems like everyone in software development is talking about Docker and containers. In fact, according to the 2016 State of the Cloud Survey by RightScale, Docker adoption doubled from 13% to 27% in just one year. Furthermore, 35% of the organizations surveyed reported that they have plans to adopt it soon. 

Why has Docker adoption skyrocketed and how can those using Bamboo for continuous deployment reap the benefits? Check out three reasons why developers love Docker, and how it can provide value for your dev team. 

But first... 

What are Containers?

A Docker container packages software in a complete filesystem with everything it needs to run – such as code, runtime, system tools, system libraries – guaranteeing that it'll always run the same on any environment. Docker is all about creating consistency and encouraging collaboration. It revolutionizes how we share our environments the same way Git has changed code collaboration. At its core, Docker is about utilizing the least amount of operating system resources and dependencies needed to run an application. This focus on maximizing efficiency leads to a painless, more collaborative, and seamlessly integrated environment to test and deploy applications. 

Sourcewww.docker.com

1. Test without surprises

A crucial part of the development process is testing, whether on a local machine or in a virtual dev environment. With containers, every environment is exactly the same so changes and unexpected dependencies won't interfere with testing – saving developers time and energy from tweaking problematic environments and instances. 

Running containers on your local machine using Docker Quickstart Terminal lets you test in a consistent environment.  

2. Collaborate with consistency

Unexpected dependencies are already a hassle for one developer and becomes an even bigger headache when other devs enter the picture. Unknowns in an environment are amplified with each new team member – who knows what's on their machine or which version of Java they're running? With Docker, consistency facilitates collaboration. By starting with a known configuration in a common container, devs are always on the same page about which version to use; it's right there in the container.

Share your Docker Images with a registry like Docker Hub.

Source: https://hub.docker.com/_/hello-world/

3. Integrate with Atlassian 

Atlassian, the leader in enterprise software for collaboration and issue tracking, is the perfect complement to Docker. By pairing Docker's consistency with Atlassian's integration and automation, collaboration between development and IT ops becomes seamless. Using the new Docker Hub 2.0 with Atlassian's Bamboo, source code can be automatically built and deployed to an identical development, test, or even production environment. No more requesting environments from the IT ops teams; triggers will automatically fire from your approved pull request in Bitbucket to spin up a lightweight container in your QA environment almost instantly. Without the excess back and forth, you can go from source code to a running application in minutes. 

The Docker Task in Atlassian's Bamboo let's you run, build and deploy images and containers with ease.

Docker is picking up a lot of traction today and rightly so. Docker containers provide consistency in the turbulent world of software development environments. They allow dev and operations teams to get customers the applications they need now – all while providing a consistent environment that makes working together a whole lot easier. 

To learn more about how Docker and Atlassian can help your dev team work faster and smarter, contact Praecipio Consulting.

About Brendan Kelly

Brendan is a Consultant & Solutions Specialist at Praecipio Consulting where he enables the sales team through technical discovery, training and product demos. When Brendan isn't delivering best-in-class business technology solutions, he can be found in the Austin Green Belt hiking and bouldering. 

Topics: atlassian blog automation continuous-delivery bamboo docker optimization process standardize testing continuous-integration deployment development environment integration cicd
7 min read

Seen It, Solved It: Jira Service Desk for ITIL

By Praecipio Consulting on May 4, 2016 11:00:00 AM

Growth Through Change 

"Organizations that do not or cannot evolve will not last." In the business world, change is constant and necessary, especially when it comes to meeting the dynamic needs of customers. ITIL, or Information Technology Infrastructure Library, is a methodology that helps organizations effectively manage change while putting the customer at the center of the process. ITIL prescribes processes to ensure the customer's needs and requests are handled with ease – from acknowledgement of an issue through the application and evaluation of the solution. One of the greatest values of the ITIL methodology is that it embeds continual improvement into the process. The ITIL framework can be leveraged by anyone, including non-technical teams, to better manage change and serve customers. Atlassian's fastest growing product, Jira Service Desk, facilitates ITIL adoption in an organization by encouraging traceability, collaboration, and reporting. 

As business process experts certified in ITIL, we leverage the ITIL methodology in unison with Jira Service Desk to institute best practices for our clients. Here are 5 real-world examples of how Praecipio Consulting helped our clients implement lasting organizational change by embracing key ITIL concepts of automation, visibility, knowledge base, change management and evaluation, and continuous improvement. 

Automation

"Using service automation to streamline both simple and more complex workflows of course impacts the overall efficiency of the organization... it also allows for a much better end-user experience for everyone at the company." - ITIL beyond IT: What is Service Automation & Service Relationship Management?

Problem: A major utility company powering the U.S. Eastern seaboard was manually reporting security equipment issues and coordinating with external vendors to fix the issues. This manual process was prone to errors and didn't allow for tracking of service level agreements (SLAs), which would determine which vendors were breaching their contracts. The company was using spreadsheets to track these crucial assets and their maintenance. The spreadsheet system was inefficient and created duplicate versions – leading to confusion, frustration, and waste. Furthermore, the spreadsheets could not track SLAs for Acknowledgement or Resolution for vendors.

Solution: To reduce redundancy and enforce SLAs, our experts implemented Jira Service Desk for the major utility company. By replacing their spreadsheets with Jira Core and Jira Service Desk, we helped them add a level of automation to their workflow. This reduced waste of time and resources, allowed for better communication with third-party vendors, and created a clear path for escalation. The custom configuration we created for the company maintained their security, while also allowing vendors to be a part of of the conversation. Furthermore, reporting features from both Jira Core and Jira Service Desk allowed for a central point of truth. The utility company could check the status of service tickets and see how well vendors were adhering to their SLAs. Through the process of improving their security equipment reporting and vendor coordination, the company found other areas of improvement and have chosen to continue working with us to maximize those workflows. 

Visibility

"It can be very difficult to know the health of your service desk, run reports, and find way to improve your support if you don’t have the right data." - The ABCs of Jira Service Desk: measuring success

Problem: A major U.S. waste management company wanted to adopt a more structured reporting system, replace an old enterprise software application, and incorporate the ITIL framework into their organization. The company's goal was to standardize tools in order to improve communication and rally around a consistent project management methodology. The waste management company desired a suite of tools with the ability to integrate functions across IT service areas, leading to better service for the end customer.

Solution: In addition to implementing several other Atlassian products, our experts helped the company leverage Jira Service Desk to achieve their business goals. We helped them create a central application with the ability to distinguish request types through a structured workflow. This included a more robust user interface to better triage issues and send them to the appropriate teams. The ability to categorize requests and label them with levels of urgency allowed the company to have better reporting, leading to improved enforcements of SLAs. 

Knowledge Base

"[A knowledge base] gets [customers] the help they need at the speed they’ve become accustomed to – i.e., in the time it takes to swipe around on their phones – and it frees service desk agents from stressing out while anxious customers wait on hold or answering the same question over email for the 10th time this week." - 4 tips for getting started with knowledge management

Problem: A large, private U.S. university wanted to revamp an old software application and replace it with a more robust and dynamic knowledge base. The university's goal was to increase usability for both their students and faculty regarding technical and campus-related questions, deflecting tickets by providing requesters with FAQ's and other resources to help them self-serve to find their answers. 

Solution: Our experts helped the university leverage Jira Service Desk and Confluence to achieve their goal. Combining Jira Service Desk with Questions for Confluence (a Confluence add-on that provides a knowledge base inside the already powerful wiki tool) allowed the university to implement a centralized knowledge database. Jira Service Desk allowed for better help engagement using queues and other helpful functionalities. Questions for Confluence empowered external users to help themselves by accessing a database of pre-answered questions, without tying up service desk agents with redundant problems.

Change Management and Evaluation

"Listening to your customers is the single most important thing you can do for the health of your company." 5 tips to transform your IT team from zero to superhero

Problem: The largest provider of support services to general and multi-specialty dental groups in the United States needed the ability to receive and respond to client feedback in addition to handling client issues. They did not have a clearly defined process for patients to interact with the organization and to raise issues. Their marketing team was searching for a new software tool that would manage feedback in a way that led to issue resolution and change management. The team's ideal tool would be able to enforce and report on multiple SLAs through issues submitted via the company's public website.

Solution: Our experts helped the dental corporation adopt Jira Core and Jira Service Desk to manage issue tracking and change management. With Jira Service Desk, the company was able to cleanly sort through client feedback and create a workflow to address issues that arose. Beyond managing client feedback, the dental corporation also used these tools for clinical tasks, billing, and other activities that needed life cycle tracking. In addition to tracking, the Atlassian tools helped the organization evaluate the effectiveness of their changes and quantified the improvements made – empowering all teams, not just marketing, to better serve their customers. 

Continuous Improvement

"With a single-product approach, configuring an SLA or modifying a workflow is easy, because they share core processes." How Jira Service Desk approaches ITSM 

Problem: A major U.S. insurance company was using three different software applications for code management, issue tracking, and service desk management – leading to inefficiencies and miscommunication. Their use of three separate applications resulted in duplicate tickets and the inability to enforce SLAs across the organization.The insurance company wanted to improve these processes and embrace ITIL's practice of continuous improvement. 

Solution: Our assessment encouraged the company to adopt a single application, Jira Service Desk, to provide a single source of truth. With Jira Service Desk, there was a common point of collaboration for issue management. This reduced duplicate tickets and saved valuable time and resources. Leveraging entities, workflows, and issue linking, we helped the insurance company align their processes to make reporting and enforcing SLAs easier, more efficient, and more effective. By strengthening their ability to track what changes are needed and to act upon those needs, we helped them develop a cycle for continuous improvement.  

ITIL for One, and ITIL for All 

"Just because one service desk streamlines the IT and service departments, it doesn’t mean that other teams can’t also benefit from them." - 5 tips to transform your IT team from zero to superhero

These real-world examples from our clients highlight how ITIL and Jira Service Desk can help organizations evolve and change – without the growing pains. ITIL concepts of automation, visibility, knowledge base, change management and evaluation, and continuous improvement aren't just for IT teams. These powerful ideas also provides immense value to other parts of any organization, technical and business teams alike. At Praecipio Consulting, we excel at leveraging the ITIL methodology and Jira Service Desk to help organizations do what they do better. Want more proof? Contact us to learn how we can help your organization evolve and do your best business. 

Topics: jira atlassian blog scaled-agile automation business confluence process standardize workflows traceability collaboration continuous-improvement integration it itil itsm jira-service-desk operations reporting white-paper
2 min read

Hipchat: Customize Your Connection

By Praecipio Consulting on Sep 29, 2015 11:00:00 AM

HipChat has long been the beloved messaging application for Atlassian users, developing integrations with Confluence and Jira to increase the seamless nature of the SDLC process with notifications and team and project-specific rooms. With the success of these integrations, Atlassian is raising the bar for HipChat functionality, offering up their API for other software producers to code their own connections to allow even more tools to team with HipChat. Recently, Atlassian held a HipChat Dev event in San Francisco for a handful of popular and innovative tech companies to dev and demo their HipChat plugins, opening the door for an all new level of HipChat functionality. New Relic, Salesforce, Tempo and other Atlassian-inclined software makers came together to tweak the HipChat API to get their products talking for an even more robust integration offering in the messaging system. With many new options becoming available, excited HipChat users can expect to see these plugins available soon, making HipChat a real-time communication hub for all aspects of the software development life cycle.

HipChat, Meet New Relic

New Relic, maker of integral tools to gain insight into the operation of your business processes, becomes a critical component of IT management when paired with HipChat. Using New Relic products like APM, Browser and Synthetics, companies gain real-time analytics for their SaaS applications to ensure that their platforms are running optimally for the best user experience. When integrated with HipChat, New Relic provides teams regular status updates, allowing issues to be addressed efficiently and expediently. Create a HipChat room for New Relic applications and stay up to date with your application performance leveraging the constant monitoring of New Relic with the constant communication of HipChat. 

Build Your Own Add-Ons

Atlassian enables users of Jira, Confluence, and yes- HipChat, with the ability to build customized add-ons for Atlassian tools and corresponding applications. The provided documentation allows the use of any web framework and any programming language to build with Atlassian's REST API to get the applications talking with remote operation over HTTP. With the unlimited possibility of integration, HipChat becomes a true force of functionality as more and more applications are tied into the tool. Give each dev team their own HipChat room built around their products to get the latest updates on their in-flight projects. Create a marketing room to allow your bloggers to see immediately when a new page view or comment comes through. With HipChat customized add-ons, your teams get the information they need, when they need it. 

Video courtesy of Atlassian

It's in the Numbers

Need more reasons to expand your company's collaboration beyond just Confluence and Jira? Atlassian has the stats the make the case for HipChat!

Statistics courtesy of Atlassian

Chatting cuts down on unnecessary, efficiency-draining emails, enhances collaboration between teams and delivers a platform for easy communication. Using Atlassian HipChat, your teams run at the speed of business with application integration, video chatting, and file sharing -- everything they need to work smarter and faster! 

Get Chatting

Revolutionize the way your teams work with HipChat! It's as easy to get as it is to use; simply contact Praecipio Consulting to learn about our extensive HipChat services, including: managed services and hosting, implementation, customization and licensing. HipChat is your central source of better business practices and Praecipio Consulting is your one-stop-shop for all your HipChat needs. Collaboration has never been easier, so get HipChatting today!

Topics: jira atlassian blog best-practices confluence hipchat new-relic rest-api integration
3 min read

Introducing New HipChat Server

By Praecipio Consulting on Feb 9, 2015 11:00:00 AM

Effective communication is critical to the daily operation of your organization. Whether it's alerting your dev teams to the status of their latest release or brainstorming ideas for the next Happy Hour venue, your team needs a way to talk. With more companies operating disparately, the idea of around the watercooler conversations is now defunct and people look to technology to help them connect. It was this exact need that Atlassian sought to address with their chat platform, HipChat. 

During the lifespan of HipChat, 3.7 billion messages have been sent, 25 million files have been shared and 23 million video minutes have been logged, making it one of the most widely used chat tools on the market. Responding to the popularity and demand of HipChat clients, Atlassian has expanded the product offering to now include a host of features and functionality that propel HipChat into an elite, unmatched realm of chat tools that bring simplicity and reliability.

Meet HipChat Server

Behind the Firewall

With the increased capacity for file sharing and features like private rooms for sensitive conversations, the need for security in your chats is paramount. Now with a Server option, you can run HipChat behind the firewall for the utmost security to keep your private conversations truly private. HipChat Server is also ideal for those unable to run cloud applications, allowing HipChat to run on your own server (or outsourced server hosting, as offered by Praecipio Consulting!).

Increased Integration

Link your HipChat Server up with other Atlassian applications like Jira, Stash and Confluence to increase communication between teams and keep everyone up to date on projects. Is your team's latest build ready for release? With a DevTeams room in HipChat, Stash will notify your team! Tag a co-worker to review a document in Confluence? HipChat will let them know. Integrate with the HipChat bot lab (or build your own) to sync your HipChat Server instance to an unlimited number of applications for maximum traceability. 

Enhance Culture & Collaboration

HipChat makes it easy for teams to communicate, boasting features that make the platform your organization's key resource for staying in the loop on work happenings from presentations to co-worker's birthday plans.

  • File Sharing- No more asking "Did you e-mail me that file? Or did you share it with me in the drive?" Just HipChat co-workers your images, presentations and important documents. They'll have it at their fingertips in an instant!
  • Video & Phone Chat- With teams spread out all over the world, sometimes it's nice to hear the voice or see the face of a teammate you don't often encounter in your home office. Use HipChat's video and audio chat to stay in touch and up to date!
  • Team Rooms- Need a space to brainstorm? Get a room! Create rooms for group needs to discuss specialized subjects like Marketing or hold a private conversation for more sensitive information like HR.  
  • @Mentions- Get peoples' attention with the @mention feature in HipChat to let them in on the conversation. Additionally, using @all notifies everyone in a room of a conversation. 
  • Emoticons- Why lie? You know the awesome emoticons are the real reason you use HipChat. With HipChat Server, you get all your favorites: (mindblown), (allthethings) and, of course, (celeryman). 

New HipChat Server brings you all the functionality you know and love, from file sharing and video chat to those ever-entertaining emoticons, but with the added benefits of running behind the firewall. Interested in HipChat Server (or any other Server-versions of Atlassian products) but don't have the bandwidth to host yourself? Let us host for you! At Praecipio Consulting, we provide Atlassian hosting to companies of all sizes to ensure you get the instances you need without the organizational strain that comes from internal hosting. With Atlassian and Praecipio Consulting, you can bring your teams the tools they need to achieve their best collaborative practices (and play with some fun emojis while they're at it). Contact us to learn how we can bring new HipChat Server to your company!

Topics: atlassian blog best-practices hipchat collaboration culture hosting integration
2 min read

Jira Portfolio Cheat Sheet

By Praecipio Consulting on Jan 13, 2015 11:00:00 AM

For projects big or small, Jira Portfolio helps you plan it all! With the ability to pull work in progress in from Jira or push the work breakdown structure into Jira, Portfolio makes managing projects a breeze. With a little set-up and some good old-fashioned planning sessions, your organization can quickly view release schedules, track estimates and actuals to business strategy targets, and manage resources in one place. 

Setup is key with Jira Portfolio. Simply choose your plan type, then work right to left: Configure, Reports, Releases, People. Once you have the business strategy and available resources, then populate your Backlog. Importing an existing set of issues from a saved filter in Jira requires only a few clicks. Or, if you prefer, create your plan and push individual initiatives, epics, stories, and defects into a single project or multiple projects. For those that are truly Agile, plan and push Epics into Jira, then allow the teams to develop and estimate Stories. Synchronize your plan and you're able to predict releases and inform stakeholders.

Push 

Dial in your plan before work begins. Add level of effort estimates and link Epics and/or Stories together to create dependencies. Then let Jira Portfolio inform you of a missing skill set, plan your sprints, or predict the release schedule. 

Pull

Mitigate risk and communicate with stakeholders with ease. Importing in-flight work provides stakeholders with more accurate release schedules based on current work efforts. Mitigate risk by seeing how new work and dependencies affect the overall schedule. Flex resources across teams to fill skills gaps. 

Choose 

Which of the five key capabilities of Portfolio Project Management are you trying to manage: change, risk, resource, pipeline, or financial? Let the capability determine whether a push strategy or a pull strategy works best. The answer may be to use both strategies in the same plan. 

Learn more about Jira Portfolio and get an in-depth demonstration in the tool with our Introduction to Jira Portfolio webinar.

Topics: atlassian blog scaled-agile best-practices integration marketplace-apps
6 min read

Top 12 Jira Questions of 2014

By Praecipio Consulting on Dec 29, 2014 11:00:00 AM

On December 3rd, we went where no Praecipio Consulting webinar has gone before: We answered your Jira questions live! Between pre-submitted questions from webinar registrants, online Praecipio Consulting followers, and real-time queries from viewers, our resident Jira expert Christopher Pepe fielded the questions you most wanted answers to. We were thrilled by your response to the call for questions and feel the answers to be so helpful that we decided to share them with the Jira-using public at large! From new Jira users to experienced technical leads, here are the top Jira questions and answers for your inquiring minds.

 Q: We have yet to find a way to enter our estimates in a manner that gives us valid burn-down charts on agile projects and would like advice. The process we use is as follows:

  • Issues are entered into Jira (into the backlog) with a high level estimate.
  • When we get into a sprint, we'd like to create sub-tasks that reallocate the hours in the original task (e.g., a story is entered with 40 hours, then the team determines that there will by 6 hours of BA work, two 8 hour development tasks, 8 hours of QA, 2 hours of documentation, and some PM work that can be logged against the main story).

Presently, we see the subtasks showing as additive and in the scenario above it ends up looking like there are 72 hours. How would you recommend that we solve this?

A: (6:04) The way Jira handles time tracking, all of your time is rolled up, so your time is double-entered. Take the original hourly estimate, delete from parent ticket (as it misses the intent of the time-tracking) and either a) don't include time estimates in the original story or b) make your stories into epics and give all sub-tasks (tests, bugs, etc.) time estimates that roll-up to give a more accurate picture of time tracked. It's also worth noting that, as people are generally not the best at estimating time, one could utilize story points to track time and establish velocity across your Agile team. For example, this new feature will take x amount of time based on x amount of sprints (compared to previous tasks of the same type). 

Q: Can we delete Statuses from already published Workflows? 

A:  (9:26) Historically no (and I believe that's still the case). You have to copy the workflow and modify, or rebuild. Then map it back to your workflow scheme, deleting the status.

Q: We are creating different issues-types for different entities, User Story, Task, Test, Bug, etc. Does having these many different issue types create complication? Is it convenient to keep track of these issues? For Ex. 1 User story might have 3 Tasks, 2 Tests and 4 Bugs, isn’t that creating linking issues or traceability issues?

A: (10:42) This is a big question and the answer is really our whole business at Praecipio Consulting, as we seek to model your processes to Jira for connectivity across all systems. Creating an efficient data model in Jira can be challenging. You're taking the right approach in thinking about how to model your data. I can't advise you without knowing more about how you operate, but recommend you think about making your Stories into Epics in Jira Agile, and then add your Tasks, Tests, and Bugs to the Epic. That really simplifies the issue linking.

Q: Is there a quick way to see an issue's priority when looking at it on a board besides filtering it?

A: (13:54) Yes, the priority is shown by its icon. Hover over to see what it is. Agile packs a lot into a little space

Q: Is there a way to automatically move an issue to a different workflow when the issue type changes. Like any Post-Function?

A: (15:29) Jira will automatically do this. It means that your Workflow Scheme needs to have different workflows configured for the issue types. If workflows have different custom fields, Jira will force you to go through a mapping stage. No post-function is needed!

Q: What options for Pass Through Authentication exist? Are Add Ons the most often used method? Are there other ways of doing this without paying hefty prices? 

A: (17:44) Add-ons are really the only way. There are REST authentication resources so if you can control intercepting the username and password you can hand them off to the application, but if your mechanism isn't HTTP based its hard to get the token in the users browser. Atlassian's Crowd is a popular choice, providing a single-sign on platform for authentication through multiple avenues.

Q: Beside custom fields, what other system configuration items can cause poor system performance? Permission schemes? Notification schemes? If so what are some best practices for these? 

A: (20:35) The short answer is: lots of schema. Custom fields, complicated workflows and the like can contribute to slower performance. Finding bottlenecks is challenging. Many layers of monitoring is the best approach (Maybe you don't have a big enough thread pool or your disk access speed is too slow.) to make sure you can see what the JVM is doing. New Relic offers simplified yet robust monitoring capabilities for these purposes 

Q: When entering a custom field, what is the best practice for configuring the field for specific issue types/projects versus a global context (all issue types/projects)? We have custom fields that will only be used for one or two issue types and a subset of projects, but we have configured them as all issue types/all projects. Is there a downside to this configuration?

A: (24:35) I encourage new admins (and even seasoned ones) to use global context and focus their energy on designing screens and related schema to get a project to operate as expected. Context makes it hard to track down why a field isn't showing up or some odd behavior that's occurring.

Q: How can I make an issue editable when the status is already closed? Also, I am unable to add a transition from a closed issue to another status. 

A: (27:25) You should be able in the workflow editor to create a transition from closed. Jira may be blocking this, since closed issues are uneditable. The default workflow that comes with Jira, if copied, wouldn't allow you to edit a closed issue- so the properties associated with the workflow are copied too. You'll need to edit your custom workflow and delete this property or create your own. 

Q: Can we add more fields in ‘Test’ Issue-type, like currently there are Test Step, Test Data and Expected Result. Can we include columns for Module, Test Scenario, etc.?

A: (30:18) Yes you can add more fields by modifying the Screens and maybe Field Configurations. You may need to create your custom fields first too.

Follow-up: (in the Zephyr panel shown in the issue) No, that is not configurable. You should tell Zephyr that you'd like it to be.

Q: Can you fix the Jira header to stay at the top of the page when scrolling?

A: (37:26) There isn't a way in the Jira UI, but if you go and inspect the element, you will find that the header bar is just a div (and stuff inside it) that you can target with CSS or Javascript to fix the hold. In Javascript, present it to Jira by creating an add-on and install. This helps you control the context and action. If you only want it on issue view, you'd add the Javascript to the field configuration. Having this function as an add-on helps future system admins know that it's an individual, customized feature that can be found and identified.

(If you listen to the webinar audio, you also hear our Jira Expert cat weighing in on the subject as Christopher Pepe translates.)

Q: What are the benefits of a federated Jira instance?

A: (41:06) Atlassian has several resources on the benefits of managing multiple instances through federating. The only places where we really see people federate instances is in industry mandates (ex. industry permissions for viewing data) or when different groups within an organization need individual ownership. In this case, you'd create application links between the two instances to allow reporting from one instance to another; the pitfall is that you can only get results from one instance at a time. 

When it comes to Jira, there is so much to know and learn! At Praecipio Consulting, we bring our Atlassian expertise to Jira and the entire product suite through our webinars, trainings and full service offering. Still have Jira questions or want to apply our experience to your instance? Find out how we can answer your questions and get you your best instance by contacting Praecipio Consulting. 

Topics: jira blog scaled-agile best-practices training configuration consulting-services integration
1 min read

Show your smarts with Confluence questions

By Joseph Lane on Aug 28, 2014 11:00:00 AM

As Abraham Lincoln famously said, "You can't trust everything you read on the internet." Those familiar with this anachronistic meme appreciate the sentiment behind it, as does anyone who has ever reported erroneous facts found while combing the interwebs. In today's fast paced world, you need reliable answers to your questions on demand.

Confluence Questions delivers search engine capability and collaborative communication across organizations that allows your entire team to demonstrate their expertise. Whether you want to know how to insert a macro into a template or where to get a speedy oil change during lunch, your queries are answered in real-time with the same collaboration and transparency you know and love from Confluence. Confluence Questions allows you to connect with experts in your organization by posting questions and up-voting the best answers for quick search-ability. 

 

LEARN MORE

Leverages your company's brain trust to provide the best answers, easily located, through the collaborative ability of Confluence. At Praecipio Consulting, our team are Atlassian Experts- when bringing clients best in breed practices and in competition. In conjunction with the release of Confluence Questions, Atlassian hosted Tour de Confluence Questions, an international competition to find the top exerts in the world- of which our own Charles Wells is among the top ranked! Interested in learning more about how to leverage Confluence Questions to find experts in your organization? Check out Charles in Praecipio Consulting's  webinar, The Experts Among Us: Finding Expertise via Confluence Questions. 

Topics: blog confluence implementation integration
1 min read

Brikit: Getting More From Your Confluence Investment with Theme Press

By Praecipio Consulting on Aug 7, 2014 11:00:00 AM

Software developers have known for years that Confluence is the ultimate collaboration tool. While the value may be apparent for some parts of your organization, others might be intimidated by new technologies, preventing your company from reaping the full return on your Confluence investment. Accentuating the power of Confluence to share information, Brikit's Theme Press gives companies an out-of-the-box tool that will trigger a Confluence adoption craze across your whole organization. Perfect for company intranets as well as external use, the beautiful design and unrivaled usability of Theme Press gives you the flexibility to customize your website for your purposes.

At Praecipio Consulting, we customized our Confluence-based website utilizing Theme Press while incorporating new pages and content into the same design. Victor Vargas, Praecipio Consulting's in-house graphic artist, pushed Theme Press to the max and was excited about the results. "As a designer, it's an effective and robust platform to use." Our new website even caught the attention of Brikit founder Darryl Duke, who featured praecipio.com (at 6:54) in this online Theme Press demonstration. To that end, we at Praecipio Consulting are excited to add Theme Press implementation to our robust service offerings, bringing this innovative platform to new and existing Confluence users. Contact us to learn how Praecipio Consulting can revolutionize your Confluence with Theme Press.

Theme Press has taken Confluence outside of the development team silo and launched a simple, dynamic, user-friendly platform that increases adoption across your organization. With customization, endless design possibilities and the easiest of editing capabilities, Theme Press puts a new spin on an old Atlassian classic to bring Confluence to a wider audience than ever before. 

Check out praecipio.com at 6:54!

Topics: blog brikit confluence implementation technology-partners consulting-services integration marketplace-apps
2 min read

Jira: Not Just for Software Development

By Praecipio Consulting on Aug 17, 2012 11:00:00 AM

Jira’s an issue tracking application, but its core flexibility and strengths mean it can become much more than a tool limited to a development group. Jira’s incredibly adept at helping teams track and accomplish tasks. Jira also has a masterful ability to manage life cycles - and it’s found great success in numerous use cases.

Use Cases

The following use case guides are meant to explain a bit of the details related to using Jira for a specific use case. The info you’ll find in here highlights much of what we’ve learned from working with clients in a variety of different industries, as well as our internal expertise and use of Jira.

For each of these use cases, we’ll attempt to highlight:

  • Particular Jira functionality specific to the use
  • Related plugins we’re aware of
  • Customization and tweaks
  • …and sometimes a sample file to help get you started

General and Non-Software Uses

Agile Software Development

Project Management

HelpDesk / Support / Trouble Ticketing

Test Case Management

This can be done by using either of the following approaches:

Requirements Management

Change Management

Topics: jira atlassian blog scaled-agile austin automation business efficiency enterprise issues management process services technology value tracking change cloud collaboration computing continuous-improvement incident-management information integration it itil itsm operations

Praecipio Consulting is an Atlassian Platinum Partner

This means that we have the most experience working with Atlassian tools and have insight into new products, features, and beta testing. Through our profound knowledge of Atlassian environments and their intricacies, we can guide your organization as you navigate these important changes.

Atlassian-Platinum-Solution-Partner

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us