Portfolio for Jira 2.12 release notes
13 February 2018
The Portfolio for Jira team is pleased to announce the release of Portfolio for Jira 2.12.
This release includes:
- BETA sneak peek into public APIs in Portfolio
- scheduling unestimated work with target dates
- beta features for plan performance
We believe these features will help you plan work more efficiently in Portfolio for Jira.
Ashley Icamen
Portfolio for Jira Server technical writer
Public REST APIs BETA
We now have public REST APIs in beta phase for Portfolio for Jira. The main functionalities of these APIs are setting the availability of teams, and listing the teams and members defined in Portfolio plans. This is our first iteration — we will add more capabilities moving forward.
As the APIs are still in beta phase, do share your feedback and thoughts in JPOSERVER-438 - Getting issue details... STATUS .
See our REST API docs to know more.
Target dates for unscheduled items
You can now use target start and target end dates when scheduling unestimated work items. This is helpful if you ever want to use a combination of custom options — perhaps target start date and due date, as shown in the example below.
See Scheduling unestimated items for more details.
Beta features for plan performance
We've added more beta features, so you can get more out of your plans.
Hierarchy issue loading
Enable this to make large plans load faster, despite having issues in multiple hierarchy levels.
Plan permission check
Use this beta feature to restrict permission checks against only the projects in your plan, and not your whole instance.
To know more about these beta features, see Using Portfolio beta features.
Performance and stability fixes