This issue has been addressed as part of new Portfolio live plans, which are now out of labs and the standard way of working with 2.0.

I've requested access as well and it too is pending. Thanks.

Hi Albert,

I requested access to the group a couple of days ago. It is still pending.

Thanks for confirming.

Cheers

Dan

Hello denise1, dan.solo1655815979,

sorry for the late update, we're organizing the communication around the beta release in a LinkedIn group, joining this group will get you the latest updates once available: https://www.linkedin.com/grp/home?gid=7018171

Best regards,
Albert Kavelar | Portfolio for JIRA Development

I second this earlier comment... "I can follow up on this by noting that the conclusion of our evaluation is that the missing sync of epic links is indeed a dealbreaker."

Hi ben.close,

Martin's Summit presentation can be viewed here: http://summit.atlassian.com/videos/featured/portfolio-for-jira

Best regards,
James Russell | Portfolio for JIRA Development

@Martin Suntinger [Atlassian]

We are planning to share more details on the new integration at the Atlassian Summit early November and provide access to beta versions shortly after that.

For those of us not able to make the summit is there any slides/videos we can review with extra details about the progress of Porfolio? Also we're now in December and wondering if you could give an update on the beta ETA.

Hello mr1440877696, cwoods,

we understand the implications for you and that the current JIRA integration options offered by Portfolio are impeding your workflow. As pointed out by Mads, we are currently working on an updated version of Portfolio. We are happy to update this thread as soon as we have definitive information.

Thanks for your understanding,
Kind regards,
Albert Kavelar | JIRA Portfolio Development

I had a conversation with Martin Suntinger a few weeks back, and he did, as hinted in his post above, tell me that Atlassian could not fix or alleviate this (open) issue in the current version of Portfolio, because they have chosen to work on the upcoming beta instead.

The current bugs and deficiencies of Portfolio are hurting the productivity of our startup, and for the time being, we have chosen to stick with Portfolio and wait for the beta. But this inflicts considerable overheads on us every week, so we would like Atlassian to reciprocate with a commitment to us.

I think everyone would appreciate if you could provide a release date of the beta that is supposed to fix all these issues. If you cannot commit to a release date yet, please commit to informing us directly (or in this thread) as soon as such a date exists.

Kind regards,

very interested in te beta. is there an ETA? i couldnt find anything on the allasian website.

Excellent... Thanks Martin. Much appreciated.
Just working through setting up first Portfolio. It's an interesting tool. Hopefully we can use it to improve our processes.
Cheers
Dan

dan.solo1655815979 I'll post infos here once the beta launches. Cheers, Martin

Hi Martin,
Could you please add us to the Beta if possible. We are also after this feature asap.
Cheers
Dan

I actually really appreciate the deliberate manual step, mainly because it allows me to get all my thoughts together on complex planning and dependencies before committing to them. I think after this initial state automatic syncing would be great.

Thank you for the update. I agree that automatically syncing would be better than the manual "Apply updates to projects" step. I am glad to hear that you are working on it. Portfolio looks like it can almost solve some major project management challenges that we have, but the missing epic sync is still a roadblock.

mr1440877696 benjamin.close mikkel.christensen Thanks for voicing your frustration loud and clear, and apologies for failing to post an update on this earlier. I'm the responsible product manager for JIRA Portfolio.

The situation is as follows: We are working on a complete overhaul of the Portfolio integration with JIRA, to address a whole set of problems, such as priority rank not being in sync with JIRA Agile, sprints not being in sync etc, dependencies not reflecting existing issue links, etc. The new type of data integration will implicitly solve the problem described above, however, the complete "Apply updates to projects" step will not exist in its current form, and will be replaced by an option to either auto-commit every change, or manually reviewing and commiting the changes made in Portfolio. Instead of manual issue import, there will be an option to configure dynamic data sources from JIRA. This is a substantial piece of work and we currently focus our time 100% on that. This also means that we don't pick up any improvements to the current integration model, as spending time on that would basically just delay the necessary overhaul and would be lost effort in the long run.

We are planning to share more details on the new integration at the Atlassian Summit early November and provide access to beta versions shortly after that.

Thanks for your understanding, i appreciate this issue has been open for a long time period, but we had to take a step back here to come up with a more solid integration model alltogether.

Martin Suntinger
Principal Product Manager, JIRA Portfolio

I have a meeting with head of support for Portfolio this morning CET and will report back here after our call. Anyone still interested in getting this fixed, please let you voice be heard in the next few hours and days. All it takes to be able to post comments here is a free Atlassian id.

Having bought porfolio and finding this bug after purchase it is certainly disappointing that there's not even a timeline for this fix. Anyone not investigating the 'apply update' results explicitly in the trial will get bitten by this.

My recommendation is not to buy Portfolio before this is fix as it's useless if you want to mange issues and epics from porfolio through to an agile workflow. You have to double handle issues/epics.

I can follow up on this by noting that the conclusion of our evaluation is that the missing sync of epic links is indeed a dealbreaker. We would not be able to use Portfolio in the way we envision without it and therefore we have given up on Portfolio.

I second the comments by Michael and Mikkel.

After a brief evaluation period, we purchased Portfolio for 25 developers, and we have now invested considerable effort into transferring business data from other planning tools to Portfolio... only to discover this bug.

This should NOT be a suggested feature. The fact that Epic links are written to Jira once, and then never again is a BUG in the advertised and documented product feature set, and until it is fixed, the use of Portfolio in a real world setting will be prone to errors, slip-ups, and issues getting lost. Frankly, I am amazed that this bug has existed since March. How many companies currently use Portfolio? Three?

Please provide a timeframe for this to be fixed, or prepare for a shitstorm of terrible reviews by people trying to use your product for real world planning.

I am evaluating Portfolio at the moment and actually just submitted a bug report about this to support an hour ago and now I found this issue.
Keeping epic/story links consistent manually would be an absolute nightmare! I am thinking this will probably be a dealbreaker for our purposes.
For an add-on that is priced like a finished product, this is a glaring piece of missing functionality.

I second that - the value of Portfolio is not there when this behaviour is not as expected

The lack of documentation of this issue make it even more frustrating. One clicks update selects replace links and magically nothing happens.

Is there a timeframe for when this will be fixed

Not having this feature basically makes JIRA Portfolio useless for management of real Agile based projects.