Having issue managing multiple projects

[Gerald Toh]

Hi I am trying to set up a project board, it tracks high level project items and also is a place where we can log all new requests. Issue is that I want to find a way to track quaterly roadmap items with the current items. I’m also having issue trying to map it out on a jira dashboard. 

[Lucas Modzelewski _Lumo_]

I used to track qarters with versions (software project), with pattern like Q1.20, Q2.20 etc, it allows to add start/release dates. This was not a developement project rather master plan of things to do. Versions are visible on timeline, but are project specific - so it worked for Epics (eg. Jira X compatibility update - with tasks for each app in their project)

At some point I switched to months for versions, to track in more details when things need to be done, and use components for qarters, but it didn't work, so well - as it required adding version and component, people were forgetting about it all the time.

At the end I was using months as fix versions and it was required field in that project. In Confluence I had a pages for each qarter with listed tasks from versions.

Labels will also work for grouping cross Jira, but won't give you much details about the dates

[Gerald Toh]

Hi that’s a great idea to utilise versions in such a manner I’ll try to set something like this . I created a custom field quarters by Q2 2025, etc but I have a problem with a whole holistic view of all items per quarter it’s challenging 

[Lucas Modzelewski _Lumo_]

Yep, it’s definitely not a simple task – especially when you're dealing with similar (but different) projects and other parallel work.

When you find the perfect solution for your case, don’t forget to share it with the community – I’m sure others will appreciate seeing how you managed it 🙂

Good luck!

Bonus tip: Document it!
When new team members join, you won’t have to explain everything from scratch. It’ll also help PMs, POs, or Scrum Masters follow your process without trying to reinvent the wheel. Be sure to highlight key decision points - I remember how frustrating it was having to justify why something "wouldn’t work" simply because others weren’t aware of the limitations tied to specific components or labels.

Document it - your future self and your team will thank you!

[John Funk]

Hi Gerald - Welcome to the Atlassian Community!

Try setting up your Quarterly items as Epics and see if that solves it for you.