Has Anyone Used Jira to Manage a Mobile App Launch? What Were Your Biggest Wins or Pain Points?

[Arianna Smith]

We’re exploring more efficient ways to manage mobile app projects — from early planning to post-launch support.

I’m curious if anyone here has used Jira (or Trello, Bitbucket, etc.) to manage a mobile app launch or update cycle.

Some things I’d love to learn from your experience:

• Which issue types or custom workflows worked best for your dev/design/support teams?

• How did you track bugs, feedback, and feature requests after launch?

• Did you use any third-party integrations (e.g., Firebase, Slack, app store tools)?

Bonus: Did your Jira setup evolve over time as the app grew in complexity?

Looking forward to hearing your war stories and best practices!

[Benjamin]

HI @Arianna Smith ,

done it for all types of platforms and Operating systems? There isn't a one size fits all. It's going to come down to how your team works and what fields are important. For example, the team may want to know the exact apps version, the Operating System version and the hardware version to reproduce the issue. 

Yes, jira setup will continuously evolve because the team is always adapting to new things that come up either to make thing more efficient. For example, you may find out the work flow needs a new status or remove a status. May find out there not enough information to file a bug where the team can work off that information. 

In all setups, I start simple. I suggest just starting with an Atlassian template and pivot from there. If aiming for perfection and adding all the nuances, you may end up with something very complex that the team may not end up using or worst causing friction to the work at hand. Making jira simple for the team allows the team focus on the work at hand. The nice thing is that Jira is simple to the needs that comes up. 

As for third party, would recommend not adding until later once the team gets settle with the ways of working on Jira. Adding the tools may seem like a great thing to do right away to keep everything connected, but that may add-on overhead of understand how everything working together when the team needs to get that mobile app out. The work and the team is more important. Pay more attention to what the team actually needs and then add/remove things in order to help eliminate/reduce the pain points the team is actually facing. 

All the best!