Forums

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

What is the best way to configure portfolio? by boards or projects?

Legna Garcia
Contributor
June 19, 2018

Hi folks,

I had firstly portfolio configured by projects in the "Issues Source" settings. However, after the settings were change some of them to get data by "board" not all dependencies are shown in dependencies report. 

Any idea or solution?

Regards,

2 answers

0 votes
Legna Garcia
Contributor
July 13, 2018

Hi folks,

I had an analysis discussion with Support team. If you are experiencing the same behavior, here is the sumary of the result :

1. The boards/projects selected as the source for the Portfolio plan didn't have that linked issues within them.  : for checking this, go to the issue that doesn't appear in the report, and click on "View on board" link, and make sure you add the issue the correspondent board or even add the correct board in portfolio plan settings.  The difference between choosing a board as a source and a project is that the project will return all issues related to it and the board, the board's filter outcome issues.

2. The issue appears in Scope option. So after board changes are done, and you are sure the portfolio resourses are correctly configured,  hit Calculate from the "scope" view. The issue started to appear in the Scope and in the Dependencies report.

I hope this helps, it worked to us

Regards,

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 22, 2018

Hi Legna,

It's best to configure by board, because then this will include sprint information.

Can you tell me, are the dependencies missing the same ones you mentioned in your other thread

Regards,

Shannon

Legna Garcia
Contributor
June 22, 2018

Hi @Shannon S: yes, they are. I just realized the configuration changed a bit with boards, I was hoping that was a cause of error. 

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 25, 2018

Thank you for confirming, Legna.

I spoke with the Jira Cloud team and they've suggested a bug that might be the issue you're running into. I've replied to your other thread so please have a look there and let us know if you have any questions.

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer