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

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

How to filter on Epics and custom fields, for Portfolio

I'm about to give up on this but want to try here before I throw in the towel.

I have the following setup:

  1. Jira Cloud with Portfolio
  2. One project, multiple teams
  3. Custom workflow with several Kanban boards covering stages from roadmap to deployment
  4. Team Kanban boards for the dev/sprint part
  5. Initiatives (used for roadmap priority segmentation), Epics, Stories, Subtask hierarchy
  6. We plan on Epic level (currently)

This setup somewhat works with Portfolio (apart from all sorts of Portfolio issues that I won't even go into here). In the source definition of Portfolio I select all relevant Epics per Initiative I want to include in the plan, allowing me to add lower priority epics to 'fill up' capacity.

As I may need to rename Epic to Features soon (currently splitting epics into multiple epics to mimic features, for more detailed planning) I need to make the Initiatives level free to act as Epics. I therefore created two custom fields for epic level issues, one for roadmap priority and one for scope inclusion/exclusion field. Selecting on those fields I should be able to find all Epics with priority 1 AND all other priorities that have been explicitly included. I do NOT want to set priority and scope fields on all involved issues unless it can be done automatically when setting the epic fields.

And now the tricky bit: I need a filter that will select for Portfolio source:

  1. All epics with priority field set to a specific value or values OR scope field set to included
  2. All user stories related to the epics identified in step 1 (not any other issuetype)

And a few limitations:

  1. Any sort of pricey (meaning any cost above zero) plugin is not an option right now
  2. Using hardcoded issuekeys is not an option
  3. In the new situation (initatives turned epics, epics turned features and planning on feature level) the adapted filter should still work

Any ideas?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across Jira Cloud instance.   📢 Get y...

217 views 10 8
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