to modify

[Rashmi-AB]

llama http link parser AI loading animation visibility to customers vs merchants visibility among teams ticket visibility profile/user evaluation logic with ml git lab changes analyzer fine tuning Jira data to developments About previous analysis

fix and integration DB socket IO connectivity issues ticket modify problem authentication view js store logic

[jesvijonathan]

• ticket update not working for activity-chat, etc fix
  • working fine locally (check Update route, gcs bucket can be created/deleted but not modified, try replacing or deleting before adding or overwritting)
• link parser error
  • working fine locally (have to check on deployed version)
• json extractor/parser
  • (we can use controlled resoposne but it cant be used conversationally, maybe on /create we can pass that parameter and get that response)
• Vertex quota limit fix
  • so trial account has fixed quota, nothing can be done... we should switch to worldline gcp account to get no quota deal
• about page
  • done
  • ai loading animation
  • done
  • pagerduty/serviceline data importer
  • Done (Support csv import and also json data)
  • llama (http & container)
  • done
  • get ticket from db with medium as email and complete inbox
  • working on it

[jesvijonathan]

yet to-do/issues :

chatbot infinity loop visibility to customers vs merchants visibility among teams ticket visibility profile/user evaluation logic with ml git lab changes analyzer fine tuning Jira data to developments previous analysis DB ticket modify problem authentication view js store logic

[jesvijonathan]

/create ticket/ [form -> json ] [json.attachments -> []] [attachment->data]

/get_tickets/ -> medium (email/portal-chat) /attachment -> (url return (gcs) / )

/update or /modify ticket -> (attachent / )

[jesvijonathan]

Will be done next -

chatbot infinity loop bucket implementaion gcs url fetch profile evaluation authentication/profile using stores & data gitlab changes inbox logic

full db

jira integration deployment