Hi Peter,
This looks a little too early to implement as the ticket could be
considered blocked by the non-existence of suitable models. At the
moment, the only non-ticket object that has an owner is the Component.
Components are not currently viewable in a dashboard style view but I
believe that they will be in the future.
The desire for items to gain an owner field expressed in at least one
other ticket: https://issues.apache.org/bloodhound/ticket/196 (for
Milestones) which, if accepted will likely result in the long term in
the ownership of Milestones, Versions and Products.
It is one of those annoying tickets where you basically know what should
be done but it probably shouldn't until something is available to
display. I would probably suggest re-assigning back to 'nobody' in this
case.
Cheers,
Gary
On 26/09/12 10:22, Peter Koželj wrote:
I need some more input on this one.
Ticket mentions dashboard views displaying fields that do not exist in the
model.
Reference to https://issues.apache.org/bloodhound/ticket/93#comment:6suggests
that field in question was milestone/owner.
However there are no views in dashboard that would display the non-existing
fields.
Furthermore, all views in dashboard deal with tickets only.
Am I looking at the wrong thing or is this ticket obsolete?
Peter
On Mon, Sep 24, 2012 at 6:34 AM, Apache Bloodhound <
[email protected]> wrote:
#95: Display of owner in dashboard views should depend on the availability
of
the field
--------------------------+-----------------------
Reporter: gjm | Owner: peter
Type: enhancement | Status: assigned
Priority: major | Milestone: Release 2
Component: dashboard | Version:
Resolution: | Keywords: starter
--------------------------+-----------------------
Changes (by peter):
* owner: nobody => peter
* status: new => assigned
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/95#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
