• List of Banks using Atlassian Cloud

    30 August 2023
    Comments are off for this post

    Banks are well known for their stringent policies on security and compliance. This is because they need to ensure their customers’ data are well protected.

    We scouted the Internet to research which banks are using Atlassian Cloud and compiled the list below.

    BankCountry / RegionProduct(s)Solution PartnerUser Count
    Latin AmericaJiraeCore4,300
    MexicoConfluence, Jira, JSMbit2bit Americas500
    Commonwealth BankAustraliaConfluence, Jira25,000
    EQ BankCanadaConfluence, JiraBlended Perspectives400
    Hanseatic BankGermanyConfluence, JiraJodocus GmbH
    Libra BankRomaniaJiraLife in Codes

    p.s: The list is ordered by the name of the bank, followed by Country/Region

    Hope the info will be useful for financial institutions who are exploring to migrate to Jira Cloud.

    References

    1. Bank from Latin America
      • https://www.e-core.com/na-en/case-study/large-private-bank-merges-multiple-data-rich-jira-instances-across-different-server-types/
    2. Bank from Mexico
      • https://bit2bitamericas.com/en/insights/mexican-bank-migrates-to-atlassian-cloud/
    3. Commonwealth Bank
      • https://www.itnews.com.au/news/cba-is-shifting-to-cloud-versions-of-atlassian-software-596929
      • https://diginomica.com/commonwealth-bank-australia-ensures-regulatory-compliance-jira-and-confluence-devops-ecosystem
      • https://www.atlassian.com/webinars/enterprise-cloud/commonwealth-bank-of-australia-engineering-transformation-at-scale
      • https://www.youtube.com/watch?v=xyD4ixf5fyM
    4. EQ Bank
      • https://www.blendedperspectives.com/about-us/equitable-bank-eq-bank-atlassian-cloud-case-study/
      • https://www.atlassian.com/customers/eqbank
    5. Hanseatic Bank
      • https://www.jodocus.io/en/success-stories/hansaetic-bank
    6. Libra Bank
      • https://lifeincodes.com/product-news/when-agile-meets-banking-the-story-of-libra-bank-romania-transitioning-to-jira-software/

    Share this post

  • Akeles Top 10 Marketplace apps in 2022

    7 February 2023
    Comments are off for this post

    Are you curious which apps other users are buying to extend the capabilities of their Jira, Confluence or Bitbucket?

    This year, we are pleased to share again our updated Top 10 Popular apps with fellow Atlassian users.
    It is a good opportunity to review which useful capabilities to add to your Atlassian suite.

    From our perspective, Marketplace apps play a significant role for successful adoption by

    • enabling automation to improve productivity, speed or security
    • providing 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 bought through us in 2022.
    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 sale value for the app.

    Akeles Top 10 List

    Congratulations to the winners. It is an achievement given there are over 4,300 apps listed in Atlassian Marketplace.

    (more…)

    Share this post

  • Akeles Top 10 Marketplace apps in 2021

    8 February 2022
    Comments are off for this post

    This year, we are continuing the tradition of sharing our Top 10 popular apps for Jira, Confluence and Bitbucket.

    From our perspective, Marketplace apps play a significant role for successful adoption of Atlassian platforms 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

    This year, Atlassian Marketplace reached $2 billion in lifetime sales. This is a huge testimony of the usefulness and popularity of Marketplace apps.

    How is the ranking done?

    The ranking is based on the number of licenses (Server/DC/Cloud) customers bought in 2021.
    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 sale value for the app.

    Akeles Top 10 List

    We are pleased to share our list for 2021 voted by the Atlassian users in Singapore. Although our list may not correspond to the global popularity in Atlassian Marketplace, it is an affirmation in the usefulness of the apps. 

    Congratulations to the winners.

    (more…)

    Share this post

  • Akeles Top 10 Marketplace Apps in 2020

    18 January 2021
    Comments are off for this post

    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/NApp NamePublisher
    01ScriptRunner for JiraAdaptavist
    02JSU Automation Suite for Jira WorkflowsBeecom
    03Advanced Roadmaps (formerly Portfolio)Atlassian
    04eazyBI Reports and Charts for JiraeazyBI
    05Extension for Jira Service ManagementDeviniti
    06Jira Workflow ToolboxDecadis AG
    07Zephyr for Jira – Test ManagementSmartBear
    08Jira Misc Workflow Extensions (JMWE)Innovalog
    09Dynamic Forms for JiraDeviniti
    10BigPicture – Project Management & PPMSoftwarePlant

    Top 10 Confluence Apps for 2020

    S/NApp NamePublisher
    01Team Calendars for Confluence Atlassian
    02Gliffy Diagrams for ConfluenceGliffy
    03draw.io Diagrams for Confluence//SEIBERT/MEDIA – Draw.io
    04Comala Document ManagementComalatech
    05Table Filter and Charts for ConfluenceStiltsoft
    06Refined for Confluence | Sites & ThemesRefined
    07Excel for ConfluenceBob Swift Atlassian Apps
    08SAML Single Sign On SAML SSO Confluenceresolution Reichert Network Solutions GmbH
    09ScriptRunner for ConfluenceAdaptavist
    10Balsamiq Wireframes for ConfluenceBalsamiq

    Top 10 Bitbucket Apps for 2020

    S/NApp NamePublisher
    1ScriptRunner for BitbucketAdaptavist
    2Webhook to Jenkins for BitbucketMohami
    3Awesome Graphs for BitbucketStiltsoft
    4SAML Single Sign On (SAML SSO) Bitbucketresolution Reichert Network Solutions GmbH
    5Workzone: PullRequest WorkflowIzymes Pty Ltd
    6External Hooks by ReconquestReconquest
    7Jira Hooks for BitbucketDevOpsSystems Mueller
    8Sonar for BitbucketMibex Software GmbH
    9Snippets for Bitbucket ServerMohami
    10Microsoft Teams Connector for BitbucketGlobo Solutions

    Share this post

  • An infographic on the differences across various JIRA products

    23 December 2015
    Comments are off for 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.

    JIRA Product Family Infographic

    For those who wants to check out the screenshots and links, it is available at https://www.akeles.com/what-are-the-differences-between-jira-software-jira-service-desk-and-jira-core/

     

    Continue Reading
  • 5 Things to Know for Scaling JIRA Performance

    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

    Response Time - JIRA 6.4 vs JIRA 6.3

    2) Custom fields have the most influence on the speed especially on creating issues

    Custom Fields and Performance

    3) The number of users does not have much impact on the speed

    # of Users on performance

    4) JIRA can support more issues without much degradation in the performance
    # of issues on performance5) Running JIRA on Java 8 is 13% faster than on Java 6

     

    Java 1.8 vs 1.6 response time

    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

  • Why our customers use JIRA

    11 December 2013
    Comments are off for this post

    Share this post

  • A review on hosting JIRA on the free Amazon EC2 Micro Instance

    19 November 2013
    Comments are off for this post

    Recently, we received an inquiry on whether it is possible to run Atlassian JIRA on Amazon EC2 Micro Instance. The free tier allows up to 750 hours of runtime each month.

    Image from Wikimedia Commons

    Image from Wikimedia Commons

    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

  • Benefits of using Wiki for Requirements Documentation

    20 August 2013
    Comments are off for this post

    Recently, Atlassian shared the details on how they are doing agile requirements documention with Confluence.

    Atlassian Tiiks

    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.

    6. Make them dynamic and engaging
    Use diagramming tools like Gliffy or Balsamiq to better communicate the problems to your team or embed external images, videos and dynamic content.

    7. Collaborate!
    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

  • Building a knowledgebase with Confluence and JIRA

    26 July 2013
    Comments are off for 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)

    JIRA mentioned in Confluence

     

    a corresponding link will be created in JIRA (see red arrow below)

    JIRA mentions

    Users can click on the link to Confluence to read the detailed solution.

    The benefits of using Confluence are:

    1. rich content can be included (e.g. videos, screenshots, diagrams)
    2. content can be easily organised in user-friendly layout
    3. easy to search as FAQs can be organised by topics
    4. easy to find the solution in a page instead of digging long list of comments (in JIRA)
    5. protects sensitive information from public viewing

    As a user, do you prefer the red pill or the blue pill?

    Solution in JIRA
    redpill
    Comment in JIRA
    Solution in Confluence
    bluepill
    Confluence knowledge page

    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