Global Automation Rule | Generating New Project Spaces

Question

Hello, I'm looking for some guidance in setting up a global automation rule in Jira.

The rule will look to a specific project board (board name is PMO | Project Requests) and when a project task type of "Project Request" comes in and the label of "Recurring" is then assigned, a web request will be made to create a new software project space with the same title as the project request, the title of the new project space will have the project request "ID" appended to the front of the title.

Example new space title " "original project request task ID" | "original project request title "

I'm having such trouble with setting up the web request within the automation rule specifically, pointing it to the proper Web Request URL, HTTP method I should chose, Web request body I believe is custom. I also have trouble getting the custom data just right to complete all I'm trying to accomplish. Also headers, should I be using headers?

Should I be doing this under global or studio?

Any help is much appreciated!

Sami Shaik · Answer

Hi @Kaitlyn Hoban , @Josh rule shape is the one to build, and @Aaron Pavez [ServiceRocket] “prove it in Postman first” is the right order. Two additions from the Create project reference as it reads today, both about making @Matthew Sinclair point (“company-managed, standardised schemes”) actually happen. 1. Add projectTemplateKey, or you do not control what gets created. The endpoint’s only required fields are key and name. projectTypeKey and projectTemplateKey are optional, and if you leave the template out, Jira picks one for you. The reference lists the software templates by name, and the names tell you which style you get: * com.pyxis.greenhopper.jira:gh-simplified-scrum-classic and gh-simplified-kanban-classic create company-managed spaces (the “classic” ones). * gh-simplified-agility-scrum, gh-simplified-agility-kanban and gh-simplified-basic create team-managed spaces. So the body becomes, for a company-managed Scrum space: {"key": "PR{{issue.key.substringAfter("-")}}", "name": "{{issue.key}} | {{issue.summary}}", "projectTypeKey": "software", "projectTemplateKey": "com.pyxis.greenhopper.jira:gh-simplified-scrum-classic", "leadAccountId": "{{issue.reporter.accountId}}"} 2. Pin the schemes in the same call. The same request body accepts permissionScheme, notificationScheme, workflowScheme, issueTypeScheme and issueTypeScreenScheme as scheme IDs (fieldConfigurationScheme is marked deprecated on the page). Pass your standard PMO scheme IDs and every space the rule creates lands on the same configuration, which is the only way “standardised schemes” survives contact with a rule that runs unattended. Read the IDs once from the scheme pages in Jira settings, or from the matching REST endpoints. On the credential. The endpoint needs the Administer Jira global permission, so whoever owns the API token in that header is a Jira admin for the life of the rule. Use a dedicated service account with that one permission, not a person’s token, and tick Hide on the Authorization header so the token is masked in the rule editor and audit log. There is no secret store in automation yet; the suggestion for one (AUTO-1365) is still gathering interest as of its 29 September update. Reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-post

Tomislav Tobijas · Answer

Hi @Kaitlyn Hoban ,

This is a bit more advanced stuff, but a few years ago, someone did something similar > you can check the article here: Let's automate project creation using Jira Automation! 👈

It's a bit outdated, but the concept should be similar.

Cheers,

Tobi

Josh · Answer

Hi Kaitlyn, building on Matthew's advice to test in a sandbox first, here is the rule shape. A rule scoped to the PMO space is enough; it doesn't need to be global.

Trigger: Field value changed → Labels. Conditions: Work item type equals Project Request, and Labels contains Recurring.

Action: Send web request

URL: https://YOURSITE.atlassian.net/rest/api/3/project

Method: POST, body: Custom data

Headers: Content-Type = application/json, and Authorization = Basic plus the base64 of email:api-token for an account with the Administer Jira permission.

Custom data:

{"key": "PR{{issue.key.substringAfter("-")}}", "name": "{{issue.key}} | {{issue.summary}}", "projectTypeKey": "software", "leadAccountId": "{{issue.reporter.accountId}}"}

The key must be unique and use uppercase letters or digits, which is why it's built from the request number. Tick "Delay execution of subsequent rule actions until we've received a response" and log {{webResponse.status}} and {{webResponse.body}} while testing, so any error shows in the audit log.