After doing an initial import from our existing JIRA tickets, our plan is in place. But when developers add a new story to an epic in Agile, it doesn't seem to appear in Portfolio. Do I need to do a regular import?
It feels like I'm doing something wrong and that Agile and Portfolio would be sharing data so updates in one reflect in the other...
Hi Joe, you need to indeed run an import regularly - there is an option in the import dialog to "Exclude already linked issues", so using the same filter, only the newly created issues will show up in the dialog. In our team, I'm used to running both an import and a "Plan > Update from date" after every sprint/before going into sprint planning to re-baseline the plan with what has been accomplished and get new data in.
We are working on this integration and establishing a more direct link between a plan and one or multiple agile boards, but it is a broader change with several implications. Right now, the benefit of the very explicit import and plan update is transparency in terms of changes to the calculated schedule/roadmap.
Best, Martin, Product Manager for JIRA Portfolio
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG