Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89775

JIRA Portfolio Evaluation - Pls. forward to Martin Suntinger

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • Plans - Timeline
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Dear Martin Suntinger,

      You may recall that we - briefly - exhanged ideas/opinions earlier this month on the subject of JIRA Portfolio.

      Our evaluation has now been completed and our project manager, Gert Pedersen, has submitted his report to our Confluence "Wiki" instance - pls. see the attached PDF.

      As you will note, the recommendation, and the following decision, was not to license JPO at the moment.

      I'm sending you the evaluation report to ensure that you know exactly what triggered the outcome. I trust you can use the content, not just to dismiss our quaint ways of working , but also for improving the product going forward.

      If you have any questions, please comment on this ticket.

      In any case, I'll be attending the Summit next November, should the need arise for us to have further interaction.

      Cheers,

      Lasse

        1. IIS-250915-1323-2.pdf
          13 kB

            [JRACLOUD-89775] JIRA Portfolio Evaluation - Pls. forward to Martin Suntinger

            Martin Suntinger added a comment -

            Hi lasse.kaiser,

            Thanks a lot for sharing the complete evaluation report - this is great input going forward and I hope in some iterations down the road we'll be able to make it a viable product for your usecases. The topic we're addressing most directly is a more seamless interplay with data in JIRA - once there is a tighter link, it opens the door for leveraging more of JIRA's flexibility e.g. with custom fields for reporting and filtering.

            As for scheduling-related input, one point i noticed was: "complex due to stage-skill setup": Even though some of the default plan templates come with stages/skills, it is actually also possible to plan completely without stages and skills, which makes it easier (just does not allow in turn to detect bottlenecks on different skillsets, but that might not be needed anyways) -> We'll put this a bit more in the background in future versions, suggesting to start without stages/skills initially, and then refine the breakdown only as needed.

            As the feedback is a collection of various points, I'm resolving it as a suggestion ticket, but taking it as input to our case-by-case deep-dive feedback, so it can be acted on in future versions.
            Thanks,
            Martin Suntinger

            Martin Suntinger added a comment - Hi lasse.kaiser , Thanks a lot for sharing the complete evaluation report - this is great input going forward and I hope in some iterations down the road we'll be able to make it a viable product for your usecases. The topic we're addressing most directly is a more seamless interplay with data in JIRA - once there is a tighter link, it opens the door for leveraging more of JIRA's flexibility e.g. with custom fields for reporting and filtering. As for scheduling-related input, one point i noticed was: "complex due to stage-skill setup": Even though some of the default plan templates come with stages/skills, it is actually also possible to plan completely without stages and skills, which makes it easier (just does not allow in turn to detect bottlenecks on different skillsets, but that might not be needed anyways) -> We'll put this a bit more in the background in future versions, suggesting to start without stages/skills initially, and then refine the breakdown only as needed. As the feedback is a collection of various points, I'm resolving it as a suggestion ticket, but taking it as input to our case-by-case deep-dive feedback, so it can be acted on in future versions. Thanks, Martin Suntinger

              Unassigned Unassigned
              lasse.kaiser Lasse Kaiser
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: