JIRA Roadmap Planning

John DiMaria October 30, 2024

My team is looking to build a larger and more comprehensive product roadmap and ultimately would benefit from using a GANTT chart that connects to other boards within our JIRA environment.

With this in mind we have a front end team, a back end team, a customer success team, a sales and marketing team and a support team that would all need to understand how our product is moving along tied to the technical development as well as the request features that are prioritized for implementation. I have several questions / scenarios that I would need clarification on ASAP pertaining to the best course of action for our use case and desired purpose.

Q. Would epics be the best way to handle larger project goals / tickets that overlap across teams or is it better to handle these overlapping project goals / tickets with labels instead?

1 answer

0 votes
Dick
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 30, 2024

Hi @John DiMaria 

Go for the differentiation in issuetype, not labels. 

Reasoning: there is hierarchy in going from goals to specified solutions to achieve these goals. This hierarchy should be in the relation between your tickets, it allows for a quick progress view and is thus more helpful to the team.

Hope this sets you on your way to greatness

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events