One of my team members and I even built a small manual, sort of instructions, on how to best use the tools, with pictures and lots of details. It was a great effort.
Fast forward to now, after nearly four years in a DC, I've just started using Jira and Confluence in the Cloud, as we've just migrated. Again, I had to investigate and prepare materials for my team to start using the tools in this new environment, UI and the new features.
So, just wanted to check with the Community, where do we go from here?
Hi Mia,
Not sure what would be "taking your tables or structured data to the next level in Confluence" as we have a Data Lake. Would you please let me know which use cases be interesting to define?
Thanks
Here is a partial Idea... It comes form my experiance of teaching other admins and training users -- but it's pretty Jira Centric (not JSM for example).
Thiose are Just a few examples.
I've done the picture below a dozen times over the years. You can use it as a roadmap for training and docs (assuming the Project/Issue Type approach).
What is the REST Angle?
You have already configured Atlassian to create screens, workflows, and everything else. Use the REST APIS (free to you) to pull that information out. And since this is 2025; pass that into an AI tool like ChatGPT to have the docs created for you?
Try this in your browser. This site is an Actual Altassian Plugin Related Instance. You may want to replace the URL with your own
https://ecosystem.atlassian.net/rest/api/3/project?expand=issueTypes
Download the JSON and pass into ChatGPT
Here is what it just told me:
Atlassian Plugins (PLUG)
Type: Software (classic, not simplified)
Category: Server Platform
Issue Types: Bug, New Feature, Improvement, Task, Sub-task, Documentation, Story, Epic.
Focus: Development and maintenance of Atlassian plugins.
REST API Browser (RAB)
Type: Software (classic)
Issue Types: Bug, New Feature, Story, Task, Sub-task.
Focus: Likely related to API exploration and tooling.
Confluence Statistics Connect (CONFSTATS)
Type: Software (classic)
Issue Types: Improvement, Task, Sub-task, New Feature, Bug.
Focus: Collecting or exposing Confluence usage/statistics.
✅ Patterns Observed:
Many are test projects or sandbox projects (e.g., “lucas-test,” “Kelvin Test 2”).
Some are archived (Watson, Albert Next-gen Project Test, Server Frontend Platform).
Larger projects (like PLUG, PAPIA, CONFSTATS) are tied directly to Atlassian product development or Marketplace workflows.
Pitfalls....The APIS are very logical (IMHO) but that probably comes from my spending years (literally) working with them. To be efficient, you will need to figure out pagination and executing the APIS in the right order.
You could use that information to build dynamic / Real time documentation. Or maybe someone has already done something like that ;-) Just a hunch.
You can find the official JIRA API Documentation online here:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#version