our organization enabled a new field and must be enabled in portfolio view, which I did successfully. Before the new field is used in JIRA issue, it was already being used in Portfolio view. So the update in Portfolio can't be updated back to JIRA issue because it wasn't enabled yet. Now that it is and people intend to update this field in JIRA, the changes are not reflecting in Portfolio. I was thinking it should be automatic...it turned out I am missing something.
Example: the field is risk mitigation
JIRA issues are supposed to be updated using risk mitigation field, and it's being populated by users. Now, in Portfolio view, the update is not showing up.
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