Summary: | Bugzilla XML template missing useful information | ||
---|---|---|---|
Product: | Gentoo Infrastructure | Reporter: | Mark Loeser (RETIRED) <halcy0n> |
Component: | Bugzilla | Assignee: | Bugzilla Admins <bugzilla> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | LpSolit |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mark Loeser (RETIRED)
![]() LpSolit, could that be interesting for you guys? I'm not sure... Somehow yes because the onmouseover (javascript) shows the status as well but on the otherside I think its better to query the bug if needed. (In reply to comment #1) > LpSolit, could that be interesting for you guys? Hum, I don't think so. The XML file is about a single bug. It's not the right place to put additional information about other bugs. Some people may ask for the assignee as well, or any other information related to dependent bugs. It's better to get the XML file of the other bug if needed. I'd expect the information that is present from the UI to be identical to what is in the XML. Knowing whether or not a blocker/dependency is open is something presented currently on the site, since it wouldn't make sense to have the user go to every single bug to check its status. I don't think it's a good idea for us to patch this in, possibly making bugzilla interfaces specific to 'our' API. |