I'm in a large corporation on a product team (with its own Jira project) that spans multiple channels including online, iOS devices, and Android devices. Each channel has its own development team, which functions completely independently of the others, has its own Jira project, and does development for other product teams as well. Unfortunately, changing any of the above is not an option for the time being.
We're looking for recommendations so that we can:
1. Provide business requirements in a centralized location (e.g., a Jira story) and specify which channels are affected. (We can already do this)
2. Provide development teams access to the issue and add to the relevant information so that they can address it.
3. Track the progress of the issue across the affected channels (which are on separate schedules) from a single location (e.g., task board or report).
I'm happy to provide additional detail as well as how we're currently attempting to do this. Just let me know.
Thanks for helping.
The challenge isn't assigning stories to development teams, but rather how to split a story, assign it to multiple teams (each of whom is working on a different development schedule), and track them individually.
For example, if there's an issue that affects customers on three different platforms, three different teams need to attend to it (worst case scenario). Since these teams are on different Jira projects, do we clone the story several times, creating one for each team (and probably duplicate information in each one) or something else?
The end goal is to be able to provide the teams with what they need while also tracking their individual progress so that we can say, "Issue X will go live on platform 1 on this date, platform 2 on that date, and so on."
I'm not sure how much this helps, but your question reminded me of a JIRA blog i read not long ago. If it doesn't entirely help, maybe it'll provide some inspiration. It came in three parts:
The roof is on FIRE… network outages, broken processes, upset clients and employees. Each day seemed to bring more and more issues. Incidents were communicated via email, messengers (skype or teams) ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events