• Color Matters

    Here is a post to commemorate the release of a new feature: Color Scheme Enhancement for Multiple Filters Chart Gadgets version 2.1.0

    1. “What purpose will this color serve?”
    2. “Will this (color) serve it’s purpose effectively?”

    Gif on Steps for a Custom scheme

    When color is used effectively, it brings life to the charts and directs users to focus on details required for effective communication.

    Such as to (1) highlight a particular data, (e.g. Tasks that has yet to be completed)

    (2) encode quantitative values, (e.g. Density of importance corresponds to darker shades)

    and, (3) to group items.

    Colors themselves tell a story, and it’s the responsibility of the designer to make sure the palette used does not create confusion within a data visualization.

    Thus, the palettes used are to have enough variation in hue and brightness.

    Try out the different color palettes available in Multiple Filters Chart Gadget and explore the possibilities with colors.


    Fun Fact:

    Image Retrieved From https://thumbnails-visually.netdna-ssl.com/color-emotion-guide_512d42458efc1_w1500.png

    Available on the Atlassian Marketplace

    Continue Reading
  • 6 Reasons Why You Should Learn JIRA

    6 reasons why you should learn JIRA


    JIRA has become sort of a standard for keeping track of issues. In fact, over 70% of the Fortune 100 companies are using JIRA.

    I just did a search for JIRA on Indeed.com and found 10,947 positions available. The positions that requires JIRA expertise ranges from JIRA administrators, Scrum Masters, QA Analysts, Software Engineers, Project Managers to Service Desk Specialists, etc.


    Today JIRA has 3 different flavors

    • JIRA Core – for business teams to track tasks, approvals, legal reviews, marketing campaigns, etc
    • JIRA Software – for software teams to track bugs, system enhancements with features to support agile development
    • JIRA Service Desk – for helpdesks to track user problems and requests

    It is possible to mix and match the 3 applications to run on a single server and web address. This provides the flexibility for business teams, software teams and helpdesk teams to collaborate on the same platform. 

    Easy-smallEasy to Use

    The UI is intuitive and Atlassian provides very comprehensive user documentation on their Confluence site. You can extend the features from the big set of add-ons from Atlassian Marketplace.


    By using JIRA to track the issues, all the historical changes and discussions are captured in context to the issue. This provides visibility and traceability that makes audits less painful.

    time-saving-smallTime Saving

    Another side effect of using JIRA is that you can save time compiling reports and sending emails. With the reporting gadgets and automation add-ons, you can focus on getting the real work done.


    The server license for 10 users starts from US$10 with 1 year of annual support. If you wish to save the hassle of setting up your own server, you can also use the Cloud edition which goes for $10 per month for up to 10 users.

    JIRA training 2016

    Share this post

  • 8 Secrets How Successful People Get Work Done

    8 secrets successful people get their work done

    Have you always feel frustrated at the end of the week that you have accomplished nothing despite being busy for the entire week?

    I was inspired by Barking up the Wrong Tree to write how using an issue tracker can improve the way of getting work done by incorporating behavioural science theories.

    1. Attention is equal to Time 

    First, you need to be aware that your smartphones and inbox are huge time suckers to your productivity.

    Each new email or a notification is likely to distract you from what you are doing. Mobile notifications is the new evil with a constant flood of notifications from your group chats and apps.

    According to research, it takes an average of 23 minutes and 15 seconds to get back to the task after getting interrupted

    People who do a lot of attention switching, they believe they can focus when they need to, but the reality is they have lost that ability.
    When you give them a task that requires focus, they perform worse than people that don’t spend a lot of time fragmenting their attention.

    Bakadesuyo: How to focus

    Therefore, you might want to check your mails and mobiles after completion of a task. 

    2. Maintaining a list 

    According to research, an average human can only keep track of 7 ± 2 tasks in working memory

    Therefore it is better to use computers to keep track of your tasks. It helps to keep you organised and ensure no tasks get missed.

    3. Setting up a routine 

    Have you ever wondered why people will always remember to log in to check their Facebook or to play their mobile games?
    Well, they all send you notifications periodically to remind you to do so.

    So you can set up a reminder for yourself to check on the tasks that you need to do at the start of the day/week.

    4. Create small wins for yourself 

    The biggest difference between working and studying is there aren’t regular tests to tell you how good you are performing and to let you move to the next level.

    You need to create small wins for yourself to and your team have the feeling of progress.

    People’s inner work lives seemed to lift or drag depending on whether or not their projects moved forward, even by small increments.
    Small wins often had a surprisingly strong positive effect, and small losses a surprisingly strong negative one.

    Bakadesuyo: How to be motivated: 4 new insights from research

    Start having a report to see how many tasks you have accomplished at the end of the week.

    You will not feel nothing is done at the end of every week.

    5. Start to reduce shallow work 

    A mentor once shared with me the concept of “Death by a Thousand Paper Cuts”

    Similarly, small insignificant tasks consume your time and distract you from getting the real work done.

    Shallow work is little stuff like email, meetings, moving information around. Things that are not really using your talents.
    Deep work pushes your current abilities to their limits. It produces high value results and improves your skills.

    Bakadesuyo: How To Stop Being Lazy And Get More Done – 5 Expert Tips

    Instead of spending time to compile reports and filling time sheets, use tools to automate this to free up time to do meaningful work

    6. Learn how to say no 

    Do you know that a common characteristic of successful people is that they know how to say no at the right time.

    By asking your co-workers to log a task in the system for you, it makes them think harder whether it is necessary.

    This either helps you to filter unnecessary tasks or prepare the information for the task upfront.

    It also helps your superior to see your workload and balance the assignment accordingly. 

    7. What gets measured get done 

    Usually most of us work together as a group. Sometimes you need someone to complete a piece of work before you can work on it.

    If the task is passed over to you late, you will have less time to work on it. The worse scenario is that it interrupts you 

    Try to set a due date when assigning out a task and send automated reminders to chase them.

    8. Use the correct tool 

    A major limitation of using the Inbox to keep track of your tasks is that emails are sorted with the latest first.
    It creates a natural tendency to read and react to newer emails than to follow up on the earlier emails.

    Work should be FIFO (First In First Out), not LIFO (Last In First Out).

    If you keep on reacting upon those newer incoming tasks, your older tasks will eventually become urgent and get on top of you.  
    Then you will be pressured to rush finish those late tasks. 

    You might want to use a To-do list tool or issue tracker to manage your tasks.


    You can find more useful tips and related information for the quotes and links referenced in this article below:

    1. http://www.bakadesuyo.com/2015/01/how-to-be-motivated/
    2. http://www.bakadesuyo.com/2015/12/how-to-focus/
    3. http://www.bakadesuyo.com/2014/08/how-to-stop-being-lazy/
    4. http://lifehacker.com/how-long-it-takes-to-get-back-on-track-after-a-distract-1720708353
    5. https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two
    6. http://www.inc.com/jessica-stillman/4-steps-to-say-no-like-the-super-successful.html

    Share this post

  • How we migrated from VertygoSLA to Days Elapsed Traffic Light plugin

    Report on the Traffic Light status of issues using 3D Gadgets

    Why we built Days Elapsed Traffic Light plugin

    We have a customer using VertygoSLA plugin to track the SLA for requests in their JIRA, but VertygoSLA was acquired by Atlassian to be embedded with JIRA Service Desk. There were 3 options available:

    1. To switch to JIRA Service Desk
    2. To find other suitable SLA plugins
    3. To build our own SLA plugin

    We decided to build our own Days Elapsed Traffic Light plugin due to the following considerations:

    • Need to calculate the number of working days. As the business requests can take many days to resolve, displaying 9 days elapsed is less mathematically challenging compared to 72 hours passed
    • Ability to flag out issues that is going to exceed the SLA soon. The yellow traffic light is helpful for alerting users
    • To be able to retain the SLA information from the old requests

    Setting up the Traffic Light custom fields

    The setup for the Traffic Light custom fields is pretty simple with a couple of steps

    1. For every VertygoSLA custom field, we added a corresponding Traffic Light custom field with the same name Added Traffic Light custom field
    2. The working calendars have to be added to define the working days and non working days. In order to cater to departments with different calendars, we introduced the concept of country calendars and organisation calendars. This will alleviate the administrators’ tasks of having to update each calendars individually
      Defining the calendar
    3. The mappings have to be defined to specify the thresholds and conditions for the SLA to be applied
    4. Post functions are added into the workflows to start and stop the Traffic Light Timers
      post functions to start the timers

    Migrating the VertygoSLA data

    The patching was the most time-consuming part as it was done incrementally over different JIRA projects. We built a patcher module that can select the issues to patch.

    1. The patching was done during off-peak hours to avoid disruption to the users
    2. The patcher will read the VertygoSLA information and find out the duration of SLA timer
    3. Using the number of days elapsed, the traffic light colour is determined
    4. The information is then populated into the corresponding Traffic Light custom field
    5. We created dashboards with our Multiple Filters Chart Gadget for the users to verify the resultsDifference in SLA Reports
    6. After verification, the VertygoSLA custom fields were deleted

    Share this post

  • When do you move JIRA Server to JIRA Data Center

    A frequently asked question by JIRA users or those who are evaluating JIRA.

    It is not uncommon that they may be wondering whether they will need to use JIRA Data Center. Thus, we are sharing our experience with JIRA Data Center in this post which hopefully can help to shed some light on it.

    What is JIRA Data Center

    JIRA Data Center is a deployment option designed for high availability and performance at scale
    when hosting JIRA Server in your own premise.

    This is achieved with a cluster of servers to share the workload from incoming requests through the use of a load balancer. Each node is a complete JIRA instance with its own index.

    JIRA Data Center Reference Architecture

    What are the benefits of using
    JIRA Data Center

    • Performance – Faster performance with load being distributed across the various nodes
    • Increased users – A 2-node JIRA Data Center cluster was able to support two times the no. of
      concurrent users with the same response time compared to a single JIRA Server 
    • High Availability – With active-active clustering, users are guaranteed uninterrupted access in
      event of hardware failure as they will be seamlessly redirected to an active node automatically
    • Instant scalability – Additional nodes can be added in real time
    • Disaster Recovery – Option to have another set of hardware on standby

    When you should start looking
    at JIRA Data Center

    The JIRA Server should be sufficient for most users until you encounter one of the scenarios below:

    • your existing JIRA issue count is hitting a million
    • your are growing at 20,000 JIRA issues per month
    • there is a need for high availability or disaster recovery
    • the CPU usage for your JIRA Server is peaking constantly
    • more and more users have started complaining of slowness

    Before upgrading to JIRA Data

    • Have you allocated more resources such as CPU and RAM to the JIRA Server?
    • Have you explored performance tuning?
    • Have you checked if the slowdown is caused by virus scanning? You can use our Attachment
      Checker for JIRA
      add-on to limit virus scanning to file attachments
    • Have you upgraded to the latest version of Java and JIRA? Do you know JIRA 6.4 is 30% faster
      than JIRA 6.3 on average? Check out 5 Things to Know for Scaling JIRA Performance

    What are the considerations

    • License Cost
      • JIRA Software Data Center is an annual term license. Thus renewal is required to continue using it
      • The pricing is based on user tiers and does not have any limit on the number of servers or CPUs

        Annual Price
        Up to 500 users US$12,000
        501 to 1,000 users US$24,000
        Up to 10,000 users US$24,000 for every 1,000 users
        Next 40,000 users US$24,000 for every 5,000 users
        More than 50,000 users US$450,000
      • There is a discount for upgrading from JIRA Software Server to JIRA Software Data Center
      • If you are only setting up a cold-failover server, you can use a free development license without
        additional cost
    • Compatibility
      • The add-ons must be data center compatible
      • If you are moving from JIRA Cloud to JIRA Data Center, this could be tricky
    • Cloud option
      • You need to have your own hosting infrastructure as there is no Data Center option for hosting with JIRA

    Recommended Strategy

    For those who do not need HA setup, we recommend the following strategy

    1. Start with JIRA Software Server
    2. Do performance tuning to stretch the limit of JIRA Software Server
    3. Conduct benchmarking tests to measure the improvement with JIRA Software Data Center
    4. The no. of nodes to allocate will depend on the no. of concurrent users and the usage pattern. The following chart can be a reference on how increasing the no. of nodes increases the no. of requests handled without affecting the time taken

    JIRA Data Center Performance Test

    Useful resources

    Share this post

  • An infographic on the differences across various JIRA products

    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 http://www.akeles.com/what-are-the-differences-between-jira-software-jira-service-desk-and-jira-core/


    Continue Reading
  • How to Deploy Changes to JIRA in a Day


    Recently, we completed a project for a bank. Their original idea was to build a system for tracking but they decide to leverage on JIRA since they were already using it. The requirements can be met by adding a few new JIRA projects and customised plugins.

    However, there was a big challenge to quickly deploy changes on an existing JIRA Production system. The changes had to be replicated across 3 separate environments (DEV, QA and PROD). This meant that the users had to wait a longer time to use the new features.  Luckily, we discovered the Configuration Manager Plugin. It is a JIRA add-on that enables automated deployment of configurations across JIRA instances.

    With this plugin, we managed to replicate the configuration in 1 environment within 1 day instead of a week. We managed to shave 8 days of effort for QA and PROD environments. It eliminated human errors which could not have been avoided if we took the traditional method. There were just too many steps to replicate with zero errors.

    We were very impressed and want to share our experience with fellow JIRA users.

    How we did it

    Due to confidentiality, the steps are listed using the screenshots taken from the plugin author’s page.

    1. The initial configuration in DEV had to be done manually. We cheated! Using our in-house Project Creator plugin, we created hundreds of custom fields from a MS Excel file
    2. After the schemes and workflows were set up, we got ready to create a configuration snapshot for export
    3. The Configuration Manager can only be accessed by a JIRA Admin under the admin console
    4. Select the Add Snapshot button (or Create Snapshot for newer version) 
      view snapshot 
    5. We used System Configuration to capture all the configuration so that we can deploy multiple projects at the same time
      Create a system snapshot
    6. After the snapshot was created, we downloaded the xml file by selecting Download from the gear icon on the right side
    7. The file was copied to the UAT environment to be deployed
    8. Similarly, the JIRA Admin had to log into the admin console to access the Configuration Manager page
    9. To play safe, we did an backup of the UAT environment before applying the changes so that in event of error, we can still restore the UAT environment to the previous setup
    10. Click on the Deploy link on the left sub-menu to access the Deploy Configuration Snapshot page
      deploying the snapshot 
    11. Click on the From Snapshot File button to upload the xml configuration file created from DEV
    12. The snapshot will be added to the list of snapshots available for deployment
    13. Click on the Deploy link under the Actions
    14. The list of configuration changes will be listed. The additions are identified by additionwhereas modifications are identified by modificationAnalyzing the changes
    15. We spent more time verifying the changes identified with the modification changes to ensure they do not affect existing configuration. 
    16. When the changes were confirmed, we proceeded with the automated deployment
    17. Once completed, the changes could be viewed in the Audit logs
      Viewing the changes from the audit log

    Interested users might want to consult the plugin documentation page at https://botronsoft.atlassian.net/wiki/display/CMJ/Configuration+Manager+Documentation for details.

    Feedback for Improvement

    We were very glad such a plugin is in existence. However, there are some limitations or possible improvements

    • The configuration stored using ActiveObjects had to be replicated manually. This is because there is no easy way to differentiate the configuration settings from the issue values
    • The selected role for the Issue Alternative Assignee custom field had to be re-configured after it had been added automatically


    We recommend Configuration Manager Plugin to JIRA Administrators who need to implement many changes across multiple JIRA environments frequently. It’s a time-saver! 

    Share this post

  • 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

  • Win free copies of the newly published JIRA 6.x Administration Cookbook

    Readers would be pleased to know that we have teamed up with Packt Publishing to organize a giveaway of the new JIRA 6.x Administration Cookbook that we have reviewed recently (See Book Review: JIRA 6.x Administration Cookbook).

    Three lucky winners stand a chance to win a digital copy of this book each.

    JIRA 6.x Administrator Cookbook


    How to Enter?

    All you need to do is head on over to the book page and look through the product description of the book and drop a line via the comments below this post to let us know what interests you the most about this book. It’s that simple.

    The first 3 valid respondents will get an e-copy of the Book.


    The contest will close on till 17th Sep 2014. Winners will be contacted by email, so be sure to use your real email address when you comment!

    Share this post

  • How we are using JIRA for Personal Data Protection Act (PDPA)

    The Personal Data Protection Act (PDPA) has come effect from 2nd July 2014

    The PDPA establishes a data protection law that comprises various rules governing the collection, use, disclosure and care of personal data. It recognises both the rights of individuals to protect their personal data, including rights of access and correction, and the needs of organisations to collect, use or disclose personal data for legitimate and reasonable purposes.


    Data Security

    We recently completed an enhancement for Data Request Tracking with JIRA.
    This enhancement tracks all requests and facilitate the approvals that is pertaining to personal data.

    Some of the steps required are:

    • create a new issue type “Data Request”
    • create a new project for Data Request
    • add those fields that you need to track
    • associate the fields to the screens
    • copy the default workflow and change it with the Workflow Designer
    • associate the schemes to the project
    • If you need reports, you can create a dashboard and add some of the built-in gadgets

    By using a centralised application instead of emails to track all the requests, it provides visibility in the handling of all requests and fulfils the audit requirements.

    We thought it was useful and adapted it for ourselves. Hence, if you have previously submitted your personal data to us, you know your data is safe.

    If you are using JIRA, you can start tracking your Data Requests today!

    Share this post