The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

create plan in portfolio 2.0 not finding epics

Larry at Isos
November 2, 2016

I have a problem when I create new portfolio plan. No matter what I provide as data sources for the plan none of the epics are present in the plan.

For all the stories in the project, some of the epics are in the same project, some are in a different project.

I've tried:

Pointing the create plan wizard at a board that is confirmed to includes the epics.

Expected Result: I should see the epics with the stories nested under them in the wizard

Result: No epics appear in the plan, but they are all present on the board.

Pointing the create plan wizard at the project and adding a filter that pulls the specific epics in from the other project.

Expected Result: I should see the epics with the stories nested under them in the wizard

Result: No epics appear in the plan, but they are all present on the project and the filter.

Secondary test - complete the wizard for both of the above (assuming  it's just the wizard view of the imported issues that is in error)

Expected Result: I should see the epics with the stories nested under them in the plan

Result: No epics appear in the plan.

Secondary test - create an epic in the plan and commit the change

Expected result: after I commit the change of adding one epic to the plan it should appear in both the project and the plan

Result: Epic is created in the project but after commit is no longer present in the plan.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Larry at Isos
November 2, 2016

Actually this is from @Martin Suntinger via email, and is in reference to this other question I didn't find: https://answers.atlassian.com/questions/38390402

Our instance had the FixVersion field hidden for epics and that caused Portfolio for JIRA to not 'see' those issues at all because (from that Live Plans answer):

...like for example having removed the fixVersion field at all from the issues? Portfolio checks this field when loading issues to see if its in an included or excluded assignment, if the whole field is not there, it might cause problems