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
For example, I want to copy the Fix Version of my Feature (Feature parent links to Epic) to my Epic through the use of a post function (provided by Jira Workflow Toolbox). When I create an Epic through Jira Software's Create button, I select my target feature in the Parent link field, and upon creation my Fix Version is copied over (via said post function).
However, when I create an Epic in Portfolio linked to my target feature, I commit the change and the field is not copied over.
So I'm not sure how Portfolio creates issues. I would have assumed it would use the same process Jira does since it's an add-on. Any ideas?
Portfolio for Jira creates issues without their issue links (at first) and so post-functions referencing these issue links will fail. Vote for the issue below!
JPO Server Suggestion: Issue creation from Portfolio plan does not create the Epic Link on the first step