Refreshing tickets, cutoff date, logging updates, bug fixes

[juanpablosalas]

This PR introduces a series of changes and bug fixes mainly to the handling of tickets.

Tickets

• Introduces cutoff_date for JIRA and Redmine tickets. If specified, A2rchi will pull only tickets created before that date. One possible issue with this is that the ticket changes after the creation date will still be fetched. (See Introduce a cutoff date for JIRA #362)
• Introduces frequency for JIRA and Redmine tickets. If specified, A2rchi will pull tickets updated/created since the last collection date within that frequency (in days). This update is triggered by a call to ChatWrapper. If the frequency is set to 0 it will pull the tickets again on every call. (See Refresh JIRA tickets since last pull #359)

Logging

• Reduced logging in persistence.py, vectorstore/manager.py. A list of stored resources was being logged as info but I find this to make a lot of noise (specially considering there are hundreds of tickets in each project, not to mention the crawled pages). I reduced the logging level to DEBUG so it's not completely gone.
• Reduced logging for httpx module

Bug fixes/Code cleaning

• Deletes utils section from base config template as it has been superseded by sources
• Removes outdated utils_config
• Fixed circular import issues in document index and incorrect display of JIRA tickets

[haozturk]

A bug identified, changes needed

[pmlugato]

I think we need to think a bit more about the document viewing/uploader. One reason to keep the account creation central was to control who was given the ability to add/delete documents (like you mentioned is not handled now). In general, I can think of a few permutations in which you might want the viewer to be accessible to everyone or only some, and then the same with actual uploading permissions (deploying to admins vs users, for example).

Is it a huge pain to move the account creation code to a different PR? Since ticket updating is more pressing, whereas the uploader is not, and can move this discussion/additional changes to the new PR? Let me know @juanpablosalas

With respect to the updating of the tickets, thanks a lot for getting this done quick, it is definitely essential for the deployment!

[juanpablosalas]

Hi @pmlugato, I agree with you! I think there are still some things we need to discuss regarding the document viewer so I switched those commits to #367

[haozturk]

Thanks Juan, my biggest concern with the current way of refreshing tickets is that update_tickets is a synchronous call which blocks the chat response until its termination. I think it's better to make it an async process that runs in the background. One way is to keep your implementation (trigger via chat call) and make it async or create a standalone service which periodically updates tickets. The second is a cleaner approach in my opinion and I don't know how much extra work it requires. What do you think? @juanpablosalas @pmlugato

[haozturk]

Getting the following error now @juanpablosalas

`(2025-12-10 11:10:23,531) [src.interfaces.chat_app.app] ERROR: Failed to update tickets - 'datetime.timedelta' object has no attribute 'minutes'`

Use .total_seconds() / 60 or seconds.
Also it'd be useful to add a debug logging line which tells if any ticket is updated, if so how many and so on.

[haozturk]

There's a bug and a various points to improve @juanpablosalas . Let me know when they are addressed and I'll review again

[juanpablosalas]

Thanks for the thorough feedback @haozturk , I pushed the changes