AI Initiative Issue Tracker

Note that Val has been working on this.

I've made several commits to the repo with the following results:

• Added cache tags to the calendar view. That fixed stale cache when issues are added/updated
• Added d.o. userid field to contributor content type. This reduced the number of calls to the API
• Added static caching of user and node data when processing a project
• Added drush commands to process single module and all modules
• Process single module configuration using Drupal queues. First thing that is done by drush command is populate the queue, so even if the drush command fails for any reason, the queue can be processed later
• Handle "429 Too many requests" responses from API (up to 3 retries with 30 seconds delay before finally giving up)
• Added contributor now shows in the dashboard

Regarding timeouts, the proper way to overcome this would be to run the imports in scheduled cron jobs, but unfortunately, DF does not support that yet.

• The admin tools buttons.
• The Sync buttons in the drawer.
• Would be good for us to keep a record of when we last did an update - we have this now in Drupal state (ai_dashboard:last_import:).
• .
• Bring issues form previous week button disaappears if you are on the current week.
• Would be good for us to keep a record of when we last did an update - we have this now in Drupal state (ai_dashboard:last_import:).
• Filtering by Component isn't working yet.
• I had timeouts (been having issues with things lasting more than 5 mins timing out and causing issues on drupalforge but not locally. So maybe do things in smaller batches?
• Maybe we should add functional tests and figure out how to handle them?

Ok therre are some bugs

- Bulk operations don't work.
- I tried to hide the buttons for Sync, delete from week and bring from last week for non-admins, but its just got rid of them entirely.
- Assigning still ddoesn't work well without rebuilding the cache

Any substantial tasks can be spun out into child issues if you'd like.

- TODO - Make a child issue for the tracker extra meta data format and issue template we want to use.

Things I've done:

- I've created the structure for adding meta data and due dates, etc. But it doesn't integrate yet.

Things left:

- Make the import make use of the new structure (due dates, summaries etc.)
- Create a "Priorities Page" which is similar to marcus' google doc but more automated for priority tasks each we need need reviewing or doing etc.
- Figure out how to display everything in terms of workstreams and epics.

Future todos:

- Automatic Syncing with the contributors google sheet.
- Have AI summarise what each company is doing each week so we can have a very top-level summary.
- Have a page that gives a newsletter for daily summaries of what has been doing each day by looking at commit history.
- Have the metadata of blocker issues so we can built gantt charts.

• I had timeouts (been having issues with things lasting more than 5 mins timing out and causing issues on drupalforge but not locally. So maybe do things in smaller batches?
• Marcus has a brief summary on his meta issue of each issue, can we use some kind of standard syntax for summary that we pull into Starforge? (One Line Summary: ) for example.
• We should have another calendar view for Management style tasks (Marketting, etc).
• Ideally going forward, we would update the assignments for the beginning of the week and then do all pulling in updates to the following week. (Would be good for the website to maintain some kind of history).
• Be good if we could facilitate Marcus' planning doc on Starforge.
• Need to have "Epics" or "Tracks" and show all the issues in a track, all the (not done issues) and start doing burndown charts.