Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Using Jira queries to populate Portfolio Edited

I am trying to limit the stories that populate in Portfolio by loading a board that is populated by a filter that pulls multiple projects into one board based on epic criteria. When I look at the board in Jira the data is correct but when I pull that board into Portfolio it no longer limits the data from that board that is filtered by my query. Here is the query that I use to populate the board "issue in epicsWhereIssueIn("project= medical") AND project != medical" but when I open portfolio it list every story from all the projects that populate that board when I just want the epics. Any help is greatly appreciated. Here is another example of a query that I cannot get to populate correctly in Portfolio: project in (auto, casualty, medical, siu, ss, property) AND type = epic AND issue in epicsWhereIssueIn("project = FLEX")

1 answer

0 votes
Crystelle S Community Leader Dec 18, 2019

Question - issue in epicsWhereIssueIn("project = FLEX") - is this an add-on? At the conference class this year I asked about using scriptrunner add-on queries in Portfolio and Atlassian admitted they saw issues with nested queries from that particular add-on. It's possible that Portfolio is also having issues with your add-on. Not an answer per se but may be why you are seeing what you are seeing. I've gotten around this issue by splitting out the queries and pulling them in individually when building a Portfolio plan.

Crystelle, thanks we are doing the same thing pulling the nested queries out but we have almost 75 teams that we have to individually create to get the same data we get from the nested query. I was told that these nested queries are called Jira tricks but they don't seem to work for portfolio.

Crystelle S Community Leader Dec 19, 2019

yes, the information we were given at the conference seemed to indicate that people are seeing strange, varied behavior and it was being investigated. the workaround suggested was what you and I are doing... that was in April this year (2019)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,558 views 25 18
Read article

Community Events

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

Events near you