We use Jira to manage a single app which is released on 3 different platforms (iOS, Android and web). The codebase is the same (Flash/Air) and 90% of the tasks apply for all 3 platforms.
We use Agile boards to track the progress of an issue through development and QA. Development is usually done on a single codebase so the task is the same for all 3 platforms. However when it comes to QA, we need to review and release it separately.
Our current solution is just to create a single issue for each task. Then we try to QA on all three platforms at once. However this rarely works nicely as one platform is usually behind the others. It gets messier when it comes to mark the issue as "released". We have got to the point where we don't use the "release" button on the Agile board because it is meaningless.
I would love to know how others solve these problems. Do you have any tips?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG