Make component in issue metadata link to advanced search for issues in that component [#2225601]

Updated: Comment #0

Problem/Motivation

In the issue metadata section the component information is only a text, and we need to transform into a clickable link, to improve the user experience.

Compare that to the tags list. Each tag is a link to a search for that tag.

This will speed up contributor who are looking for issues related to an issue they are already looking at.

Proposed resolution

Change component text to be a link to point at the advanced search page for the respective project, with the component filter presetted.

Remaining tasks

discuss
implement https://drupal.org/contribute/drupalorg/code (Contribute to Drupal.org Code changes document)
write patch
add before screenshot
review

User interface changes

Yes. That's the whole issue.

API changes

None.

Comments

Comment #1

YesCT CreditAttribution: YesCT commented 26 March 2014 at 09:54

Title:

The componenet information from the issue metadata section must be a clickable link

» Make component in issue metadata link to advanced search for issues in that component

Comment #2

nagy.norbert1989 CreditAttribution: nagy.norbert1989 commented 31 March 2014 at 09:13

Issue summary:

View changes

Comment #3

YesCT CreditAttribution: YesCT commented 3 April 2014 at 14:42

Issue summary:

View changes

added link to how to work on a d.o issue to the remaining tasks in the issue summary

Comment #4

YesCT CreditAttribution: YesCT commented 21 December 2014 at 18:21

Parent issue:

» #2396859: [Meta] finding issues is difficult

Comment #5

YesCT CreditAttribution: YesCT commented 9 March 2015 at 20:19

Comment #6

dww

we/he/they

CreditAttribution: dww as a volunteer commented 16 May 2015 at 23:56

I like this, but it contradicts the direction people are proposing with #2489868: Make priority and category header in meta data summary (in sidebar) on issues link to the handbook page that defines them, and style to look like links. If any of the labels in this block are turning into links, we should be consistent about what they're linking to (either docs or searches, not some of both).

Comment #7

joachim CreditAttribution: joachim commented 17 May 2015 at 06:19

I don't think it does contradict: the mockup on that other issue indicates it's the field label that would link to documentation; here I'm suggesting the actual field value is made a link.

Comment #8

dww

we/he/they

CreditAttribution: dww as a volunteer commented 17 May 2015 at 09:06

Right, YesCT pointed out the same in the other issue. I think that could be a repeatable pattern throughout this UI, I withdraw my concern about a contradiction.

However, holy crap, this is already such an overwhelming interface -- I can't imagine how painful it would be to navigate with a screen reader...

Comment #9

joachim CreditAttribution: joachim commented 26 May 2015 at 09:12

It occurs to me that this could probably be done with https://www.drupal.org/project/linked_field and some new admin settings in the field formatters.

Comment #10

ressa CreditAttribution: ressa at Ardea commented 2 December 2020 at 16:57

I agree with the proposal of linking the component text to the advanced search page for the respective project, with the component filter presetted. (I recently created an issue (#3185573: Link Component field in issues) which was correctly closed by @drumm as a duplicate of this issue.)