Hyperlink issue metadata values

zen, what are you talking about? ;) i can't work on this issue since i have no idea what feature you're requesting. please clarify. thanks.

see the (now duplicate) http://drupal.org/node/140853 for another interpretation on this. i suggested they move that thread in here, so we'll see how it shakes out. however, http://drupal.org/node/52232 is even older and is talking about a similar topic (for the username). i think i'll mark that as the dup with this, since this is a more far-reaching suggestion than what's there.

Linking to other issues in the project (or more specifically by issue type) would certainly fit with the behaviour of other modules like Taxonomy, Node Reference and (IIRC) Profile.

Also I've just now noticed that you can get to the project home page through the breadcrumbs, so my initial issue (finding my way back to the project home) isn't so much of a problem for people with actual brains.

Also I've just now noticed that you can get to the project home page through the breadcrumbs, so my initial issue (finding my way back to the project home) isn't so much of a problem for people with actual brains.

I also just created a duplicate issue for this ( I searched but this issue title eluded me :-)
http://drupal.org/node/141071

The breadcrumbs solve my initial issue too.
So having the projectname link to it's issue que instead seems fine to me.

subscribing

Yet another take on this... at my day job, some folks didn't realize you were expected to "reply" to an issue to change the things in that table. They wanted to assign an issue to someone else, and were completely frustrated by that table, since you couldn't click on anything or alter it in any way. :( So, if we made those things links, people might assume the link is how to alter that piece of issue metadata...

Seems there are a *lot* of different things people might expect if we made those links, and whatever we do it's going to make some people happy, confuse other people, and really annoy others. I think the issue UI needs a more coherent plan and usability effort, before we incrementally tweak things like this.

Heh....funny.

I have a hard time believing this will be that common of a problem, but I could be wrong.

I was thinking after our discussion last weekend about displaying metadata fields with multiple changes (as in the case of a multi select taxonomy term), that since we'd talked about passing this stuff through a theme function to get the output, that fixing this issue at the same time might be worthwhile. But given that this issue could get out of hand in scope quickly, maybe it's best to keep them separate.

Now that #219734: Allow theming of changes in project issue table and email is in, doing something like this would be possible, since in that commit the function that themes the metadata tables was switched to call filter_xss() instead of check_plain() on the metadata field labels and values, so it would be easier to make these links.

We should wrap any behavior created here in a theme function (or functions) so that individual sites can override whatever default behavior we implement. As for what to do by default, I'm not sure I agree with the original proposal as far as where the links should head.

In my opinion, having links to issue queues filtered by certain fields (eg. all issues of project A that are set as CNR when a user clicks on the "code needs review" link in the metadata table) is less useful than having those fields link to pages with more explanatory information. For example, the username would go to that user's profile page (via theme_username()) and the project name would be linked to the project node.

Those are the only links that I think would be obvious and broadly applicable enough that we would want the project issue tracking module to handle by default.

For drupal.org, I think it would be more useful to have the status value link to a handbook page that explains what the status itself means. By doing so I think we could solve #234544: Add link to patch creation/application handbook page on issues with patches at the same time, which would be nice.

For the rest of the metadata fields, such as version, component, and priority, I can't think of an obvious link target.

Changing title to be (hopefully) more descriptive.

Some thoughts on this..

"Clicking Drupal could display all issues in the Drupal project."
"link back to project home"
"people might assume the link is how to alter that piece of issue metadata..."

We don't necessarily have to pick one of these. What about this
Project: <a href="[project home]">[project name]</a><a href="#[edit field anchor]"><img src="pencil.gif"/></a>
or this
Project: <a href="[project home]">[project name] ([project shortname])</a><a href="[project issues]"><img src="issues.gif"/></a>
along with some useful title attributes or fancy tooltips? On the other hand, we should not put too much stuff in this piece of text.

----------

"Also I've just now noticed that you can get to the project home page through the breadcrumbs, so my initial issue (finding my way back to the project home) isn't so much of a problem for people with actual brains."

It seems that these breadcrumbs lack visibility. They are small and grey, they don't even have a hover effect, the different segments don't have a strong visual separation, they don't afford clicking, they don't afford reading, they take more time to scan than people usually want to spend looking for links. Of course, for better answers we would need some user research.

The good thing about the breadcrumb is that it gives you both the module page and the issue queue. The rest of the breadcrumb (Home » Download » Modules) is not very useful.

So, why not have the more important parts of the breadcrumb in a more visible font?

---------

"For drupal.org, I think it would be more useful to have the status value link to a handbook page that explains what the status itself means."

This could be done with a little question mark that you can click or hover.
Status (<a href="#">?</a>): active

--------

Another visibility problem (for me) is the "Issues for [module]" block on the left of each module page. I never noticed that block, I always looked on the right and bottom of the page. At the bottom there is only "pending patches", which is quite pointless to me.

Maybe there should be a link to the issue queue right on top of each module page. Maybe make it a tab?

This does seems like it would be a useful thing to add. Would be great to implement this idea!

Meta Issue - https://drupal.org/node/1080550