I’m working on a mobile app that’s available for both Android and iOS. Right now, I have separate JIRA projects for each platform. But this setup is causing some headaches.
When I create user stories in Greenhopper, I want them to apply to both projects at once. Currently, I have to clone or link the stories, which is a bit of a pain.
Does anyone know if there’s a better way to handle this? I’m looking for a method that lets me create a single user story and assign it to both the Android and iOS projects simultaneously. Maybe there’s a feature in JIRA I’m missing or a workflow trick that could help?
I’d really appreciate any suggestions or best practices for managing cross-platform user stories more efficiently. Thanks in advance for your help!
Have you considered utilizing a single JIRA project with custom fields for platform-specific details? This approach could streamline your workflow significantly. Create a ‘Platform’ custom field with options for Android, iOS, or Both. When creating user stories, simply select the appropriate platform(s). This method allows for unified tracking while maintaining platform distinction when necessary. It also facilitates easier reporting and cross-platform feature parity analysis. Additionally, you could set up filters or boards based on the platform field to view platform-specific work when needed. This setup has worked well in my experience managing multi-platform projects, reducing duplication and improving overall project clarity.
hey swimminshark, have u tried using labels or components instead of separate projects? u could set up a single project with components for android and ios, then tag stories accordingly. might be easier to manage and track across platforms that way. just a thought!
I’ve faced similar challenges managing cross-platform projects in JIRA. One approach that worked well for us was creating a master project for the app, then using epics to group related features across platforms. We’d create a main user story in the epic, then subtasks for platform-specific implementation details.
This structure allowed us to maintain a holistic view of feature development while still accommodating platform differences. We used custom fields to tag items as Android, iOS, or shared, which helped with filtering and reporting.
Another benefit was improved communication between platform teams, as they could easily see the overall progress and dependencies. It took some initial setup, but it significantly reduced duplication and made our sprints more efficient.
Just remember to clearly define your workflow and train your team on the new structure to ensure everyone’s on the same page.