nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Prevent Portfolio from importing potential projects defined by filter

Marc Dzierzawa

We using a filter as portfolio source like:

status != Backlog AND project in projectsLeadByUser(username)

It seems that portfolio imports all potential projects even those which don't have any matching issues.

Is it possibel to prevent portfolio of doing this? It is important for us as it would improve the overview and the filter choice and also prevents exceeding the 100 projects per plan maximum.

Comments

Shannon S

Hi Marc,

You should include "AND status = Open" in your filter to use with Portfolio. This might not affect the issue but it's good to include. Can you run that whole query in Jira Issue Navigator and see what comes back?
Please also run a database search for the projects you are lead in:
```
SELECT * from project WHERE lead = 'username';
```

Thank you!

Shannon

Marc Dzierzawa

Hi Shannon,

1. I added "AND resolution = Unresolved" as we have also other status which we want to have included. However this didn't affect the issue. When I run the query in Jira Issue Navigator, the result is what I expected.

2. I tried this and see all the projects where I set as lead. These are the projects which I also see in portfolio.

I don't know if I put my problem across correctly:

Say we have two project where I set as lead: Project "A" has some issues which are not resolved, Project "B" has only issues which are resolved or even no issues. When I use my mentioned filter as source in protfolio, I only see the issues of Project "A" in the list (which is what i expect"). However I still see Project "A" and Project "B" in the project filter list. But I would expect that I will only see Project "A" as there is no issue of Project "B" in my portfolio plan.

Shannon S

Marc,

Thank you for checking that. So, to confirm, Project A does have some issues that aren't closed yet, but Project B has ONLY issues that are resolved? Can you clarify what you mean by "or even no issues"?

Since Project B is only resolved issues, are you saying you expect Project B to not show up at all?

Regards

Shannon

Marc Dzierzawa

Hi Shannon,

these are two possible use cases where I expect that Project B will not shown in portfolio. In both cases, there will be no issue from Project B which is found by my filter (either because the project has no issues or all issues are already closed).

Yes, I would expect that project B is not shown in portfolio as the filter doesn't find any issues of Project B.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

advanced-roadmaps