Hi Valdis, you can't do that right now, however, it sounds like an interesting feature indeed. The only problem right now would be that JQL require calling JIRA API everytime someone change such filter and at the moment the engine does all the filtering at the frontend side.
As an interim solution, would be OK for you to just having yet another filter for "Issue Type"? That sounds like much easier to implement.
OK, so I think the feature that you're after here would be something like an extra "JQL filter" that is always included when querying JIRA API. Then, it would work regardless of current filter setup as some kind of "low-level filtering" (in fact, we do that for removing archived projects from results already). I like that idea as it will address other issues too, for example, that one reported here:
I have created a separate feature request for this (can't say exact timeframe yet but I think it will be done in next few days, week at most:)
The feature I've mentioned in my last comment is now implemented so you can use custom JQL query now. More information here:
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs