Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-276

"Apply update to projects" should provide an option to sync Epic/Story relationships

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      Atlassian Update - 24 March 2016

      Hi everyone,

      Thanks for voting and commenting! This issue is being addressed as part of the all new Portfolio live plans, which feature an entirely overhauled and more seamless integration model with JIRA Software / Agile. Live plans are currently available as a labs feature for both Server* and Cloud, so you can start evaluating them without any risk of impacting existing Portfolio plans. They are not yet feature-complete, we're working on bringing all major capabilities of standard plans back into live plans on top of the new integration model before we graduate live plans out of labs and make them the new standard way of working.
      Please check out this blog for a summary and short videos of how the top-voted suggestions are being addressed with live plans: Top 10 suggestions addressed in live plans and join our Portfolio Pioneers LinkedIn group to discuss feedback and best practices!

      Thanks,
      Martin Suntinger
      msuntinger@atlassian.com
      Principal Product Manager, Portfolio for JIRA

      *The live plans labs feature is available with Portfolio for JIRA 1.12 or higher. It is compatible with JIRA Software 7.0.5 or higher, and JIRA 6.3 or higher, in association with JIRA Agile 6.7.12 or higher.

      When pushing update via Plan > Apply updates to project/s, despite all items under Update linked elements are selected, the Epic-Story links are not updated.

      Steps to reproduce:

      • Import Story and Epics from JIRA
      • Create new Epic and corresponding JIRA Epic using Portfolio
      • Move existing Story under new Epic using Portfolio
      • Click Plan > Apply updates to projects/s

      Current Behaviour

      • New JIRA Epic does not link with the JIRA Story
      • The JIRA Story still links with original JIRA Epic

      Expected Behaviour

      • The JIRA Story should now linked with the new JIRA Epic created from Portfolio

          Form Name

            [JPOSERVER-276] "Apply update to projects" should provide an option to sync Epic/Story relationships

            Albert Kavelar added a comment -

            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.

            Albert Kavelar added a comment - 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.

            Denise Hemke added a comment -

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

            Denise Hemke added a comment - I've requested access as well and it too is pending. Thanks.

            DanS added a comment -

            Hi Albert,

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

            Thanks for confirming.

            Cheers

            Dan

            DanS added a comment - Hi Albert, I requested access to the group a couple of days ago. It is still pending. Thanks for confirming. Cheers Dan

            Albert Kavelar added a comment -

            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

            Albert Kavelar added a comment - 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

            DanS added a comment -

            Hi Martin,
            Now that I have seen your talk at Summit and see what is coming we are desperate for the new version.
            It addresses most of our issues with Portfolio and will make it much more useful for our organisation.
            Any idea what the beta release date will be? We are ready and willing.
            Cheers
            Dan

            DanS added a comment - Hi Martin, Now that I have seen your talk at Summit and see what is coming we are desperate for the new version. It addresses most of our issues with Portfolio and will make it much more useful for our organisation. Any idea what the beta release date will be? We are ready and willing. Cheers Dan

            Denise Hemke added a comment -

            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."

            Denise Hemke added a comment - 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."

            James Russell added a comment -

            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

            James Russell added a comment - 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

            Benjamin Close added a comment -

            @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.

            Benjamin Close added a comment - @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.

            Albert Kavelar added a comment -

            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

            Albert Kavelar added a comment - 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

            Mads Rydahl added a comment -

            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,

            Mads Rydahl added a comment - 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,

              Unassigned Unassigned
              akavelar Albert Kavelar
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: