•  
     
    story #32281 Search artifacts with/without parents via TQL
Summary
Empty
Search artifacts with/without parents via TQL
  • Find user stories that don't have parents: WITHOUT PARENT

  • Find user stories that have parents: WITH PARENT

  • Find user stories that have parent "artifact #123" as parent: WITH PARENT ARTIFACT = 123

  • Find user stories that have parent in epic tracker: WITH PARENT TRACKER = 'epic'

Empty
Empty
Empty
Status
Empty
Done
Development
  • [x] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [x] 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)?
  • [x] Is it exploratory?
Empty
Details
#32281
Nicolas Terray (nterray)
2023-06-26 09:40
2023-05-31 19:13
33870

References
Referencing story #32281

Git commit

tuleap/tuleap/stable

refactor: Remove Visitor & Visitable interfaces f4362d32f8
refactor: Enforce signature of ValueWrapperVisitor ed5c66ea13
refactor: final, final everywhere e6b3b924f5
feat: Introduce WITH PARENT 351ae4d553
feat: Introduce WITHOUT PARENT 9a01ebce13
fix: Fatal error for TQL with parenthesis 189fea26db
chore: Argument type does not match the declared docblock 0c8548229b
feat: WITH|WITHOUT PARENT in CrossTracker 136707c6c1
feat: WITH|WITHOUT PARENT ARTIFACT a64a82dcbc
feat: WITH|WITHOUT PARENT TRACKER 0f0aa8d90a
refactor: move IProvideParametrizedFromAndWhereSQLFragments to Tracker b573266d3d
refactor: Report monstro query goes EasyDB 6f1743ceea
refactor: Add documentation/tests for Option::match() c212512744
debug: log failing query 4bb61150ea
fix: Fatal error when too many artifacts on a table 0c726b15f6

Follow-ups

User avatar
  • So that
    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
  • Status changed from On going to Done
User avatar
  • So that
    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