Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25313

Extend Advanced Roadmaps to third-party plugins

XMLWordPrintable

    • 2
    • 9
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Problem Definition

      Currently, Advanced Roadmaps for Jira (Portfolio) is not able to integrate with some of the popular third-party apps, such as:

      Supported Feature

      1. Some of the features in these third-party apps use custom JQL functions, such as:
        • islinkissueof
        • linkrecursive
        • issue in fieldmatch()
      2. SR Behaviours

      Suggested Solution

      We should have this integration between Advanced Roadmaps for Jira (Portfolio) and other third-party apps to utilize the features provided by them.

      These features are useful to integrate with Advanced Roadmaps for Jira (Portfolio) when it comes to hierarchy representation.
      Customers widely use these and are considered to be very important to be integrated with Advanced Roadmaps for Jira (Portfolio).

          Form Name

            [JSWSERVER-25313] Extend Advanced Roadmaps to third-party plugins

            Aakrity Tibrewal added a comment -

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Deleted Account (Inactive) added a comment -

            We have a scriptrunner post function that automatically sets the correct Portfolio "Team" on issue creation. Although the Team is correctly filled in in Jira, Portfolio does not seem to pick up on the change as the value is normally set from within portfolio itself and not by 3rd party add-ons.

            We'd really like to see this feature implemented as we can take away a lot of unnecessary extra work from our project managers as thousands of tickets get created by various automated systems (and all of them need to fit in the plan).

            Deleted Account (Inactive) added a comment - We have a scriptrunner post function that automatically sets the correct Portfolio "Team" on issue creation. Although the Team is correctly filled in in Jira, Portfolio does not seem to pick up on the change as the value is normally set from within portfolio itself and not by 3rd party add-ons. We'd really like to see this feature implemented as we can take away a lot of unnecessary extra work from our project managers as thousands of tickets get created by various automated systems (and all of them need to fit in the plan).

            Roi Fine (Inactive) added a comment -

            Hi all,

            Scriptrunner has recently released an update with some fixes to Portfolio compatibility. You can check it out here: https://scriptrunner.adaptavist.com/latest/jira/releases/current-release.html

            The Portfolio for JIRA team

            Roi Fine (Inactive) added a comment - Hi all, Scriptrunner has recently released an update with some fixes to Portfolio compatibility. You can check it out here: https://scriptrunner.adaptavist.com/latest/jira/releases/current-release.html The Portfolio for JIRA team

            Natallia Shalakhanava added a comment -

            I confirm, in the newer versions of JP, when we are using issueFunction  with issuesInEpics function, the items are returned by query but are not scheduled on timeline. This is very unfortunate behavior, because in the older version of JIRA Portfolio(2.1.5) the functionality was working fine, and thus we adopted this function for all of our project plans!

            Natallia Shalakhanava added a comment - I confirm, in the newer versions of JP, when we are using issueFunction   with issuesInEpics function, the items are returned by query but are not scheduled on timeline. This is very unfortunate behavior, because in the older version of JIRA Portfolio(2.1.5) the functionality was working fine, and thus we adopted this function for all of our project plans!

            PoflankovaM added a comment -

            Wnen you use some Script Runner JQL functions in Portfolio plan source board/filter,  sometimes it cause that tasks are not scheduled right.

            PoflankovaM added a comment - Wnen you use some Script Runner JQL functions in Portfolio plan source board/filter,  sometimes it cause that tasks are not scheduled right.

            Mark Adams added a comment -

            Thanks Robert. We already have Structure 3.4 installed and are planning to update it to use the Parent Link very soon.
            Thanks for the links to the blogs as well!

            Mark Adams added a comment - Thanks Robert. We already have Structure 3.4 installed and are planning to update it to use the Parent Link very soon. Thanks for the links to the blogs as well!

            Robert Leitch [ALM Works] added a comment -

            Hi Daryl, Mark, in Structure 3.4 we implemented grouping/extending support for Parent Link.

            Here's a basic example of using grouping by Parent Link to recreate Portfolio plans in Structure. There's a second part about creating overviews of multiple Portfolio plans.

            You can also build structures top-down using the Parent Link extender. More materials are in the works (managing links, embedding structure-d plans in Confluence & dashboards, exporting, etc.).

            Robert Leitch [ALM Works] added a comment - Hi Daryl, Mark, in Structure 3.4 we implemented grouping/extending support for Parent Link. Here's a basic example of using grouping by Parent Link to recreate Portfolio plans in Structure . There's a second part about creating overviews of multiple Portfolio plans . You can also build structures top-down using the Parent Link extender. More materials are in the works (managing links, embedding structure-d plans in Confluence & dashboards, exporting, etc.).

            Mark Adams added a comment -

            This goes too for working in the other direction, as the new 'parent link' and 'child link' introduced by Portfolio needs to be supported by Structure and scriptrunner before they can be properly utilised.

            Mark Adams added a comment - This goes too for working in the other direction, as the new 'parent link' and 'child link' introduced by Portfolio needs to be supported by Structure and scriptrunner before they can be properly utilised.

              Unassigned Unassigned
              dchua Daryl Chuah (Inactive)
              Votes:
              31 Vote for this issue
              Watchers:
              33 Start watching this issue

                Created:
                Updated: