I'm trying on the new Portfolio 2.0 for Cloud.
But I can't seem to import tickets during planning. I'm allowed in the creation of a plan, where you choose the JIRA-projects and releases.
But after that I can't find an import button like in the old version, and it doesn't seem to automatically import issues(unless they should be treated special to get auto-imported)
Any help or pointers would be greatly appreciated?
Portfolio 2.0 has replaced the import workflow with an "Issue source" model. The issue sources are the projects/boards/filters that you define as the issues to bring into Portfolio and remain synchronized with JIRA.
The steps in the plan creation wizard will ask you to select the issue sources from JIRA, relevant fix versions/releases and particular issues you want to exclude/include. Once this has been configured issues will automatically be brought in from JIRA including new issues as they're added to the source from outside Portfolio.
Please let me know if you have any further questions regarding this.
Thank you for the answer.
How do I configure/edit which projects/boards/filters after I've created the plan. I realize that I can configure it in the creation wizard, as you mention. But any changes after that, I can't seem to find where to configure?
I'm trying to bootstrap a new plan for an existing project, and everything seems fine except that stories that have already been completed don't seem to be included in the import. As a result everything is showing as 0% progress, which is very wrong
Is that intended, or something I'm doing wrong?
I found another thread somewhere in Atlassian Community that talked about the filters that determine which closed issues appear in Portfolio at all. By default, it only shows closed issues in the current sprint, but using the filters at the top of the page you can change that to display based on custom date ranges.
The solution for me to find "done" tickets in my Portfolio plan was the "Resolution" state of the ticket but there is a catch: the new Jira UI doesn't show Resolution, and even after switching to the old version doesn't let you edit the Resolution.
What I end up doing was:
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
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