There’s nothing terribly complicated about what I’m posting today, but it’s been a while since I put out an update.
The challenge today was to create a sort of interlocking series of issues, using a listener. That is, the listener listens for an issue to be created. It creates a bug and an epic within the same project. It then sets the epic link of the original issue and bug to be the newly created epic. It was also an exercise in balancing efficiency with readability. Certainly, there are much more efficient ways this script could have been written. But I think as an example, it’s fairly readable, and that has value too.
//Example Listener for Jira Cloud - Create Bug and Epic Automatically //Author: Ken McClean / email@example.com //Script functions: // - Script runs as a listener // - On issue create, script creates a new epic // - It also creates a new bug // - The script then sets the epic link of the original issue and the new bug to be the newly created epic //References: //https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post //https://library.adaptavist.com/entity/create-subtasks-when-issue-created //BEGIN DECLARATIONS: final bugTypeID = "10008" final epicTypeID = "10000" final epicNameField = "customfield_10011" final epicLinkField