nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to track bugs in Confluence knowledge base for our support team

Capps

We are using Confluence Cloud as our internal wiki for our support team.

Whats the best way to record known bugs from our developers so that they can easily be seen in a "page" (maybe) for our support desk team.

What I want to achieve is a single source of truth in our Wiki for the support team.

Accepted answers

Peter DeWitt

@Capps , I would keep the bugs in Jira and then use the Jira Issue Macro in Confluence to display each item. You can structure the JQL so that only open bugs are displayed.

-pjd

All comments

Peter DeWitt

@Capps , I would keep the bugs in Jira and then use the Jira Issue Macro in Confluence to display each item. You can structure the JQL so that only open bugs are displayed.

-pjd

Dan Winkler_0y432l

I echo @Peter DeWitt's answer, and we use the macro to track our release notes in Confluence.

A Jira admin creates a filter to track fixed issues, known issues, etc, then sends me the filter number, which I plug into the macro on our Confluence Release Notes page. The issues in Confluence automatically update whenever they're changed in Jira, so they're always current. It's the source of truth for our releases, and it's one of our most popular pages.

Capps

Thanks very much 👍🏻

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence-cloud