•  
     
    story #38648 Choose my own columns based on semantics and always there fields
Summary
Empty
Choose my own columns based on semantics and always there fields
Empty

The TQL grammar is extended with a SELECT keyword that precedes the previously existing "filtering" conditions. I can write several field names (separated by commas ,) from the selected trackers.

SELECT is optional (to maintain backwards-compatibility of TQL language). When it is absent, the default set of columns is shown: Tracker badge and artifact title, Project label, Status, Last update date, Submitted by, Assigned to.

SELECT @id, @title WHERE @last_update_date > NOW() -1m

The previous example will show two columns @id and @title. Those columns will show the artifact values for always there field artifact id and semantic title.

Allowed semantics:

  • @title
  • @description
  • @status
  • @assigned_to

Allowed always there fields:

  • @submitted_on
  • @last_update_date
  • @submitted_by
  • @last_update_by
  • @id

A given field (for example @id) can only be selected once. For example SELECT @id, @title, @id will raise an error.

Figma mockup: https://www.figma.com/design/oDjT4tC3fDGP5P4JdKfkdE/Columns-choices---ST?node-id=67-21319

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
#38648
Kevin Traini (ktraini)
2024-10-17 10:17
2024-06-27 15:51
40333

References
Referencing story #38648

Follow-ups

User avatar
Joris MASSON (jmasson)2024-10-17 10:17
  • 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
  • Is related to
    • Added is Covered by: