We are using JIRA Kanban board to manage a product that is shipped to three different mobile app stores. Most of the code base is cross platform, but some features require platform-specific code.
So usual flow of work is:
1. Implement features, fix bugs, etc.
2. Prepare build for Platform 1 and handover to QA. QA verifies issues fixed in step 1
3. Release build to Platform 1 store
4. Prepare build for Platform 2 and handover to QA. QA verifies issues fixed in step 1
5. Release build to Platform 1 store
6. And so on
Now if use Kanban release feature at step 3, QA sees that the list of issues to be verified on step 5 is no more visible on Kanban Board. This may result in QA failing to verify a few of the issues on 2nd platform.
One simple solution is to use the Kanban release button after the builds are release for all platforms, but I feel that this will clutter the board unnecessarily.
Anyone got a better suggestion?
Have you explored using swimlanes to segregated each platform's issues? Assume you don't have swimlanes already configured you can set them up for each platform;
Platform 1 || JQL: platform = platform1 || Issues for platform 1
Platform 2 || JQL: platform = platform2 || Issues for platform 2
Platform 3 || JQL: platform = platform3 || Issues for platform 3
Thanks for your suggestion Marc. As I mentioned most of the issues are common to all platforms and fixed by changes to common cross-platform codebase. The real issue is that all issues are verified by QA team separately on each platform build. So if we use the Kanban "release" feature after 1st platform release, the issues are not yet verified on other platforms reducing the visibility for other platforms
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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