We have a workflow with several post-functions on the create transition to set fields based upon the link type relationship, for example: when creating a Story, the component field will be set based upon the component field in the associated Epic (using 'has Epic' relationship).
This works fine when creating new Stories via JIRA. However, if we create our Stories in JIRA Portfolio, the same post-functions are not applied and the component field is not populated based upon the associated Epic.
Is this to be expected? Anyone know if there's another way around this? Thanks.
Unfortunately, without a published API, it's difficult to see exactly what Portfolio is doing when it creates issues within Jira.
The order of operations of your Post Functions may need to be rearranged for Portfolio to support it. Or you may need to make the Component/s field required to force it to pop up the create dialog in Portfolio.
Those are the only suggestions I can make. I am curious to see if either of those fixes the issue. If not, you may need to file a bug or suggestion with Atlassian.
The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag. Do you structure your teams i...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot