Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Best Practice: When delivery is attached to multiple ideas

Tere Pile
Contributor
November 18, 2025

Our current process requires 1 idea: 1 or more Delivery items (prefer epic level).  We also allow many epics to 1 idea if it's a larger effort or multiple 'teams' working an item. 

However - the question is Jira allows 'me' to attach more than 1 idea to work item.  So why is it not allowed.  The simple answer is our process related to reporting & visibility.  Inflating effort, value, potentially disconnected timelines. No real 'dependency' view (other than custom field).  Essentially Delivery Status becomes an irrelevant field if I don't 'merge' ideas.  And if I merge, I 'may' lose the timeline tracking I'm trying to show between core development areas. 

I get the pain point for teams; I guess I'm just curious what others do.  

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events