Hi there, we are new to JIRA and trying to figure out how we should configure it. We have different stacks in our project, like iOS, Android, Backend, Web. Are these supposed to be setup as separate projects/boards in JIRA, or should stories across these stacks be managed under the same JIRA project / board?
If they have to be managed in separate boards, is it possible to have a unified view across all boards, to get a holistic view of how related issues progress? For example, can we include issues from multiple boards into the same sprint or Kanban, and track them in a holistic manner?
And how do we manage stories that are identical? For example, for the iOS and Android stacks the stories will be identical (whether they are in the same or separate boards), but different people will be working on them and there will be timing differences at some point (for example iOS is done, but Android overruns the sprint). Is there a story clone function, or do we have to create them manually twice?
We ended up splitting our Stack into JIRA "Components", which also seems to be the intended way to do it (although not very clear from the documentation). So we have a component for each of iOS, Droid, Backend, etc.
We also created swimlanes and organized them by component using JQL filters, i.e.:
component = iOS
Finally, when we create an issue, we assign it a component. Now all our issues are grouped by component on our boards and we can see and track them simultaneously.
We are having a similar dilemma on this. Does this mean that you created two identical stories with different components (e.g. iOS / Android) or created one story with two components in it? If the later, how did you manage the story separately in the scrum board? Thanks in advance.
Yes. there is a story clone process. However, without an add-on the clone must happen within the same project.
As Joe's answer implies, it all depends on how you want to manage your work
One way would be to use separate stories in the same project for the Android and IOS work. (Create one and clone it for the other.) You could link them together if it's important. to track how they are progressing in parallel. Other thoughts:
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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