You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My name is Lars Broden and I am the Product Manager for the Bulk Clone 3:rd Party plugins which is on Atlassian Marketplace
We have some customers of our plugin Bulk Clone Professional that is also using Jira Portfolio and would like to BulkClone "Child Issues" and as a result would like to have the "Parent Link" field migrated to the cloned parent issue in case they want to clone a parent issue and it's child issues.
In order to accomplish this we need to be able to edit the "Parent Link" custom field value from Java, from our research so far it seems that the value for the field is a custom Portfolio object (not an IssueImpl object)?, and we cannot update the value of the field as a consequence of this.
Is there a way we could do this from Java?, The "Epic Link" field for example stores an IssueImpl object as it's value and that type is available in the API and we can edit values for it. Could you guide us in the right direction?
The way we try to set the value is via "field.updateValue(obj1, obj2,...)"
Would appreciate a quick feedback on this as we have clients awaiting an imminent release supporting this and we are currently stuck/blocked to proceed
LB Consulting Group AB
Moible: +46 (0) 709 56 58 43
Hi @Lars Broden ,
Portfolio Parent Link information is stored in the issue properties (see entity_property table) that is accessible via the Jira REST and Java API (e.g. https://developer.atlassian.com/server/jira/platform/entity-properties/)
The issue property is essentially a JSON blob that may contain multiple values (this is the case for Portfolio) so be sure not interfere with those, depending on how you interact with those values.
Also, those fields require to be in the Jira Lucene index so depending on how the issue gets modified, be sure it gets re-indexed!