Hey everyone, I’m working on an app that’s available for both Android and iOS. Right now, I’ve got separate JIRA projects for each platform. But I’m finding it a bit tedious to handle user stories.
Currently, I have to create duplicate stories or use linking to manage features across both platforms. It’s not ideal and takes up extra time.
I’m wondering if there’s a way to create a single user story in Greenhopper that can be assigned to both Android and iOS projects at once. Has anyone figured out a good way to do this? Or maybe there’s a better approach I haven’t thought of yet?
Any tips or tricks would be really helpful. Thanks in advance for your input!
I’ve faced similar challenges managing cross-platform projects in JIRA. One approach that worked well for us was creating a separate ‘Core Features’ project alongside our platform-specific ones. We’d write platform-agnostic user stories there, then create sub-tasks for Android and iOS implementations.
This setup allowed us to track overall feature progress while still maintaining granular control over platform-specific work. We used JIRA’s ‘relates to’ links to connect everything.
For reporting, we set up custom dashboards that aggregated data across all projects. This gave stakeholders a clear view of feature parity and development status.
It took some initial setup, but it significantly reduced duplication and improved our cross-platform coordination. Might be worth exploring if your current workflow isn’t cutting it.
hey, have u tried using epics in JIRA? we do this at my company - create an epic for each major feature, then make stories for android and ios under it. helps keep everything organized and you can easily see progress across platforms. might be worth a shot!
In my experience, a practical solution is to utilize JIRA’s ‘Components’ feature. Create a single project for your app and set up components for ‘Android’, ‘iOS’, and ‘Cross-Platform’. This allows you to categorize issues effectively without duplicating stories.
When creating a user story, assign it to the ‘Cross-Platform’ component. Then, use sub-tasks for platform-specific implementation details, assigning these to the respective Android or iOS components. This approach maintains a unified view of features while allowing for platform-specific tracking.
Additionally, leverage JIRA’s custom fields to indicate platform relevance or status. This enables powerful filtering and reporting capabilities, giving you a clear overview of feature parity across platforms.
This method has streamlined our cross-platform development process significantly, reducing redundancy and improving overall project management efficiency.