#4504 "self" variable for ticket searches

v1.0.0
closed
nobody
for-support (18) p3 (267) 42cc (432)
General
Cory Johns
2015-08-20
2012-07-05
Chris Tsai
No

I'd like to be able to set up a saved search that could return all the tickets reported by the user performing the search. Similar to how Trac uses $USER for that purpose (eg. https://sourceforge.net/apps/trac/sourceforge/report/9).

Or some other way for users to (relatively) easily find the tickets they submitted.

Related

Tickets: #4504
Tickets: #5757

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-07-13
    • milestone: limbo --> forge-backlog
     

  • Chris Tsai - 2012-10-17
    • labels: for-support --> for-support, p3
     

  • Anonymous - 2012-11-23

    Originally by: fina

    +1
    we also need this feature.

     

  • Dave Brondsema

    Dave Brondsema - 2013-03-28
    • labels: for-support, p3 --> for-support, p3, 42cc
     

  • Igor Bondarenko - 2013-04-01

    Created #311: [#4504] $USER variable for ticket searches (1 cp)

     

    Related

    Tickets: #4504

  • Igor Bondarenko - 2013-04-01
    • status: open --> in-progress
     

  • Igor Bondarenko - 2013-04-09

    We've implemented $USER variable in the searches. Now search query is preprocessed and $USER is replaced by actual username right before feeding query to solr. It works fine for tickets, however there is one problem. If $USER variable appears in 'saved search' then users will get inconsistent number of hits for this search in the left bar, due to a fact that hits are cached.

    I see two options here:

    1. Don't display hits for saved searches containing $USER (maybe display some placeholder like 'x' or nothing at all)
    2. Update counts for this searches on every request (it might be pretty expensive)

    What is your thoughts about that? Thanks

     

  • Dave Brondsema

    Dave Brondsema - 2013-04-09

    Option 1 makes sense to me. I think showing nothing at all would be fine - whatever's easy.

     

  • Igor Bondarenko - 2013-04-10
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-04-10

    Closed #311. je/42cc_4504

     

  • Cory Johns - 2013-04-12
    • status: code-review --> closed
    • QA: Cory Johns
    • Milestone: forge-backlog --> forge-apr-19
     

Log in to post a comment.