Sorry to hear that. Good luck finding a new gig without needing to interact with Teams again.

I used to update my tickets from Emacs org-mode where I kept my working set off knowledge. The org export functions dealt with whatever format Jira expects. Nowadays I’m mostly tracking stuff so my comments are generally never more than a “thanks”, 👍 or occasionally a link to the patch series or pull requests.

Jira is alright, not great, not terrible. You need something to track projects and break down work and say least being ubiquitous a lot of people are familiar with it.

Teams is a dumpster fire of excrement though.

Ah is that what had broken my horseshoe graph? The custom graphs come up a unrecognised types whatever form I try.

My tariff comes with smart charge but I’ve ended up turning it off and just triggering directly with home assistant. I have two buttons: one for smart night time charge and one to enable daytime charge once the solar has heated up the hot water. However my current export rate (15p/kWh) is twice as good as the night rate (7p/kWh) so it’s better to bank the export and then have a steady charge over night.

Looking at the rates the OP posted I wonder if the variable tariff would make more sense. I suspect the automation rules would be a bit more complex.

There is a very large corpus of FLOSS software out there serving everything from individual itches to whole industries. Any project that is important to someone’s bottom line is likely to have paid developers working on it but often alongside hobbyists.

The project I predominately work on is about 90% paid developers but from lots of different companies and organisations. Practically though the developers don’t care about the affiliation of the other developers they work with but the ideas and patches they bring to the project.