Top 5 Most Requested Features for Confluence 2016

December 6, 2016
#News#Confluence
2 min

In our post last year we reviewed the most requested features for Atlassian Confluence, this year we decided to take a new look at them and see what has changed since that time.

At first, let’s remember Top 5 Most Requested Features for Confluence in 2015. That list looked as follows:

But what’s the destiny of these requests today? Well, let’s see. Continue reading “Top 5 Most Requested Features for Confluence 2016”

Three approaches to editing pages in Confluence 6

November 29, 2016
#Confluence
1 min

All the people who use Atlassian Confluence Server were waiting for the release of Confluence 6. Every major product version brings great changes for users. Confluence 6 was released with only one major feature, but this feature is very special. Collaborative editing became available for everyone. Let’s take a look at it.

How collaborative editing works

Continue reading “Three approaches to editing pages in Confluence 6”

Case Study: Frontend Mentioning for Confluence

October 20, 2016
#Confluence#Case Study
2 min

We were looking for a seamless integration of a major performance improvement for the usage of Confluence. The StiltSoft team provided a fast approach and delivered in time, in cost and in quality. Now, we are looking forward to working again with Stiltsoft for the next release.

P. Eckelmann

About the Customer

Some time ago we completed a challenging project for Philipp Eckelmann, the private owner of several add-ons in the Atlassian Marketplace. Philipp has worked for a long time as the consultant and manager. Today, he is board member of a midsized company with 270 employees. Over these years he has got great experience in communication with business partners and establishment of new contacts when doing business.

Several months ago Philipp decided to bring his experience to real life in the form of several add-on for Atlassian Confluence. We already published the case study about one of the completed add-ons bundled within CRM Suite.

His choice was not accidental, as his expertise and experience were closely connected to Confluence and he wanted to continue using it. Additionally, there were dozens of contacts on his own Confluence where he wanted to keep them further.

Continue reading “Case Study: Frontend Mentioning for Confluence”

Case Study: Brand-New Theme for Atlassian Confluence

September 6, 2016
#Case Study#News#Confluence
1 min

About Customer

In the late year of 2012 started our cooperation with one Australian company specializing in creation and provision of complex Сloud-based solutions. Data Solutions Group is an IT company with the headquarters in Melbourne, Australia.

Their customer-oriented approach allows them to architect cloud-based infrastructure and re-innovate the existing solutions with the industry-leading technologies. Extensive expertise in Cloud technologies and the status of AWS Advanced Consulting Partner allows them to supply customers with the high-speed, flexible, scalable and reliable Cloud ecosystems.

The necessity to execute only the proven processes and use the situation-applicable methods in Atlassian Confluence made them contact us and add significant updates into their user experience. Confluence was chosen as the tool for easy and convenient team collaboration and quick communication and interaction with their customers. As of that moment, there were some missing features in Confluence that the customer wanted us as Atlassian experts to add.

Continue reading “Case Study: Brand-New Theme for Atlassian Confluence”

Case Study: How M20 Technology uses Confluence for customer and partner relationship management (CRM & PRM)

August 3, 2016
#Confluence#Case Study
12 min

About M20 Technology

M20 Technology, an Atlassian Expert Partner in New York City, helps companies work and collaborate more effectively through the use of Atlassian tools.

Atlassian Confluence is the knowledge base and team collaboration tool of choice for M20 Technology. Over the years they’ve gathered a great load of Confluence best practices for various cases. One of them is managing customer and partner relationships in Confluence.

How M20 built a CRM and PRM in Confluence

As a fast-growing business, M20 recognized the need for customer and partner relationship management (CRM & PRM). They needed an overview of their customers, prospects and partners to help build strong and sustainable relationships with them. For most organizations, such visibility is essential for continued success and growth of a business.

As a business that specializes in building solutions in Confluence, the natural solution was to build it there and here is what it looks like today:

m20 1

This post covers a simplified solution of what M20 Technology uses today. This version makes it  easier to get started and create a basic framework you can customize and build upon. If you are interested in learning how to build a more comprehensive solution, check out this webinar hosted by ServiceRocket and M20 Technology.

To set up such a system in Confluence, M20 Technology extended their wiki with 4 add-ons:

  • Google Apps Connector by M20 Technology – to connect Confluence with a company’s Google Apps account to retrieve contacts details
  • Reporting and Scaffolding by ServiceRocket – for building a table with contacts of customers and partners on a Confluence page
  • Table Filter and Charts for Confluence by StiltSoft – to dynamically filter the contacts table, e.g. search for a specific contact, find all contacts of a certain type (customer, prospect, or partner) or within a given location, hide columns irrelevant for a current session

