Best Practice for multiple teams with dependencies working toward one goal

[Jordan Smith]

I'm curious to get some thoughts from others on how they would set up Jira to manage this example scenario.

Project: User management portal - xyz enhancements

Teams involved: frontend, backend (apis), salesforce

Example User Story: As a user of the User Management Portal I upload pdf attachments for onboarding that store in Salesforce for my contact.

This story involves work from all 3 teams

• SF: add new fields to contact object
• FE: create upload attachment component
• BE: create api endpoint for uploading attachments

Requirements for Jira Setup

• Each team (SF, Frontend, Backend) all work in their own sprints
  • Each teams ticket/issue needs to be pointed separately
• Each teams tickets/issues all relate to one parent issue
• I need a timeline/dependency view for cross-team work
  • This would help me plan sprints and track progress for the feature

---

What I've Tried

One Project: custom-software-development (this might be too broad)

Multiple Boards: (frontend scrum, backend scrum, sf scrum, timeline board).

custom filter for each board to only include stories for that specific team.

Epic: User management portal - xyz enhancements

Stories.. - these end up being task like issues based on issue hierarchy and the need to place in separate sprints

No use of Tasks and Subtasks right now.

Problems

• My issue hierarchy doesn't allow me to story point subtasks and place them in different sprints. 
• Timeline board doesn't allow me to see dependency lines across issues in timeline view.
• Only each scrum board that has active sprints can see the timeline view with dependencies and sprint placements. 

---

Questions

• What Atlassian features would you all be considering for this?
• Is 'User management portal - xyz enhancements' a project, epic or something else?
  • Related: is 'custom-software-development' project too broad for what I'm trying to accomplish.

[Lucas Modzelewski _Lumo_]

"User management portal - xyz enhancements" - sounds like a project with multiple enhancements, then Epics + Stories should be fine. 

Each new enhancement can be an Epic, and work would be assigned in Stories for each team.

Because of specialized teams (frontend, backend, salesforce) I would most probably use components - to group/filter tasks and maybe assign leaders by default. If the stories would have same names I would also add some prefix to issue names like [F] for tasks for frontend issues. I prefer Prefix over Suffix because long names in some views are trimmed, and its easier to just spot the letter at the beginning or sort alphabetically and have issues grouped effortless.

Versioning - I would use built in Jira versions, those are visible on timelines (if dates are set) and would keep teams focused on delivering on time.

As for user stories, and subtasks - depending on communication, each team would have to state their requirements for story, maybe it could be tracked with subtasks assigned to each component lead, but in some simple cases maybe some checklist would do the job - just to check that it was reviewed by [B] team

---

My set up looks like this: Idea (from JPD) > Epic > New feature / Story, Improvement, Task, Technical Task, Bug, Client Bug, Documentation > Subtask > Checklist 

I like the idea of Improvements - it's something small in already existing feature, it requires less time in planning, because everyone already knows and use this feature, but additional works can greatly improve the UX/UI.

It also helps in filtering things which are good enough for release, if something is an improvement, can be done later without harm to main feature