What documentation automation would be useful?

[Mayank_FastDoc]

Hey everyone, I’m the co-founder of FastDoc, and we’ve been building something to take the pain out of documentation for Agile teams. Our mission is to help teams share what's getting released proactively, so every other team from support and sales to success can learn about changes and do their job better! 

We just launched a new beta feature that lets you automate docs using no-code rules inside our forge Jira app. A few things you can do:

• Auto-generate docs (release notes, help articles, technical docs, GTM briefs, etc.) when Jira issue work item statuses change, and publish them to a selected Confluence space.

• Automatically publish release notes when a Version or Release is marked as completed.

• At the end of a sprint, generate a sprint summary that includes comparisons with the previous sprint’s KPIs.

We started by letting users manually pick the scope, tone, doc type, and goal, and it helped save a ton of time creating first drafts. But there was still friction, since users had to remember to trigger it. So we decided to keep that option for when you need more control, but also allow teams to build automation around it.

I’d love to hear from folks here:

What else should we automate? We’ve seen some weak signals for time-based rules (for example, “summarize all Done work items every 30 days”).

If you're curious, you can check it out here: https://marketplace.atlassian.com/apps/1233783

Always open to feedback. Thanks!

[Jim Knepley - ReleaseTEAM]

Hi @Mayank_FastDoc 

I've been considering this myself, but probably won't have time to pull it together.

Your bullet list above seems to focus on creating new docs. I'm thinking more along the lines of updates.

1. A feature branch gets merged to a release branch.

2. AI evaluates that commit to see if it invalidates any existing documentation.

3. If it does, the AI creates a Jira issue to evaluate the existing documentation and suggest changes to reflect the merge.

I was thinking it would operate on markdown files in the repository, but I like the idea of it managing Confluence pages, too.

[Mayank_FastDoc]

Hi Jim, thanks for your reply. We are working on a POC for a customer that has the same use case, they have their documents in ASCII format. If you're interested in helping us shape it, I'd love to set up some time with you to dive deeper.