Jira expert needed to help us decide of project layout
Closed - This job posting has been filled and work has been completed.
We have a mobile app in iOS and Android, and a Java J2EE backend, and all these three code bases form a single product. We are trying to decide how to layout the project in Jira using Agile tools, allowing us to plan out sprint across the three code bases. Right now we have defined a single project in Jira, and use "Components" to mark whether a task is iOS, Android or Backend, but some tasks like new features end up producing three tasks (one tagged to each code base) and this seems cumbersome.
We are looking for someone to disucss with us, and maybe do some Jira configuration, to help us decide on a strategy.
Please, only Jira experts who have good English skills.