Feat/meta data v2

[ankitsmt211]

Adding more data from help threads to our already existing table, along with listener that updates changes done after thread creation.

• [x] Alter Help_Thread table
• [x] Update write operation to db with extra fields
• [x] Update ticket status and closedAt when thread archived/closed.

Additions:

• [x] update message count per thread
• [x] members participated per thread
• [x] routine that settles ticket status due to hiccup

[marko-radosavljevic]

Seems fine, doesn't really resolve #660 since we are not using or displaying this data. So probably a fresh issue should be created with how to move forward with interpreting and displaying this data in a meaningful and nice way, UI wise. ^^

[ankitsmt211]

Seems fine, doesn't really resolve #660 since we are not using or displaying this data. So probably a fresh issue should be created with how to move forward with interpreting and displaying this data in a meaningful and nice way, UI wise. ^^

True, imma remove the referenced issue.

[ankitsmt211]

the code itself is fine, but the system has a crucial problem. it is not resilient at all. thread status will be incorrect in case of issues:

• if an update message is missed bc of error, the thread remains "open" in the DB
• if the bot is offline and turned on after a few days again, threads that have been closed remain "open" in the DB

there should be some sort of routine that checks threads that are marked open but are older than three days, just to make sure the metadata remains correct

should it also update other data? like message count/participants from already closed thread? or just status?

[sonarqubecloud[bot]]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud