Generating HTML code from a client BRD

[ALEX VARGHESE]

My client provides a BRD for a campaign through a JIRA Ticket. Can ROVO help me generate highly accurate html code using the past templates? How to setup Rovo to help me do this

[Tomislav Tobijas]

Hey @ALEX VARGHESE ,

Rovo can probably help you out here. You could build Rovo Agents to automate the process of reading BRD doc and transforming it into structured HTML based on historical data.

What I would recommend to check and to start with is this learning course: Work with Rovo agents and build your own 📚
Apart from it, there's a whole learning path that can give you a pretty decent overview of Rovo, and its capabilities: Get the most out of Rovo 

Steps for creating something like this would be:

1. Create a custom Rovo agent > see course/learning path
2. Connect the knowledge source(s) > see course/learning path
3. Enable work item collaboration > support docs
4. Prompting for the code

Hope this helps.

Cheers,
Tobi

[Nishant Paraskar]

Yes, this is actually a great use case for Rovo.

A simple way to set it up would be to store your approved HTML templates, brand guidelines, and examples of previous campaigns in Confluence. Then create a Rovo Agent that has access to both the Confluence space and the Jira project where campaign requests are submitted.

For the Rovo Agent instructions, keep it focused on tasks such as:

- Reviewing the Jira ticket requirements.
- Finding the most relevant template from Confluence.
- Following your branding and coding standards.
- Generating production-ready HTML based on the request.

You can also give the Agent a few examples of successful past campaigns so it has some context on the expected output.

If you want to take it a step further, create an action that:

1. Reads the campaign requirements from the Jira ticket.
2. Generates a BRD or campaign specification page in Confluence.
3. Uses that information, along with the approved templates, to generate the HTML.

That way the process becomes much more streamlined: Jira ticket → BRD in Confluence → HTML generation based on approved templates.

In my experience, Rovo performs much better when you provide clear examples and guidance in Confluence.

For example, I have used a similar approach where detailed test cases and validation rules were stored in Confluence. The Rovo Agent was instructed to review and follow those test cases before taking any action. This helped ensure the Agent consistently followed the expected process  at runtime.

[Germán Morales _ Hiera]

Hi @Alex Varghese, welcome to the community! 👋

Short answer: yes, Rovo can help, but the right tool depends on where your past templates live, and it's worth setting expectations on "highly accurate" up front.

If your templates are in a Git repo (Bitbucket Cloud or GitHub Cloud) → use Rovo Dev in Jira. This is the code-generation path. It reads the work item (your BRD) plus your connected codebase, generates the code, and opens a draft pull request for your team to review.

• Requirements: Jira Cloud, a connected Bitbucket/GitHub Cloud repo, Rovo Dev enabled on the site, and available Rovo Dev credit.
• Keep your past HTML templates in that repo so Rovo Dev can use them as references, and add a saved prompt pointing to the example files and your coding standards.
• It never merges on its own; you review the draft PR. You can run it on demand from the work item, in your IDE, or via an automation rule that fires when the BRD ticket is created.
• Docs: Generate code from a work item in Jira and Supported repositories.

If your templates live as documents (Confluence, Drive, etc.) → build a no-code custom Rovo Agent in Rovo Studio. Add your template library as knowledge sources, write instructions, and trigger it from Chat, the /ai editor, or an automation rule. This gives you an HTML draft from the ticket content that you copy out, rather than committing to a repo. Docs: Create and edit Rovo agents.

One reality check: Rovo produces a strong first draft, not guaranteed-correct code. Accuracy depends heavily on how consistent and clean your past templates are and how complete the BRD in the ticket is, so always review before shipping. That review step is exactly why Rovo Dev hands you a draft PR instead of merging.

Worth noting: Rovo is a Cloud-only capability. If you're on Jira Data Center, neither of these options is available.

Quick question so we can point you the right way: where do your past templates currently live, a Git repo or Confluence/files?

Hope this helps! Let us know if you have any questions.