•  
     
    story #10703 define a query with "people" fields
Summary
Empty
define a query with "people" fields
Empty

This story apply on following fields:

  • submitted_by
  • last_update_by
  • assigned_to

The 2 firsts are "Always There Fields" while the later is defined by semantic. Specificities of ATF are described in the epic.

For those fields:

  • Can use =, !=, IN, NOT IN operators
  • None and '' (empty string) should be taken into account (same behaviour than on single tracker)
  • Can use MYSELF() function
  • Search is done on username
  • Field/semantic must be readable in all trackers of query

For "assigned_to" semantic:

  • In single-tracker TQL search, given a list field is bound to a user group, for example 'Project Members', when I search a username 'johndoe' and 'johndoe' is not a 'Project member', then an error is shown to tell me that 'johndoe' is not a valid value for this field.
  • In cross-tracker TQL search, that check is not made. Searching on 'johndoe' will yield 0 results because 'johndoe' is not a 'Project member'
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#10703
Manuel Vacelet (vaceletm)
2018-04-23 16:50
2017-09-29 14:15
4448

References
Referencing story #10703

Git commit

tuleap/tuleap/stable

In and Not In should be a valid operator but unsupported by any field 6565f4a910
Add @submitted_by as a supported metadata e12b8bb6cf
Deal with = for submitted_by 915c4be165
Deal with ! = for submitted_by 83a0502a36
Check that all trackers use a subby field (readable) a97a1653d1
Empty string should be allowed in Equal and NotEqual b0e76e58d4
Deal with IN() for submitted_by 7ef981cba4
Deal with NOT IN() for submitted_by feea6d17ab
Add simple REST tests to ensure that no fatal error is thrown 830e4a4713
Add ATF luby in grammar 62f2f0d3c8
autocomplete and syntax highlight @last_update_by 531ddfe52a
Accept MYSELF() keyword 697ccc98c3
Deal with IN and NOT IN for ATF last_update_by 943befa7d2
Check that all trackers use a luby field (readable) a67b1a363d
Add 'Assigned to' semantic to grammar a965fe473d
Add simple REST tests to ensure that no fatal error is thrown a1b03a7248
Deal with = for assigned_to semantic 9b02c63d95
Deal with != for assigned_to semantic bd03c84bab
Check that all trackers have the assigned to semantic 9f8ac27bd7
Deal with IN() for assigned_to semantic d5b2db5b80
@assigned_to = empty string should only return selected trackers 5011a99890
Deal with NOT IN() for assigned_to semantic a7af7648bb
Add a simple REST test juste to ensure that not fatal error is thrown 6ecf16a8dc

Follow-ups

User avatar
Joris MASSON (jmasson)2018-04-12 10:03
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Permissions set to