Why aren't dropdowns intelligent?

Question

Overall JIRA is a pretty great product. However there are some things that don't make sense. For example, if I'm editing a ticket that is part of a project and I click the Sprint dropdown for example, why do I see options in the sprint dropdown that aren't for this project? Makes no sense. Why not filter for the sprints in the current project???

Similar, if I'm running a search and I pick a Project, then am trying to filter for a particular sprint in that project (Sprint 3 for example) ...I type Sprint 3 and I get no results but a bunch of sprint names from different projects. WHY ....doesn't it filter it based on the project I have already selected? Now it's a major pain for me to filter for the sprint and I'm not even sure how to do it because typing "Sprint 3" in the dropdown shows no results even though I have filtered for the Project and the list of issues shows issues assigned to Sprint 3. So frustrating.

Nic Brough -Adaptavist- · Answer

Atlassian's docs reach that way, but if you're using that type of board, you can't possibly run into the problem you describe because you can't edit the filter as you have said you have.  So you must be using the boards that do not belong to projects.

Jason Burdey · Answer

Based on JIRA documentation, sprints are created inside projects. https://support.atlassian.com/jira-software-cloud/docs/enable-sprints/

Boards can be created in a project or are based on a filter and that is why you can have issues from multiple projects displayed on that board. https://confluence.atlassian.com/jirasoftwareserver/creating-a-board-938845220.html

Creating boards based on a filter is not something I have really used so it's something I will have to look into which seems cool.

Nic Brough -Adaptavist- · Answer

But sprints are not created "inside projects".  They're created from boards, which could include many projects.  Hence they can't do it.  (Although my "fix" would be to get the code to parse the JQL for "project in" or "project =" type clauses so that they can)

On the subject of "how many people run cross-project boards", my experience gives me an answer of "most".  I'm less connected to development now, but in my last job, the organisation I worked for had about 3,500 active Jira users (i.e. using it to run their jobs), almost 1,000 active projects (and maybe 3-4,000 more mostly without active development, but still needed to be monitored for support).  I don't think I ever saw a board with only one project there!  More recently, as a consultant now, I do see more, but I would still say fewer than half of the boards I see are covered by just "project = x"

This ratio jumps massively upwards if you go to places doing Scaled Agile - generally a board represents a teams work and that goes across projects a lot more!  It's rare to see a large user base with single project boards.