nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to best handle mobile projects that include ios and android versions

Rich Byard

So we have mobile projects that are built in android and ios. members that work on android and members that work on ios but for the same application.

How to best manage them, is it separate projects for ios and android?

or one project , need a few suggestions on this

Thanks

Accepted answers

All comments

Ismael Jimoh

Hi @Rich Byard

I would go with components here because not only does this allow you share the same workflow and manage the project easier it avoids data duplicates.

It could be said that it was designed for this purpose if both products processes are the same. Else, you would either go for separate projects when this is not the case.

Andrew_g4chs4

Hi @Rich Byard

Looks like better one project, but we don't know business process.

Components - to separate products https://confluence.atlassian.com/jirasoftwarecloud/organizing-work-with-components-764478279.html

Issue type - to separate if different business process or fields https://confluence.atlassian.com/adminjiracloud/issue-types-844500742.html

Issue security - to hide issues from teams https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html

B.R.

Rich Byard

Hi @Ismael Jimoh , Thanks for the reply.

I looked into the components section, that looks like a solution although how are you suggesting to handle assignees? Say if i add a task and add components for android and ios to it , but i have to assign it to both the android developer as well as the ios developer. When i used component and added android first and then ios, it got assigned to the android dev.

any suggestions would be helpful.

thanks

Rich Byard

Hi @Andrew , Thanks for the reply.

So the process is , we have a backend software to which we are creating app (android and iOS). The teams are different , we have 2 devs for android and 2 devs for ios.

The tasks that we add for android, by default will apply for ios. Current scenario, we have to duplicate the tasks which is not feasible as the projects increase. Bugs are added separately coz they will be platform specific.

any suggestions would be helpful.

thanks

Andrew_g4chs4

Hi @Rich Byard ,

I check on my local server. When created issue with multiple components Jira sort it alphabetical and assignee on first.

I show:

Not mean how you add component. For example if added 'android' then 'aaa' assignee will be 'Yandex' because 'aaa' first. If added 'testC' then 'android' assignee will be 'AndreDvizhok'.

It mean in your case all issues will assignee to 'andreid' team.

B.R.

Rich Byard

Hi @Andrew exactly my point.

But I also want to assign it to a member from the iOS team. How do I do that. The only way I do that is I create another taak that will be assigned to the iOS member. Isn't it?

So needed guidance around this

Ismael Jimoh

Hi @Rich Byard ,

The component allows you to set a default assignee. This person ideally could be the project lead for the mobile platform. When a ticket is created and the component is set to Android/iOS, the appropriate team lead would be added as the assignee.

Now you can then create 2 boards with the filter:

project = <your> and component = iOS

or 

project = <your> and component = android

This means the issues marked with these components would automatically appear in these boards. (For bugs, this would be ideal however for task where you want people to work on once, you have these in a single separate board).

Why 3 boards?

Unless you allow parallel sprints, JIRA only allows one sprint per board. With having separate boards where each team tracks their individual bugs, you are sure that the appropriate people are working on what they need to.

General Board - for all tasks shared by both platforms.
Android Board - for bugs related to Android
iOS Board - for bugs related to iOS

The delegation of tasks can then be handled by the lead of each platform.

I hope this helps you clarify the topic of assigning and feel free to reach out if you have any further questions.

Ismael Jimoh

As seen below, you can specify component lead and in the last drop down, you can set the component lead(platform/team lead) as the default assignee for the said component.

Screenshot 2019-04-30 at 16.32.21.png

Andrew_g4chs4

@Rich Byard ,
"The tasks that we add for android, by default will apply for ios."

It mean two dev teams work on one the same issue in parallel time or today work dev android, tomorrow work dev ios?

In first maybe you need add custom field 'user picker' and call it some like 'iOS developer'? And use "assignee" to keep responsible for android, and "ios dev" for acc. for ios?

In second case just re-assignee.

B.R.

Andrew_g4chs4

Please see my comment above :-)

B.R.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server