I don’t think that features coming down the line needs much more than a regularly updated (monthly? fortnightly? however long your dev cycles last…) html page on the pathio site. It doesn’t have to be much more complicated than that, it doesn’t necessarily have to drill deep into the hows of what you’re doing, just headliners of say:
Planned for next feature release
- Cubic Subdivision infill
- Mirror controls for models and groups
- Gyroid infill
That should hopefully be a copy and paste job in the grand scheme of things.
For bug tracking and visibility, in my former job, I only ever found dedicated bug tracking software to be useful for managing bugs. Anything else becomes uncontrollable, unwieldy, and resists how you want to use it.
I personally swear by Jira, but the needs and the scale of the projects I worked on were very different to yours. For you guys, I would consider the project based things like gitlab. They have good, lightweight bug tracking implementations, and depending on the states you establish in your bug workflows, you can make it clear where dev time is going (perhaps even getting devs to comment on when they’re working on it, if you want to. Thats a double edged sword in some respects…) People are used to it from other projects too, so it doesn’t require much “user training” hopefully.
I know that there might be some duplication between what you use internally and externally, and ideally you don’t want that, but it may be worth seeing what integrations you can use or potentially develop to assist with that, migrating bugs or updating statuses between one and the other. Certainly beats tying up a person with the same task, in the long run.