I am building out a SAFe deployment with Portfolio based on the following hierarchy:
I want to do a bulk upload into the various levels, but I want to automate the process to update the links without having to update 50+ features manually. After updating manually, I noted the updated custom fields 19870 and 19753 as being updated to match the parent. When I try to update the fields via API, one comes back with "not on the appropriate screen" and the other results in "internal server error".
I know at least one of the custom fields is locked. Is there an easy API based way around this restriction? What changes need to be made in order for API based updates to be successful? The manual options is not an option based on the volume, plus the potential for human error goes up pretty quickly as the user gets bored.
At this time there is no official Portfolio API published. There are a few open Suggestions to Implement a REST API for JIRA Portfolio:
Please vote on both of these and add your use case to the notes to add impact.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs