Hi i am new to Automation for jira plugin. Is there any documentation available like best practices to use Automation for jira available. I have googled it but couldn't find an exact document. Here is what i found while googling.
1.https://confluence.atlassian.com/automation/concepts-993924598.html.(Mostly the concept is explained here)
2.https://support.atlassian.com/cloud-automation/docs/best-practices-for-optimizing-automation-rules/(Best practices for optimizing automation rules).
Can anybody give me a perfect document for best practices for using Automation for jira plugin.
Thanks in advance.
I do not believe there are "best" practices for any tool; only better ones. How your teams use it depends on what your teams need to support Jira usage.
Here are some things I have found may help with automation usage:
These are all really good tips, @Bill Sheboy
Both Documentation and Backups are a really good idea.
Once you have that backup file (example: automation-rules-202201121937.json), this jq comand will extract Name, Description, Status (enabled or not), ID, Project ID, and Trigger Type and convert it to a CSV, which could be imported into Excel or Google Sheets, which would be a great starting point for documentation:
jq -r '.rules | [.name, .description, .state, .id, .projects.projectId, .trigger.type] | @csv' automation-rules-202201121937.json > rules.csv
So rules.csv will look like this:
"Add request participants",,"ENABLED",1819286,"10001","jira.manual.trigger.issue"
"Approvers to Watchers",,"ENABLED",2361087,,"jira.issue.field.changed"
"Assign to First Commenter",,"ENABLED",1578948,"10001","jira.issue.event.trigger:commented"
"Changelog / Multiselect fun",,"ENABLED",1567973,"10001","jira.issue.field.changed"
One problem with this is that you'd need to look up Project ID. If you export the list of Project and IDs this is pretty easy to do with a lookup table in Excel or Google Sheets.
To get list of Projects and IDs (50 at a time):
If you save that as a file (projects.json), jq lets you convert that output into a CSV with ID and Project Name, which would work great as a lookup table:
jq -r '.values | [.id, .name] | @csv' projects.json > project.csv
I could write a whole article on JSON and Automation Rules... (It's been in the works for a while. :-)
Another idea that I've not actually implemented is using jq to just nicely format the JSON from the export file, and then checking that into a source code repository tool like Bitbucket or Github. (This command would just be:
jq -r '.' automation-rules-202201121937.json > formatted-rules.csv
If you did uploaded each backup as a new version, you would be able to use built in tools to see changes/differences as you add/edit rules.
I've done this kind of comparison manually between sandbox and production environments and it was helpful in looking for errors in complex rules.
Please check this out Best Practices Link about Automation for Jira Plugin https://blog.codebarrel.io/10-tips-best-practices-to-get-started-with-automation-for-jira-b423e6868595
Also take look at Automation Library here https://www.atlassian.com/software/jira/automation-template-library
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events