Ask Me Anything: Jira Cloud apps on iOS and Android

[Steen Andersson]

Edit: This AMA event is now closed. 

March 26, 2020

Hey everyone!

WE'RE LIVE! for this AMA. Ask me anything about our Jira Cloud Mobile apps in iOS & Android.

For those of you who don’t know me, I’m Steen Andersson, the head of Jira Cloud Platform.

We believe that work has changed – the modern global workforce demands more flexibility, communication, and collaboration. We’ve designed the Jira native apps to help you work in your own terms; stay close to your issues, projects and teams; know what to work on right away; move work forward wherever, whenever, on any device.

In the last few months, we’ve shipped new Jira capabilities, a new user-friendly navigation UI, and tons of performance improvements. With more software, IT, and business use-cases as well as reporting features on the horizon, we’re executing on our goal of creating the perfect all-day companion for effective software, IT, and business individuals.

We are not done yet, but we’d love to hear what you think of the apps so far.

Ask me anything about the Jira Cloud Mobile apps:

• How do the mobile apps help me?
• What is the mobile apps team currently working on?
• What’s next on the mobile apps roadmap?

Upvote others' questions and stay tuned as I’ll be answering anything on your mind on March 26. 

[Frank Polscheit]

Using my latest version (download from my server at http://www.polscheit.de/plugins/jira/gantt-chart/gantt-3.1.9-JIRA6_2015-03-04T13-11-05Z.jar and install this JAR-file via "upload" button on JIRA's page "manage add-ons" as system admin.), I have optimized the performance of the Gantt Gadget.

Nevertheless, displaying such large amount of issue (> 200.000 issues) will always be an infrastructure problem: I assume, your database servers will never be fast enough retrieving all that data nor your LAN throughput from the server to your browser, which it may run into memory problems. Within JIRA's dashboard, the solution is to use a suitable filter (e.g. issues not being resolved or closed) in order to reduce the amount off issues. Idea behind the scene: nobody would like to scroll over >200.000 issues as this is not efficient working. Additional to use a suitable JIRA filter, you can specify a time period you are interested in. This can be "from" - "to" in form a absolute dates or even better by using relative dates (e.g. from '-4w' to '12w'). Having specified a time period based on relative dates, you'll get a time period automatically shifted per day. This would retrieve and display the issues belonging to that time period depending on "today" only, like one month in the past until 3 months within the future.

I appreciate your feedback.

Kind regards,
Frank 

[Deleted user]

Hey Frank, We will update in our next window.  The issue I see is that the gadget takes quite some time to load before we can specify a filter.  this is true especially when embedded in Confluence.  I will check how your optimizations affect this and let you know.

[Deleted user]

We've updated to the latest version and set the default JQL to a query that will return 0 rows. We still see the gadget never finishes loading in Confluence yet loads instantly in JIRA.

[Frank Polscheit]

Developing Gantt-Chart version 3.2, I have re-implemented issues' loading and parts of the internal issue container and have reached a performance boost: 1000 issues to be displayed within < 10 sec. using a common hosted virtual environment and within about 2 sec. using my optimized test environment based on server-side SSDs). May be, there's a bug avoiding the disable of the "loading" message in case of empty result set. Please have a look at your browser's console output. Kind regards, Frank

[Deleted user]

Is this what you need for Console output? Confluence gadget with console: http://screencast.com/t/HQUNcA5u6s Compared to the same gadget (same settings) in JIRA: http://screencast.com/t/86o2lsGNK7

[Deleted user]

Hi @Frank Polscheit - Have you had a chance to look at the screencasts above?

[Frank Polscheit]

I am re-engineering the load algorithm to enhance performance, currently. Coming version 3.2 will be optimized to run 20x - 50x times or even faster (depending on your environment: loading e.g. 1000 issues between 2 - 10 sec.) according to my tests at the moment. Kind regards, Frank

[Deleted user]

Thanks. We will keep an eye out for it.