Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11278

Improve the "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue.Learn more" error message

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 8
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      A customer was confused by this error message showing on his board: "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue. Learn more"

      Apparently this displays if there are no projects or issue types detected, which is most likely due to the board's filter filtering them out.

      The Learn more links to a general page on Configuring boards, but I think we should be more specific in the error message. Suggested text:
      "You will need to use the full dialog to create a new issue, as your board's filter is excluding all projects and/or issue types."

          Form Name

            [JSWSERVER-11278] Improve the "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue.Learn more" error message

            Why does this "pop-up" stay in place with no option to get rid of it?  It blocks information behond it which is very annoying when trying to review issues by Epic.

            Henry St Aubyn added a comment - Why does this "pop-up" stay in place with no option to get rid of it?  It blocks information behond it which is very annoying when trying to review issues by Epic.

            richard.wheeldon added a comment - - edited

            My concern with this error message is that there doesn't seem to be any way to get rid of it, once it gets stuck there. i.e. The full dialog for ticket creation will appear but this error message floats above it.

            It looks like it appears as part of a hover-over but under some circumstances (which I can't figure out but are annoyingly frequent) when the mouse moves away the little popup stays there and can't be got rid of other than by a hard-refresh. Probably fixable by a simple. "If you click on this thing, it should go away" rule.

            richard.wheeldon added a comment - - edited My concern with this error message is that there doesn't seem to be any way to get rid of it, once it gets stuck there. i.e. The full dialog for ticket creation will appear but this error message floats above it. It looks like it appears as part of a hover-over but under some circumstances (which I can't figure out but are annoyingly frequent) when the mouse moves away the little popup stays there and can't be got rid of other than by a hard-refresh. Probably fixable by a simple. "If you click on this thing, it should go away" rule.

            I was stumped for a long time on this error but found what caused it. I got this error message when my board's filter had a query for two labels (i.e. project = foo AND labels = "A" AND labels = "B" ORDER BY Rank ASC) since I wanted it to show just stories that had both labels. 

            If I removed the 'AND labels = "B"' part it would do a create inline without the full dialog. I can understand if my query had an OR (i.e. 'labels in ("A", "B")' how Jira wouldn't know which label(s) to put in for the new story, but I request that this be fixed to automatically handle the AND case by populating the new issue with both labels.

            Let me know if there are any other workarounds.

            Brian Kinkade added a comment - I was stumped for a long time on this error but found what caused it. I got this error message when my board's filter had a query for two labels (i.e. project = foo AND labels = "A" AND labels = "B" ORDER BY Rank ASC) since I wanted it to show just stories that had both labels.  If I removed the 'AND labels = "B"' part it would do a create inline without the full dialog. I can understand if my query had an OR (i.e. 'labels in ("A", "B")' how Jira wouldn't know which label(s) to put in for the new story, but I request that this be fixed to automatically handle the AND case by populating the new issue with both labels. Let me know if there are any other workarounds.

            Chloe King added a comment -

            I have been having this problem, and it seems to be due to (in my case) the project only having 1 issue type - adding in a second solved this issue (it is worth noting that the saved filter was set to show everything, so in this instance it did not seem to be an issue related to the filter not finding any results).

            Chloe King added a comment - I have been having this problem, and it seems to be due to (in my case) the project only having 1 issue type - adding in a second solved this issue (it is worth noting that the saved filter was set to show everything, so in this instance it did not seem to be an issue related to the filter not finding any results).

            This occurred to me as well, and here's why. I changed the name of the project after it was created, except the "Saved Filter" that is set for the board (under Configure) still had the old name of the project (it doesn't look like it uses a proper key). Hence it was no longer valid, and this caused the problem where every time I clicked on the Backlog tab, the Create Issue window would automatically pop up (with the useless "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue. Learn more"). The suggested update to the text above would be very helpful to troubleshoot this.

            If you are seeing this problem, check if you have changed any project names, board names, or project keys, and check your filters (both on the Board and individual ones).

            Hakan Kilic added a comment - This occurred to me as well, and here's why. I changed the name of the project after it was created, except the "Saved Filter" that is set for the board (under Configure) still had the old name of the project (it doesn't look like it uses a proper key). Hence it was no longer valid, and this caused the problem where every time I clicked on the Backlog tab, the Create Issue window would automatically pop up (with the useless "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue. Learn more"). The suggested update to the text above would be very helpful to troubleshoot this. If you are seeing this problem, check if you have changed any project names, board names, or project keys, and check your filters (both on the Board and individual ones).

            I'm still not clear on what is causing this issue but with the new navigation behavior it is screwing up my universe.

            Michelle Melancon added a comment - I'm still not clear on what is causing this issue but with the new navigation behavior it is screwing up my universe.

            Same here. Of course we are filtering out projects, I assume a lot of teams will do this. Why no issue types are detected, is beyond me.
            The suggested new error message above is no more helpful than the one appearing now. Please offer a solution for this (not filtering out projects is not a practical solution)

            Barbara Kohlroser added a comment - Same here. Of course we are filtering out projects, I assume a lot of teams will do this. Why no issue types are detected, is beyond me. The suggested new error message above is no more helpful than the one appearing now. Please offer a solution for this (not filtering out projects is not a practical solution)

            Jon Abad added a comment -

            I have a similar concern.
            The filter on a sample board is much like Ray's:

            project = CP AND fixVersion in (6.0.0) AND "Scrum Team" = "The DAs" OR project = CP AND issuetype = epic AND issue in linkedIssuesFromQuery("project = CP AND fixVersion in (6.0.0) AND 'Scrum Team' = 'The DAs'") ORDER BY Rank ASC
            

            I'm explicitly limiting my results to contents from a single project and fixversion+team but other than that, it's nice and loose.

            Jon Abad added a comment - I have a similar concern. The filter on a sample board is much like Ray's: project = CP AND fixVersion in (6.0.0) AND "Scrum Team" = "The DAs" OR project = CP AND issuetype = epic AND issue in linkedIssuesFromQuery( "project = CP AND fixVersion in (6.0.0) AND 'Scrum Team' = 'The DAs' " ) ORDER BY Rank ASC I'm explicitly limiting my results to contents from a single project and fixversion+team but other than that, it's nice and loose.

            Don't quite follow your explaination here. We get this Error box on the planning board when we click the +Create.

            Our filter on the board is :project = "ALM Stack" and (("Epic Link" is not EMPTY) or (issuetype in ("Bug/Enhancement Task", "User Story Task", Sub-Task, Epic))) ORDER BY "Agile Ranking" ASC

            Could you give an answer as to why we are seeing this, so I know what to tell customers that are seeing the same issue.

            Thanks.

            Ray Maxwell added a comment - Don't quite follow your explaination here. We get this Error box on the planning board when we click the +Create. Our filter on the board is :project = "ALM Stack" and (("Epic Link" is not EMPTY) or (issuetype in ("Bug/Enhancement Task", "User Story Task", Sub-Task, Epic))) ORDER BY "Agile Ranking" ASC Could you give an answer as to why we are seeing this, so I know what to tell customers that are seeing the same issue. Thanks.

              Unassigned Unassigned
              alui Andrew
              Votes:
              15 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: