Hello,
Need your help in a matter,
We've been using Jira for the past 5 years, managing the dev lifecycle of our 5 mobile applications, each one of them using a different project and structure ( depending on the size of the team and our demands for that project).
Now we decided to create 2 more apps, that share the same code base ( with different skins and some different logic ) in addition to those we already have. The dev product and QA teams don't want to duplicate all the issues and features or bugs, for each project, because most of the issues/features /bugs will be on both of the apps.
The question is, how to manage this in Jira. For example, when we open a new bug which is applicable to both of the apps, but it was fixed and closed only in one of them, how can it be done?
Because the apps will not be launched and released at the same time ( could be months apart), we want to make sure to go over all the features /bugs/ issues per app.
Hi Roman,
I'm a Product Manager in the Jira Mobile team. Do you want to chat sometime? I'm keen to understand mobile development workflows and see how we can support you better here.
Hoping you can give more of a deep dive on how your team works & what's happening (if this is still a problem or you have workarounds) and we can share what happens on the Atlassian side. We could learn from you and you can also learn from what we do.
Please shoot me an email at rmagpantay@atlassian.com if you're interested.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.