Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How do you best organize iOS, Android, WebApp, Teams, Backend development of the same app in Jira?

Hi All,

I have a common problem most of the Jira users/Product team are facing 

I have a team of 22 people

1 Designer

6 QA

3 APi Developer

3 iOS Developer

3 Android developer Developer

2 Webapp & teams Developer

3 Data Science Developer

1 Project Manager


All the members are working on 1 project in agile methodology

I have used different plans to manage this project every other plan has its limitations


Finally, I have reached to conclusion it's not efficient but it works. Let me know if we can improve or tweak the plan to achieve best of Jira.

I have created separate projects for each department.

So I have, Android, iOS, Api, Webapp, Teams, DataScience, QA

Each department has got it's own QA member associated with it

Any issues that QA team is not sure of will be created on QA board & after discussion will be moved to respective department jira board

We have Created one PM Board/Project, which has all the tickets (by tickets I mean BRD/FSD/PRD)that needs to be completed in the upcoming sprint.

On this tickets, after reviewing them we assign tags/labels (Like Android, iOS, teams, webapp) this indicates that we need to create tickets in all this jira project/boards which are then linked back to PM tickets.

All discussion/decisions of tickets are mentioned on the PM tickets, Based on the tickets details on PM project/board QA team prepares the Use-cases/test cases which has to run by developer once development is completed. 


We are not using Epic/stories for our project but recently, we feel we can do better planning in Jira.

Please assist here

1 answer

I am working on the same nature of  company with similar product and team sizes. in order to keep track of what needs to happen, what's happening and what has happened, my Product Owner and I work closely.

1. My Product Manager manages the backlog and provides priority for the team to work on.

2. My teams check their respective boards/dashboards/assignments. Some members are shared over boards

3. I create all the filters, labels, workflow automation, ticket overflow, conduct scrum rituals

Though it is not possible to keep a detailed watch on each activities that team does. But I try my best to assign tickets to the team members, get the commitment deadline and check if things are done on time.

Yes Always use EPIC, coordinate with your PO, get the product roadmap, discuss on it, negotiate story priority with PO by discussing tickets with your teams, conduct grooming for next sprint's items. This really helps.

Time management and task breakdown is the tough part though.

thanks alot this definitely helps

Let me incorporate the epics in my scenario, will share my feedback

Like Sanjog Sigdel likes this

Awesome. Hope this helps.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events