It allowed them to create a table with contacts similar to the one below:

m20 2

This example contacts table includes:

  • 6 columns that are automatically populated with data from a linked Google Apps account: Name, Company, Email, City, State, Phone
  • the Type column, which has a predefined list of options a maintainer of a contacts table needs to manually choose from (customer, prospect, partner)
  • the Notes column, where you can enter any additional contact related information

It’s up to you to decide what columns to use in your own contacts table. You can tune it as you wish by adding new columns (e.g. contact status, job title, LinkedIn profile, lead source) and deleting those you don’t need.

Setting up a contacts table

Let’s see how to configure this contacts table.

To get started:

1. Install the Google Apps ConnectorReportingScaffolding, and Table Filter and Charts for Confluence add-ons.

2. Set up a Google Service account and authorize it in Confluence. Configure Google Apps Connector (see the Administrator Guide for details). If you don’t have a Google Apps account, you can skip this step and proceed by creating a dynamic table. Though you’d need to fill out your table manually adding one row at a time.

Then create a Confluence page for your contacts table and set up a structure of macros on it as described below. It requires some work, but it’s initial configuration that needs to be done only once.

While editing a page, insert a Report Table macro. Inside its body, add a Google Contact Reporter macro. In reporter, specify whether to list contacts from all Google Apps accounts linked to Confluence or only from some of them.

m20 3

Below the Google Contact Reporter macro, you need to add 8 ‘Report Column’ macros:

1. Title the first Report Column Name. Embed a ‘Report Info’ in it. Set the ‘Report Info’ key to ‘report:item’ and check the ‘Link To Item’ box. It will display the contact’s name and link to the contact’s profile page.

m20 4
2. The title for the second one is Company. Check the ‘Injected’ box for it. Insert a ‘Report Info’ inside its macro body with the key ‘contact:company’.

3. Next four Report Columns are also injected ones. Meaning you need to check the ‘Injected’ box for them. But they don’t require ‘Report Info’ macros. Insert the following keys in their macro bodies instead:

  • %contact:email% for the Email Report Column (to output the contact’s email address)
  • %contact:work address > address:city%  for the City Report Column (to extract the city property of the contact’s work address)
  • %contact:work address > address:state% for the State Report Column (to display the state of the contact’s work address)
  • %contact:phone% for the Phone Report Column (to render the contact’s phone number)

4. The remaining Report Columns are Type and Notes. Both of them are also injected:

  • Inside the Type Report Column insert a ‘List Data’ macro. Specify a field name for it and choose ‘Select’ as a type option. Then embed 3 ‘List Option’ macros in your ‘List Data’ with values ‘Customer’, ‘Prospect’ and ‘Partner’. This combination of macros will create a drop-down list with contact type options for you to select from
  • And the last Report Column is Notes. Add a ‘Text Data’ macro in its body. Provide a unique field name and select ‘line’ as the type of field. It will display a text field in each contact record for you to type in your notes when working with a report.

Now the configuration of your contacts table is done. It’s time to add filtration to your report. To do that, insert a Table Filter macro on the very top of your page and move the ‘Report Table’ macro with all those macros embedded in it inside Table Filter.

You can set up your filters right here while editing a page or later when viewing your table. Let’s first save the page, see our contacts, and then get back to filtration.

Ta-dah. We’ve got a table with all our Google Apps account contact details right in Confluence.

m20 6

Initially Type and Notes columns are empty. To work with them, click the ‘Edit Contents’ button on the page. You’ll have your table displayed in a window, where you can select a contact type in a drop-down menu and enter text in the ‘Notes’ field.

m20 7

Filtering and finding contacts

Your contact database is ready for you to work with. There is a variety of filters that will help you search, filter and analyze your massive contacts report. In this example we’ll use 4 of them:

  • Global filter to search in all columns of a table
  • ‘Company’ free text filter for search by Company name
  • ‘Type’ drop-down filter to filter by contact type, e.g. to see only prospects
  • Hide columns filter to select what columns are not important for your current goals and should be hidden

You can add filters and make changes in your filtration panel right in the View mode.

m20 8

And have your report dynamically updated when you apply filters.

m20 9

Moreover, you can create pivot tables and illustrative charts to get a summary of your contact table and analyze your contact list.

