Structure, Assets and Bitbucket - how to get control over your technical debt
Until yesterday.
Yesterday I started to work on a new schema in assets, just to map up what I actually have. I also added some information on the new category system I am setting up now so I can document what categories I have set up and the icons connected to it. As I worked on this, I also created a new Confluence space where I will document things in more detail. Since I want to have the code for the templates there and also some records of it, I realized that maybe it would not be a bad idea to connect tasks and bugs to the Assets objects.
When I created some custom fields for that and connected to my development Jira, I also figured that maybe I should not just have the code in a Confluence page, but add it to a repository so I can work with the code properly. I already had Gitlab setup and I decided to add GitHub as well since I have been using that more in the past. Once setup, I opened up Visual Studio Code and started to connect things.
I have connected to Atlassian in the past and since I am beta testing the Rovo Dev Agent, I also started to use that to help get everything set up and connected. When asked if I wanted to connect a build pipeline as well, I figured that I would go all in on the Atlassian setup, so I asked RDA to toss out GitHub and setup Bitbucket instead.
This is where the fun stuff begun, as RDA struggled hard to get the Bitbucket Pipelines setup. It went as far as RDA, saying it got frustrated and just gave up on trying to fix the code and started from scratch again! Eventually everything was set up so it works, and I now can work with the template code as actual code again, but I think RDA need a vacation after that ordeal :)
I did signup for Bitbucket standard, but the pricing seems weird. In Bitbucket, the price is $3.65 for one user monthly, but when you sign up it changes to $18.25. That is a massive change, so I will reach out to Atlassian about this and see what is going on. I am assuming there is an issue as they are merging the external Bitbucket billing to the standard billing and there can be some shenanigans happening. It should be $3.65, so I just need to confirm this.
Once the billing is fixed, I am planning to see if I can use the Snippets function as well for code snippets I use often. These are code fragments that I use for certain things in the templates that is easier to have separate, especially if I want to share it publicly as well. Unfortunately, I could not get the link to work in Confluence, so I will see if this is a limitation or if there is a setting I need to adjust.
With this setup, I now have a flow of how to deal with the technical debt and how to get rid of it. What is still missing is a naming standard and some documentation so I can clean out the many, many templates that are polluting my platform. Assets will be my starting point, Confluence will be where I document the templates and Jira where I create the tasks when I work on the templates. VS Code is where I work with the code and Bitbucket where I store the code. This would have been even better if I could actually have files to work with in the Invision Community platform, but I will just have to cut and paste into the GUI, which is fine.
Overall, I feel that I finally have a structure and a plan for handling templates now, so I just have to see how well this turn out in practice as well. For now, I have my hands full of documenting everything. I consider that a good thing, though, as this situation has blocked me and made working with the site slow, almost to the point of not wanting to do anything here at all. Now I am looking forward to working on the Atlassian release Notes database again, which I plan to add to the site again in January next year.
So thanks to Atlassian tools, I am now positive and looking forward to getting my technical debt situation under control and jumpstart my 2026 with new energy and inspiration!