How to create a Scrum board from JQL query

Question

I have a JQL query that lets me see open bugs, stories, and epics in my project backlog:

project = ABC AND (issuetype != Test OR issuetype = Epic) AND status != Closed

I saved this query, but when I try to Create a Scrum Board from this saved query, it gets converted into something else that doesn't show any Epics:

https://mycompany.atlassian.net/secure/RapidBoard.jspa?rapidView=83&view=planning&issueLimit=100

Any ideas how I can brute force my Scrum board to default to my saved query? Thanks

Seth Cohen_qb1gco · Answer

Thanks, @Petter Gonçalves. I appreciate the reply but don't think you directly answered my question. Let me expand a bit to see if you can provide further guidance.

* Our team uses Classic Jira and Scrum.
* We recently added Portfolio to our toolkit, one main reason was so we could stop using Epics to track big quarterly projects and use Initiatives instead for these.
* What we'd like to have is a simple board we can use for sprint planning that shows:* Portfolio Initiatives which we use to track our major project commitments.
* Epics which we now use to encapsulate features that span multiple sprints.
* Stories, Bugs, Tasks that are defined as completable in 1 sprint.

* The query I used above (which I agree can be improved, thanks) gets me closer to the single board view we seek per above when I run the query in Issue Search.  
But I can't find a way to create a Scrum board view from this query -- instead, every time I try to create a new board I get a RapidBoard with parameters rapidView=83, view=planning, and issueLimit=100 (we need more). I can't seem to not get this to happen.
* Do you know how I could create a Scrum board to be used for planning from a custom JQL query using Classic Jira?

Thanks for any help.

Petter Gonçalves · Answer

Hello @Seth Cohen

Welcome to Atlassian Community!

Boards created from JQL filters display the exact same issues that the filter returns, however, there are some settings and exceptions you must consider.

Please, allow me to bring you some concepts so we can better know we are on the same page:

1 - Since Epics captures a large body of work but would not suppose to be tracked in Sprints, Scrum boards do not display any Epics in the board itself but in a separate panel at the left side of the board, as you can see in the screenshots below:

2 - Once you configure your board with a JQL filter, you must make sure the statuses of the issues returned in your board are correctly mapped to your board columns.

To check it, navigate to your board > Click in the three dots icon (...) at the top-right corner > Board settings > Columns and check if the status is properly mapped to your board columns.

3 - Check your JQL query, once you added the "issuetype != Test", it will consider all issues that are not "test", including Epics. That being said, the parameter "issuetype = Epic" is not necessary.

To edit the JQL query related to your board, navigate to your board > Click in the three dots icon (...) at the top-right corner > Board settings > General > Edit filter query:

project = ABC AND issuetype != Test AND status != Closed

Let us know if you have any questions.