#4299 user-fields on ticket tracker function poorly [25856]

v1.0.0
closed
nobody
Tracker
2015-08-20
2012-05-30
Chris Tsai
No

https://sourceforge.net/apps/trac/sourceforge/ticket/25856

the upgraded bug tracker's assigned-to field isn't any kind of drop-down selector, so I have to remember user names exactly to enter them in there. If I enter a nonexistent username, then it just silently fails to update. Then, after I enter a correct username, the ticket will display the assigned-to field as the name of the user, instead of their username, which is a bad idea, as it doesnt help me remember their usernames at all.

I agree with the user on both points.

Related

Tickets: #1715
Tickets: #4299

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-05-31
    • milestone: limbo --> forge-backlog
     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-06-06

    Originally by: algorithms

    • labels: support --> support, v2
     
  • Chris Tsai - 2012-09-26
    • labels: support, v2 --> support, v2, p3
     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-11-07

    Originally by: zeromus

    creator should display username as well. I don't know why I called it "assigned-to" months ago, but now it seems to be called Owner.

    Perhaps this could be an option in the bug tracker field editor?

     
  • Dave Brondsema

    Dave Brondsema - 2013-02-19
    • labels: support, v2, p3 --> support, v2, p3, 42cc
    • summary: assigned-to field functions poorly [25856] --> user-fields on ticket tracker function poorly [25856]
     
  • Dave Brondsema

    Dave Brondsema - 2013-02-19

    I think we should use a "combo box" which lets people type in a username but also provide a dropdown list of choices. Most projects have a relatively small number of members, so a dropdown will work fine. (A few projects have hundreds or thousands of members, so that may take a while to generate, perhaps need to load it with ajax so it doesn't block the page load?)

     
  • Igor Bondarenko

    Igor Bondarenko - 2013-02-20

    Created #281: [#4299] user-fields on ticket tracker function poorly (3cp)

     

    Related

    Tickets: #4299

  • Igor Bondarenko

    Igor Bondarenko - 2013-02-20
    • status: open --> in-progress
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-03-05

    Closed #281. je/42cc_4299

    We've created a ProjectUserCombo widget and have applied it to the ticket's assigned_to (Owner) field.

    Seems like there are still a couple places, where old widget is used. We could change them to use the new widget too, if needed. Here they are:

    $ ack 'ProjectUserSelect' .
    ForgeWiki/forgewiki/wiki_main.py
    517:        c.user_select = ffw.ProjectUserSelect()
    
    ForgeTracker/forgetracker/tracker_main.py
    731:        c.user_select = ffw.ProjectUserSelect()
    838:        c.user_select = ffw.ProjectUserSelect()
    1707:        c.user_select = ffw.ProjectUserSelect()
    
    ForgeTracker/forgetracker/widgets/ticket_form.py
    149:        return ffw.ProjectUserSelect(label=field.label, name=str(field.name))
    
    Allura/allura/lib/widgets/form_fields.py
    84:class ProjectUserSelect(ew.InputField):
    94:        super(ProjectUserSelect, self).__init__(**kw)
    102:        for r in super(ProjectUserSelect, self).resources(): yield r
    
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-03-05
    • status: in-progress --> code-review
     
  • Tim Van Steenburgh

    • qa: Tim Van Steenburgh
     
  • Tim Van Steenburgh

    Looks good. Please replace the remaining ProjectUserSelect in the Tracker with ProjectUserCombo. Also, we should make the 'User' type custom field use ProjectUserCombo instead of ProjectUserSelect. So more specifically, update these:

    ForgeTracker/forgetracker/tracker_main.py
    731:        c.user_select = ffw.ProjectUserSelect()
    838:        c.user_select = ffw.ProjectUserSelect()
    1707:        c.user_select = ffw.ProjectUserSelect()
    
    ForgeTracker/forgetracker/widgets/ticket_form.py
    149:        return ffw.ProjectUserSelect(label=field.label, name=str(field.name))
    

    The ProjectUserSelect in the Wiki tool appears to be superfluous as it's not referenced in the template.

     
  • Tim Van Steenburgh

    • status: code-review --> in-progress
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-03-08

    Created #293: [#4299] Replace tracker's user fields with ProjectUserCombo (1cp)

     

    Related

    Tickets: #4299

  • Igor Bondarenko

    Igor Bondarenko - 2013-03-15

    Closed #293. allura:je/42cc_4299

    Changed all ProjectUserSelect's to ProjectUserCombo in the Tracker.

    On mass edit page 'user' type custom field uses standard text input, not ProjectUserSelect, so we didn't change it. If it's necessary to use a new widget there too, it should be a separate ticket, I think.

    Also, sometimes KeyError occurred on mass edit with custom fields, fixed that too.

     
  • Igor Bondarenko

    Igor Bondarenko - 2013-03-15
    • status: in-progress --> code-review
     
  • Tim Van Steenburgh

    • status: code-review --> closed
     
  • Dave Brondsema

    Dave Brondsema - 2013-04-05
    • milestone: forge-backlog --> forge-mar-22