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
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
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