This seems like something that broke within the past few days but it could be that it's been broken for awhile and I just missed it.

It used to be that when you were looking at an issue like, say, #2152229: Convert theme_textarea() to Twig and you click the "Twig" issue tag link you were taken to https://drupal.org/project/issues/search/drupal?issue_tags=Twig (project-specific search for that tag). Instead, you are now taken to https://drupal.org/project/issues/search?issue_tags=Twig (global search of that tag) which doesn't let you filter by e.g. project version so is a lot less optimal.

It's not the end of the world, since you can just hack the URL, but still.

Comments

tvn’s picture

tvn CreditAttribution: tvn commented
Project: [Archive] Drupal.org D7 upgrade QA » Project issue tracking
Version: » 7.x-2.x-dev
Component: Code » Issues

Indeed, it shows all issues with the tag now, not only of that specific project.

I must say, I always hated that filtering :) and had to go and manually search for issues across all projects. Sometimes I would click the tag and think those are all the issues with this tag, and later discover there are a lot more in other projects.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

I think this is set in drupalorg_searchapi_issue_views_taxonomy_term_uri().

I don't like isolated code in Features, it is fair game to be moved. I think project_issue module would be best, so keeping this issue here.

However, the only context this function has is $code. It doesn't even know what issue you are looking at, unless some hacky code is added. If there is a clean way to do this, maybe via another API, let's do it. Otherwise, we can won't fix this.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

Why on earth would we won't fix this? This continues to slow me down every single day. The only possible scenario I can see it might be helpful in is a project like Drupal.org that sprawls 50+ issue queues. For every other use case, though, you need to go through this frustrating dance:

1) Click on an issue and comment on it/commit it/whatever.
2) Say to yourself "Cool, I want to find more issues like that," and click the tag.
3) Go "Wait, what? Why are there so many issues?" Sit there for a few seconds squinting. Then go "Oh, blah. Right. I need to limit the project to 'Drupal core' (or whatever)."
4) Do that, and still see too many issues, because you also need to filter by version, which was not available on the previous screen that searched all projects.

:(