Best Practices for cross-project timelines

[Shae Theaker]

Hello friends, 

I want to know if the community has settled on a best practice for timeline / view of tickets across multiple projects. My org is just getting going in Jira and wants to set it up right. Here is our use case: 

We run multiple projects that align to fulfillment teams. 

Software dev has a project
Marketing has a project 
User Experience has a project 

Efforts often involve collaboration between these teams and therefore ends up in sharing tickets. I've thought of a couple different set ups but haven't found one that fits right yet. 
Here's what I've tried so far: 

1. Story from project X linked to Epic in project Y
   1. pros - viewable in plans mode 
   2. cons - lots of maintenance to maintain the query (OR parent in (epic-1, epic-2 etc.) - requires updating query every time an epic is added 
2. Attach a label to project X stories that shows they involve project Y 
   1. pros - low maintenance query to bring this in to plans mode 
   2. cons - must be diligent with labels or tickets will get lost 
3. Use paired tickets - create a story in project X and link to story in project Y
   1. pros - no query needed 
   2. cons - requires considerable collaboration to pair the tickets and requires opening the ticket to view the status of the paired ticket 

How have y'all set this up in your orgs? 
Has anyone found a better way? 

[Humashankar VJ]

Hi @Shae Theaker 

To learn more refer to the article Jira Timeline: A Comprehensive Guide to Project Timelines

which provides a comprehensive guide on managing project timelines in Jira, covering various aspects that align with your query about best practices for cross-project timelines

1. Understanding Project Timelines
2. Benefits of Jira Project Timelines
3. Key Features
4. Customizing Timelines
5. Best Practices
6. Tools and Add-ons

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards