We are using a Jira Cloud Scrum board called QA Board within a single space (Web_Dev). Within this space, we operate two boards by design:
The QA Board is filtered to show only Bug-type issues. The original board filter JQL was:
project in (10099) AND issuetype in (10077) ORDER BY Rank ASC(10077 corresponds to the Bug issue type)
We attempted to modify the JQL so that the inline "+ Create" option on the board would allow creating Bug issues (currently it defaults to Task only). After editing and saving the JQL, an unexpected problem occurred.
issuetype = Bug).project in (10099) AND issuetype in (10077) ORDER BY Rank ASC) and performing a hard refresh (Cmd+Shift+R), the Create button still does not reappear.WD: Scrum Issue Type Scheme)Our QA team relies on this board to triage and create Bug issues during testing. Without the "+ Create" button, QA testers cannot register bugs directly from the board, which significantly slows down our QA cycle and forces us to rely on manual fallback (top-level "+ Create" button), which is less efficient and breaks the team's established workflow.
Any guidance on:
would be greatly appreciated.
Thank you in advance!
Hello @씨엘 ,
Good day! Welcome to Atlassian Community :)
Thank you for sharing detailed information. The inline '+' create button on company managed Scrum/Kanban boards has strict requirements as outlined here: https://support.atlassian.com/jira/kb/issue-create-button-option-not-visible-in-all-columns-of-boards-in-company-managed-projects/
One of which is the Board filter. Kanban and Scrum boards must be created with the default board filter. Currently, non default board filters are not supported.
Your filter [ project in (10099) AND issuetype in (10077) ORDER BY Rank ASC) ] includes an issuetype clause, making it a custom/non-default filter. The default format Jira board should be on is: project = PROJECT_KEY ORDERBY Rank ASC
Please change the filter query of the board to default and it should work.
Thank you
Hello @Shalini Pradhan
Thank you very much for the detailed explanation and reference document.
You were right — the issue was related to our board/workflow configuration.
After reverting the board filter closer to the default structure and simplifying some workflow transitions, the inline “+ Create” behavior started working correctly again.
Really appreciate the guidance. It helped us identify the root cause much faster.
Thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.