Time flies and we are in 2021 already. We crunched our sales numbers for Atlassian Marketplace Apps licenses to identify the developing trends.
This year, we are sharing this list as we feel it may be useful to fellow Atlassian users looking to extract more value from Jira/Confluence/Bitbucket.
From our perspective, Marketplace apps play a significant role for established instances by
- enabling automation to improve productivity, speed or security
- adding features to provide additional capabilities like Business Analytics, Test Automation, etc
- organising information to provide insight and facilitate collaboration
How is the ranking done?
The ranking is based on the number of licenses (Server/DC/Cloud) we sold for each app in 2020.
We felt this will be a better measure of the popularity of the app.
In event of a tie, we go by the licensed users count, followed by the total sales for the app.
Akeles Top 10 List
We are pleased to share our list for 2020 voted by the end users in Singapore. While our list may not reflect their actual popularity in Atlassian Marketplace, it is an affirmation in the usefulness of the apps.
Congratulations to the winners.
Top 10 Jira Apps for 2020
S/N App Name Publisher 01 ScriptRunner for Jira Adaptavist 02 JSU Automation Suite for Jira Workflows Beecom 03 Advanced Roadmaps (formerly Portfolio) Atlassian 04 eazyBI Reports and Charts for Jira eazyBI 05 Extension for Jira Service Management Deviniti 06 Jira Workflow Toolbox Decadis AG 07 Zephyr for Jira – Test Management SmartBear 08 Jira Misc Workflow Extensions (JMWE) Innovalog 09 Dynamic Forms for Jira Deviniti 10 BigPicture – Project Management & PPM SoftwarePlant
Top 10 Confluence Apps for 2020
S/N App Name Publisher 01 Team Calendars for Confluence Atlassian 02 Gliffy Diagrams for Confluence Gliffy 03 draw.io Diagrams for Confluence //SEIBERT/MEDIA – Draw.io 04 Comala Document Management Comalatech 05 Table Filter and Charts for Confluence Stiltsoft 06 Refined for Confluence | Sites & Themes Refined 07 Excel for Confluence Bob Swift Atlassian Apps 08 SAML Single Sign On SAML SSO Confluence resolution Reichert Network Solutions GmbH 09 ScriptRunner for Confluence Adaptavist 10 Balsamiq Wireframes for Confluence Balsamiq
Top 10 Bitbucket Apps for 2020
S/N App Name Publisher 1 ScriptRunner for Bitbucket Adaptavist 2 Webhook to Jenkins for Bitbucket Mohami 3 Awesome Graphs for Bitbucket Stiltsoft 4 SAML Single Sign On (SAML SSO) Bitbucket resolution Reichert Network Solutions GmbH 5 Workzone: PullRequest Workflow Izymes Pty Ltd 6 External Hooks by Reconquest Reconquest 7 Jira Hooks for Bitbucket DevOpsSystems Mueller 8 Sonar for Bitbucket Mibex Software GmbH 9 Snippets for Bitbucket Server Mohami 10 Microsoft Teams Connector for Bitbucket Globo Solutions
Share this post
We have been spent a lot of time explaining to customers the differences between JIRA Core, JIRA Software and JIRA ServiceDesk. Think this infographic summarises them well.
For those who wants to check out the screenshots and links, it is available at http://www.akeles.com/what-are-the-differences-between-jira-software-jira-service-desk-and-jira-core/
Atlassian’s Five Secrets of JIRA Performance at Scale webinar shared some useful insights on scaling JIRA performance.
Here is a pictorial summary will be useful for those who missed the video.
1) JIRA 6.4 is 30% faster than JIRA 6.3
2) Custom fields have the most influence on the speed especially on creating issues
3) The number of users does not have much impact on the speed
For details, you can check out the video below or the detailed report at https://confluence.atlassian.com/display/ENTERPRISE/Scaling+JIRA
Share this post
We were curious on its performance and did some testing on it.
We did the setup with
- RHEL 6 64-bit
- Atlassian JIRA 6.1.2
- Oracle JDK 1.7.0_45
- Apache Tomcat 7.0.29
- MySQL Database Server 5.1.69
The specs for the virtual machine
- 6 GB of disk space
- 590 MB of ram
- Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
The setup was completed successfully and we were able to create issues within JIRA. However, the performance seemed to be quite bursty as compared to our typical use. Sometimes an action is almost instantaneous, sometimes, a log in can take longer than 5 seconds.
In the end, we recommended him to consider upgrading the server specs or to take a look at Atlassian OnDemand. The cost of ownership will be lower with automatic version upgrades and data backups.
For a comparison on the differences between onDemand and self hosted, you can refer to our infographic.
Share this post
Recently, Atlassian shared the details on how they are doing agile requirements documention with Confluence.
It also included a well summarized list of the benefits below.
1. One page, one source, one problem
Keeping it simple. The requirements page becomes the “landing page” for everything related to the set of problems within a particular epic. Having something that is the central go-to location saves your team members time in accessing this information and gives them a concise view.
2. A page enables you to be agile
One of the awesome things about using a simple page to collaborate on verses a dedicated requirements management tool is that you can be agile about your documentation! You don’t have to follow a format every time – do what you need, when you need it and be agile about it. In fact, I encourage you to customise the Requirements Blueprint as you learn what works for your team so you can model your processes easily. Chop and change as required.
3. Dive in for context and detail
We often forget how powerful a simple link can be. We embed a lot of links within our requirements landing page. It helps abstract out the complexity and progressively disclose the information as it is needed to the reader. Linking detailed resources my included such things as:
- Customer interviews for background, validation or further context for the feature
- Pages or blogs where similar ideas were proposed
- Previous discussion or technical documentation and diagrams
- Videos of product demos or other related content from external sources
4. Living Stories: Stay updated, track and report on progress
I see a lot of customers do this as well. Once the stories have been roughly thought out – we often use the JIRA integration features in Confluence to link the two. From the page you can easily create your backlog stories. These are automatically embedded with two-way syncing from JIRA. So you instantly get progress reports of how the story is tracking with your dev team, right from your requirements landing page. Learn more.
5. Use your collective team and organisational wisdom
Especially if you are in a large organisation – documenting requirements Confluence makes it easy for other people in different teams to contribute and make suggestions. In the Confluence team, I’ve been amazed at the amount of times someone else from another team jumps into the conversation with a comment providing great feedback, suggestions, or lessons learnt from similar projects. It really does help a large organisation feel like a small team.
The most important aspect of all this is getting everyone involved. Never write a requirements document by yourself you should always have a developer with you and write it together. Share the page with the team and get feedback. Comment, ask questions, encourage others to contribute with thoughts and ideas. This is also a huge asset for a distributed team.
As for the details on how to do it, you can check out the full blog post at http://blogs.atlassian.com/2013/07/agile-requirements-documentation-a-guide
Share this post
JIRA is used by many organisations as a Helpdesk system to keep track of their user queries and requests. Over time, it becomes a valuable Knowledge Base. These solved cases will have details on:
- how to replicate the error,
- what was the root cause and
- the desired solution
By opening up the Knowledge Base, it improves productivity by enabling end users to search for the solution first. If it is available, the end user will get his/her issues fixed and the Helpdesk team can handle difficult cases.
For organisations already have this arrangement, it can be further enhanced by tapping onto Confluence.
When tackling FAQs that require a detailed write-up, a new page can be created in Confluence via a standard template. As long as the JIRA issue is mentioned in the Confluence page (see red arrow in diagram below)
a corresponding link will be created in JIRA (see red arrow below)
Users can click on the link to Confluence to read the detailed solution.
The benefits of using Confluence are:
- rich content can be included (e.g. videos, screenshots, diagrams)
- content can be easily organised in user-friendly layout
- easy to search as FAQs can be organised by topics
- easy to find the solution in a page instead of digging long list of comments (in JIRA)
- protects sensitive information from public viewing
As a user, do you prefer the red pill or the blue pill?
By investing a small effort in Confluence, it will reduce a big effort in JIRA subsequently.
You can start with a Doc Sprint to jumpstart your Knowledge Base with your own FAQs.
Share this post
We have been asked many times on the differences between OnDemand hosting versus hosting the Atlassian apps within the premises.
Here’s a chart we did that lists down the various factors for consideration together with a rating for each option.
Share this post
A lot of people has the misconception that JIRA is used purely as a Bug Tracker. In fact, it can be used for many other purposes due to the key features (such as searching, dashboards, email notifications, workflows, permissions, issue types) provided by an Issue Tracker.
Whenever there is an item required (e.g. printer cartridges) or wished (e.g. OSIM uDivine), the person will create a new Wish in our Wishing Well project in JIRA.
The wish will be reviewed and fulfilled depending on the need, cost, urgency and usefulness. Periodically, we will review outstanding wishes as part of our Office Improvement Project.
The good thing about using JIRA is that all wishes remains tracked so that we don’t miss out any of them. Wishers can also find out on the status of their wishes by logging into JIRA. And now, we welcome Well-wishers to come in to grant our wish for an Osim uDivine.
Share this post
A picture tells a thousand words on why JIRA is used by nearly 20,000 teams, spanning 115 countries around the globe. The tool that makes a difference.
For more details, you can refer to this blog post – Make Growth Easy: Why People Choose JIRA 6
Share this post