The Jira Mobile Plugin – A Review

As of Jira version 8.3 released this year, Jira can integrate with a mobile app developed by Atlassian. The plugin comes standard in 8.3, but you can view it here: Mobile Plugin for Jira.

In some areas, it shows promise, but we are also finding others where improvement is needed. This article is a brief overview of the free Mobile app for Jira Server and Data Center.

Logging In

To connect your Jira instance, you will need to first download from the Android or iPhone app store. For this blog, I’ll be using my iOS device and connecting it to one of our sandbox instances (running 8.4.2). To connect, add your URL and add your credentials.

Figure 1: Logging In

Accessing Jira Software Projects

Projects and boards were easily accessible when first logging in, allowing you to navigate to your SCRUM or Kanban board quickly. As shown in the figure below, the board was available with drag+drop touch capabilities.

Figure 2: SCRUM Board Example

Opening an issue was simple as well; by tapping on the issue, you were able to open the issue details. All fields, including custom and system fields, were visible in the app.

Figure 3: Opening an Issue

Issue Searching

No JQL necessary – search is based on pre-selected filters and free-text search as shown below.

Figure 4: Free Text Search

Transitioning and Editing Issues

Transitioning and Editing Issues is accomplished by opening and editing the issue’s fields on-the-fly. Note any permissions you have access to on the server will be active in the mobile app as well. To transition an issue, you can click on the transition, and the options in the workflow will be available to you.

Figure 5: Transitioning Issues

Known Limitations

There are some known limitations/workarounds for the mobile app.

  • Currently, it does not support Service Desk (see the figure below)
  • No support for connecting through a VPN (unless you have this set up on your phone)
  • It may have issues connecting to an instance utilizing an SSL certificate (if the certificate is self-signed).

These configurations/workarounds are forthcoming, and beta versions of the app showed promise around the Service Desk and Software implementations. Also – looking for Dashboards? You won’t find any here, unfortunately.

Figure 6: Jira Service Desk Project View

Our Recommendation? Try it!

Check it out and see if it’s the right fit for your team. If you have a more advanced implementation, we recommend reviewing some of the other mobile apps on the Atlassian Marketplace. Have questions? Feel free to drop us a line! Get In Touch

Testing Jira Configurations (and other Atlassian Tools)

Testing Jira Configurations (and other Atlassian Tools)

Testing is often the task in your project that is often left behind, or becomes the recipient of a shortened timeline based on scope creep, time crunch, or whatever the reason. With more organizations relying on the Atlassian Tool Suite (specifically Jira and Confluence) as their core enterprise tool suite, the importance of testing new configurations, add-ons, and custom scripts developed in a widely-used tool suite is more important than ever before. Answering the questions “What broke?” and “What works?” is essential to understanding the impact and risk your new functionality or requirement implementation poses. This blog is not a catch-all, end-all, be-all for your testing woes, but we want you to start thinking through some strategies and best practices when it comes to testing and maintaining your Atlassian Tool Suite. 

How much testing? 

This is generally defined in your governance model, but we recommend setting up a defined and succinct list of functionality you are looking to testing any time major functionality is developed. For instance, if you have a custom script running for only one project, test the core functionality and workflows already configured for that project, along with testing core features inherent with major projects in your instance. 

When should you test?

Test early, test often. Following the implementation of any major configuration, add-on / app, or custom script in your development environment, have a list of core functionality you are testing, major projects you will review, and also a running list of any bugs. To state the obvious – make sure you resolve the bugs before pushing the script into production.  

Some Of Our Recommendations

These recommendations may seem straightforward, conspicuous, and previously alluded to in the paragraphs above, but they’re still very relevant:

  • Have a plan: understand and dedicate the role of tester to a team member (hint: not the developer), when testing will be performed, frequency, and scope of testing. Understand what functional tests you want to perform, and load testing strategies. 
  • Development Environment: Don’t have one? Get one. If you’re on Server or Data Center Atlassian generally allows you to use the same licenses across your development and production environments. Have Cloud? Contact a Partner (like us) and we’ll help you.
  • Test early, test often: Going back to having a plan. Test early, test often, and automate. Review your scripts on a monthly or quarterly basis to ensure scripts detailing core functionality remain relevant.  
  • Use Configuration Manager: easily migrate project configurations between your development and production environment using the Configuration Manager for Jira add-on (for server and data center). 
  • Automation: Automate your load testing and functional testing scripts. Use tools such as Selenium, Gatling, and others to automate your testing scripts and pull out testing reports. 

Interested in improving performance on your Jira or Confluence instance? Talk to us today!