Where do we go from here?

[Asif Etu]

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?

[Mia Tamm _Simpleasyty_]

Hi @Asif Etu, welcome to the Cloud side! 🎉

It’s always a big step to move from DC to Cloud, and you’ll notice that while some things look different, the benefits usually come quickly — faster updates, easier collaboration, and integrations that keep growing.

If at some point you’re also thinking about taking your tables or structured data to the next level in Confluence, I’d love to hear about your use cases. That’s something I’m very passionate about, and I believe sharing experiences can really help us all get the most out of these tools.

Looking forward to seeing how your journey in Cloud unfolds!

— Mia Tamm

[Christianne Ribeiro]

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

[Mia Tamm _Simpleasyty_]

Hi @Christianne Ribeiro, thanks a lot for asking — that’s a great point.

When I mentioned “taking tables to the next level in Confluence,” I was mainly referring to use cases where teams want to do a bit more than the very basic static tables. For example:

• Project tracking tables with statuses, owners and due dates.

• Light KPI dashboards, where you aggregate information across teams.

• Budget vs. spend tables or simple resource planning.

• Or even just bringing Excel/CSV data into Confluence so that it’s accessible and easier to update.

Of course, a Data Lake is perfect for storing and analyzing large-scale structured data. What I often see is that Confluence tables are more about making a slice of that information actionable for collaboration — something lightweight and close to the team’s daily work.

Cheers,

— Mia Tamm

[David Nickell]

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).

1. Documentation and training will probably be organized by PROJECTS and ISSUE TYPES.  This "Pair" determines all the rules and fields associated with the work you manage.
   1. Some Issue Types may have complex Workflows
   2. Some Issue Types may require estimates and time entry (depending on your rules)
2. Your stakeholders will want to know expectations for eah type
3. The Dev Team always wants to know priorities and what should be done next.
4. Managers will want to know who is working on what.  

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:

---

Classic Software Projects

• 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