Portfolio for Jira 2.13 release notes
23 April 2018
The Portfolio for Jira team is pleased to announce the release of Portfolio for Jira 2.13.
- Java APIs in Portfolio
- REST APIs out of Beta
- One more editable custom field type
- Performance improvements now out of Beta
We believe these features will help you plan work more efficiently in Portfolio for Jira.
Portfolio for Jira Server technical writer
Want to try a shiny new version? Renew your active software maintenance now.
Java APIs now available
After releasing REST APIs, we're now launching Java APIs in Portfolio for Jira 2.13. Tha 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, but we'll add more functionalities based on the feedback we'll receive.
Head to our Java API docs, and do share your feedback on our Java APIs in - JPOSERVER-1814Getting issue details... STATUS .
REST APIs out of Beta
Following the REST APIs (Beta phase), we've revamped and improved the APIs, based on your feedback — and we thank you all for your valuable comments and suggestions. In this release, our REST APIs are fully out of Beta, with the following improvements:
- Listing plans and programs
- Getting issue hierarchy configuration
- Managing holidays in plans
Check out our REST API docs to know more:
Another custom field type made editable
Remember when you had a list-type custom field in your plan, and you could not select an option from that list in your plan? Say goodbye to those times, because we now let you do just that.
See Configuring custom fields to know more.
Performance improvements now out of Beta
We released some performance improvements as beta features back in Portfolio for Jira 2.12. These features are now out of Beta:
- Hierarchy issue loading
- Plan permission checks
Check out Early access features for more info.
Performance and stability fixes