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; } } }

Provide visibility of automation rules within instance

Gary Spross

I would like to provide a way for our users to be able to see what automation rules exist within our instance. This would help avoid duplication of rules and allow useful rules that maybe someone isn't aware of to be considered for enablement within additional projects/areas.

My initial thought was to manually create a Confluence page and add details for every automation rule. This seems like a maintenance nightmare to me though. We would need to ensure anytime a rule is updated, the details pertaining to that rule within this Confluence page are also updated. If a rule is added, better remember to add it to the Confluence page. Also, need to ensure any automations created/updated by project admins are added/updated within the Confluence page...

Any thoughts/suggestions on a potential way of automating an "Automation Rule Library" Confluence page?

Accepted answers

Ste Wright

Hi @Gary Spross

I'd suggest the REST API, but not sure how much is available based on documentation, and that this feature request exists - [AUTO-51] Official REST API to manage rules, export/import and access automation audit logs

---

I've seen it done in a manual way, which was...

Global rules were documented in Confluence
Project-specific rules were only included once these were multi-Project
Rules were reviewed once per month to locate duplicates or similar rules, and switched to global/multi-project if these existed

^ Not ideal I know, but it reduces the work a small amount as Project-specific rules can often be very similar with just minor tweaks.

Ste

All comments

Ste Wright

Hi @Gary Spross

---

I've seen it done in a manual way, which was...

Global rules were documented in Confluence
Project-specific rules were only included once these were multi-Project
Rules were reviewed once per month to locate duplicates or similar rules, and switched to global/multi-project if these existed

^ Not ideal I know, but it reduces the work a small amount as Project-specific rules can often be very similar with just minor tweaks.

Ste

Gary Spross

Thanks @Ste Wright!

After creating this post I found that feature request and voted for it. It's only 3 years old, so maybe there's hope! I figured it would end up being a manual process, so I guess I'll get started! Thanks for your suggestions on how best to document.

Bill Sheboy

Hi @Gary Spross

Adding to Stephen's suggestions...

You could regularly export all rules from the global admin area as JSON, and with some parsing capture a few rule details for documentation. I recall seeing another community post about doing that, although I have not tried to create such a parser...yet :^)

Kind regards,
Bill

Gary Spross

Good thought! I'll look into writing a script to parse out the necessary data and then be able to put that directly into the Confluence document. Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud