I’m working on a mobile application that targets both Android and iOS platforms. Currently, I maintain separate JIRA projects for each platform which creates some workflow challenges.
Right now when I need to track a feature that affects both platforms, I end up creating duplicate tickets or using links between issues. This approach feels clunky and makes it harder to get a unified view of progress.
What I really want is to create one user story in Agile boards that can be associated with both my Android and iOS projects simultaneously. This would help me track cross-platform features more efficiently without the overhead of managing multiple related tickets.
Has anyone found a clean solution for this kind of multi-project story management? I’m open to different approaches or JIRA configurations that might solve this problem.
We used epic-based organization in one project. Created parent epics for cross-platform features, then broke them into platform-specific tasks underneath. You get unified tracking without losing visibility into individual platform work. The trick was custom issue types - ‘Cross-Platform Story’ as the parent, with ‘Android Implementation’ and ‘iOS Implementation’ as subtasks. Progress rolls up automatically, so stakeholders see one view while devs have their platform-specific items. We also set up automation rules to sync fields between related tasks. When a platform task hits testing, it auto-updates a custom field on the parent story. Takes setup upfront but cuts out the manual work of syncing duplicate tickets across separate projects.
Had this exact problem two years ago with a React Native project that still had platform-specific stuff. Instead of wrestling with JIRA’s cross-project features, I just restructured everything into one project and used component labels for Android, iOS, and shared code. Way easier.
Now each story gets tagged with whatever platforms it touches. No more duplicate tickets, and I can actually see how features are progressing across the board. Set up custom fields for platform scope and dashboard filters to slice the work by Android-only, iOS-only, or cross-platform.
Yeah, it took time upfront to migrate tickets and get the team used to the new tagging system. But the workflow got so much cleaner. You can still run separate sprints or boards if your dev teams work independently - having everything in one project just makes reporting and story management way less of a headache.
honestly, just use portfolio for epic linking if you’ve got it. keeps projects separate but gives u the unified view you’re after. set up cross-project epics spanning both android/ios projects and link stories underneath. more overhead than cramming everything into one project, but you keep separation if that matters for your team structure or permissions.