•  
     
    story #41464 Convert non expert queries
Summary
Empty
Convert non expert queries
Empty

Non expert queries are converted as full TQL. Current TQL doesn't allow to express exactly what was possible with non expert mode. For instance, non expert mode allows to select

Bug from project Alpaca

Stories from project Dog

During the conversion, it will be a merge of both SELECT ... FROM @project.name IN ('Alpaca', 'Dog') AND @tracker.name IN ('Bug', 'Stories').

Converted queries have no title but have a description "Converted from simple query on 'Bug from project Alpaca', 'Stories from project Dog'" (adapted depending on context obviously).

Only "always there fields" are converted to expert mode, which imply:

  • Artifact column is split in two columns: Id (the artifact ID) and Tracker
  • Status column is removed.
  • Assigned to is also removed.
Empty
Empty
Status
Cross tracker search
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
#41464
Kevin Traini (ktraini)
2025-02-04 12:10
2025-01-17 09:23
43146

References

Follow-ups

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