It’s incredibly convenient to manage your contacts in the platform where your collaboration happens. Hoping this detailed step-by-step guide makes it easy for you to set up CRM and PRM in your Confluence. And another amazing thing is that there are so many other ways your teams can benefit from add-ons used in this solution. So go ahead and try it!

Start your free trial of add-ons for Confluence used in this solution today:

Visualizing Jira Data in Confluence: Round 2

June 2, 2016
#Reporting#Analytics#Integration#How To#Confluence#Jira
11 min

Some time has passed since the publication of our first post about the way to visualize Jira data in Atlassian Confluence with Table Filter and Charts add-on. The development of the add-on has not stopped, so since the previous blog post, it has received new features that will allow you to more efficiently work with table data.

In this article, we will show you how you can apply the newly added feature – two-dimensional pivot tables – for creating reports on Jira data in Confluence.

Showing Jira data in Confluence

To output data in Confluence from Jira, you need to configure an application link.

When complete all you need to do is to create a page and insert the Jira macro on it. Within the Jira Issue macro, you can either insert the appropriate JQL query to fetch issues from Jira instance. Otherwise, you can use the pre-defined filters and enter the filter name into the corresponding field. You can also define the additional information showed for issues in the table.

confluence_jira_issues_macro_configurationAs a result, you will get a table with Jira issues when you save the page. But if you decide to filter these issues in Confluence, you will find a problem with it. Yes, you are right. There are no tools in Confluence for data filtration.

Filtration, Pivot Tables and Charts in one tool

So what you can do with the list of your Jira issues? Of course, you can update the JQL query, add new parameters, limit the date ranges or enumerate assignees, and so on.

But is it possible to do this without performing any manipulations with the initial table with issues? Yes, and you can do this with Table Filter and Charts add-on. What capabilities does this add-on give you?

The add-on bundles a set of the three macros:

  • Table Filter macro allows you to add dropdown, free text, date range, number range, and icon filters. So you will be always able to filter data of any type in Confluence.
  • Pivot Table macro allows you to summarize your table and aggregate it against specific values.
  • Chart from Table macro allows you to visualize your table data with the set of available charts and graphs.

All these macros allow you to quickly change their settings while viewing the page and save them in the macro bodies. Data is updated automatically once you update the settings or the data source returns updated data.

So what should you do? Just insert your table or the macro outputting table data into one or multiple macros of Table Filter and Charts add-on. And you’re done.

confluence_table_filter_pivot_table_chart_from_table_macros

Getting Insights into Your Jira Data

So let’s save the page and see what we can do with Jira issues.

We have created the application link to jira.atlassian.com and we want to see the list of issues that have been created since the beginning of the year and their breakdown by component and resolution status. So we use the following JQL query to get the raw list of Jira issues:


project = "JIRA Software (including JIRA Agile)" AND createdDate > startOfYear()

 

Our list includes 477 issues that relate to Jira Software project.

So our combination of macros generates the pivot table, that you can further filter with the pane. We decided to limit the issues created only in the first quarter of 2016.

confluence_pivot_table_jira_issuesAggregation is performed against project components and resolution status. You can quickly switch aggregation in your two-dimensional pivot table against any other parameter.

The Chart from Table macro allows you to visualize the table with aggregated values with the help of the stacked bar chart.

confluence_generated_chart_from_tableThis macro allows you to select the table columns for chart generation. You can also disable particular parameters from showing in the chart by clicking the corresponding values in the legend. You can always quickly change the data series to another one. You can view the results and try to modify its parameters here.

For example, we want to see the distribution of issues by assignee and issue status, and exclude all unassigned issues and see the amount of completed work by particular employees.

confluence_pivot_table_with_jira_issuesWe choose the column chart to visualize the distribution of issues in the breakdown by assignee and issue status. You can try this case here.

confluence_chart_visualization_jira_issuesAnd the last case, that we are interested in the number of issues aggregated against status and resolution with the number of watchers greater than five.

confluence_jira_issues_chart_filtration_pivot_tableSo we add the number range filter for the Watchers column and set here ‘5’ as the minimal number of watchers for the issues to include. The pivot table and the column chart showing the distribution of issues are generated automatically.

Benefits

Table Filter and Charts app allows you to add more interactivity to your work. Now you can forget for the continuous page edits, just place the Jira macro within the bundled macros and manipulate data the way you want it. This add-on can become a real alternative to Jira Charts macro, or for eazyBI Reports and Charts and Arsenale Dataplane Reports add-ons. Explore your issue data from Jira on Confluence pages and share it with your colleagues with much ease.