Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Updating the Jira Portfolio custom fields via API

I am building out a SAFe deployment with Portfolio based on the following hierarchy:

Portfolio Epic

     Capability

          Feature

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".

issue.update(fields={'customfield_19870': 'GISCAP-11'})
issue.update(fields={'customfield_19753': 'GISCAP-11'})

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.

1 answer

1 vote

Hi David,

 

At this time there is no official Portfolio API published.  There are a few open Suggestions to Implement a REST API for JIRA Portfolio:

JPOSERVER-438 - Implement a REST API for JIRA Portfolio

JPOSERVER-1814Publish Portfolio for JIRA Java API

Please vote on both of these and add your use case to the notes to add impact.

 

Cheers,

Branden

Thanks.   Posted a comment to JPOSERVER-438 looking a potential workaround.

cPrime is working on a upstream solution to the problem which will allow API access to update the Parent Link.   Hopefully, something within the FY18Q4 timeframe.

Hello, do we have news from Atlassian about an official and complete API ?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

132 views 9 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you