Auto Created Front End and backend tickets have the same name (at least append Front End or Back End to the Name) and are all assigned to the same repo (first one in list).

[glind]

Tickets created via auto-creation always have 2 Front End and 1 Back End ticket (so far in testing). They also share the same name for each ticket and description. We need to append Front End and Back End to the name where appropriate. They also are all left unassigned to a repo or default select the first repo. We need to know when repo is Front End at least and then try to suggest a backend repo based on the repo name and any occurrence of all or part of that repo name in the ticket.

[glind]

Also when these are updated to go to the appropriate repo in the Insights interface they do not move.

[odenypeter]

@glind I think this is more of manual process coz I think these tickets are added directly to the DB

[glind]

This is the process I am talking about. They don't generate unique names

[glind]

It also seems to suggess 2 FE tickets every time now at least in Dev never a backend ticket

[patelradhika]

@glind The tickets created by this process are assigned to the first repo as they are created automatically without taking the repo input from the user. As for the suggestions that logic is on the BE so need to check that.

[glind]

@patelradhika Let's try and work out the logic in the backend so we know what repos are available if we are connected to github. Something like this.

Split Feature into Issue Call: (This could also be a direct call to gemini) should look for repos and create a name via gemini or babble beaver.

be_ticket_name = babble_beaver_suggest_issue_name_be(feature.description)
fe_ticket_name = babble_beaver_suggest_issue_name_fe(feature.description)

IF github:
be_repo = tensor_flow_suggest_repo(github, be_ticket_name)
be_ticket_assign(be_ticket_name, be_repo)
IF buildly_react_fe in repo_list THEN
fe_repo = "buildly_react_fe"
ELSE
be_repo = Default
fe_repo = Default