My team utilizes Jira for project management, housing all initiatives within a central project. Project plans are subsequently developed for these initiatives. Collaboration with other teams often involves them creating related tasks in their respective Jira projects. While I can link these tasks via issue linking, a critical limitation arises: I cannot establish dependencies between these linked tasks and my primary initiative's tasks, nor do they appear on my main project plan. I seek a solution to this challenge. Is it feasible to incorporate these external tasks as dependencies and visualize them within my project plan? Furthermore, what are established best practices for cross-team collaboration within Jira when using one project plan as the central hub for an initiative?
Hi Ana - Welcome to the Atlassian Community!
You probably want to base your Plan on a JQL Query and not a project or board.
You might want to check the hierarchy setting? If you are using initiative issue type, I think the next level you can put is Epic issue type, then story issue type, before sub-tasks.
You might want to check the Plan feature of JIRA premium where you can configure specific views on your specific issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.