I have multiple scrum boards and one epic kanban board pointed at my program in EA. I notice, in Jira, that the standard issue types are automatically assigned to their Program, PI and sprint via EA (this is so cool!), is there a way to associate Epics to programs and PIs?
I have one epic where this information is populated and I have no idea how it happened :-)
Thanks for reaching out via the Atlassian Community.
There is no automatic way to associate Epics with Programs or Program Increments today like there is with issues that have been scheduled into Sprints on Team Boards.
I know from other Community posts that you have trialed our app Easy Agile Roadmaps. Our goal with Programs, is that we would replicate the same date synchronisation behaviour in Easy Agile Roadmaps into Easy Agile Programs for issues that are scheduled on the Increment Roadmap. This would eventually automatically associate any Epics/Roadmap Issues that have start/end dates that align with the dates of a Program Increment.
Would this be an appropriate way to associate your Epics with Programs/Program Increments moving forward?
Until we bite off that date sync work, you will need to manually drag and drop the Epics from your Kanban Board onto the timeline for your Increment Roadmap.
Thanks Elizabeth, looking forward to hearing your feedback
Product Manager - Easy Agile
Hi @Teagan ,
Thanks for your quick response. I think synching could be helpful as you describe. I was actually wondering about the intended functionality of the fields that are added to Jira upon the installation of EA programs: "Program Increment" and "Program".
The use case might be:
As a Program Manager, I want to filter all epics associated to a specific a program increment so I can visualize PI progress by Epic in a Jira dashboard gadget or confluence page for stakeholder-friendly viewing.
Update: I have since had the opportunity to speak with another helpful EA rep who said that the current functionality of EA programs does not associate these fields to Epics. Additionally, my feature request was recorded :-)
For any future reader of this post: Regarding the unusual behavior I witnessed: full disclosure, my test instance also had another app installed, which may have been conflicting and may explain why I saw it in a single record. The problem has since apparently self-corrected.
Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events