Hello,
I use JIRA with n8n. I want to avoid JIRA automation rules, since i"m limited to 5000 per month, and it goes fast.
I used a jira automation rule that attach a form to he issue after a statut transition.
In n8n, there is no JIra nodes available to do that task. I tried with a HTTPS request node, but don't work.
Is there a way to attach a form automatically without a jira automation rule?
Hi @Loic
As mentioned by @Sunny Ape
If the issue is already created in Jira, you could add a form to this issue, using the Forms API.
@Marc -Devoteam- and @Sunny Ape
As per the below link, the API works only with JSM.forms and "Advanced Forms" (i.e. Proforma Forms).
https://developer.atlassian.com/cloud/forms/rest/intro/#about
That makes me suspect that it will not work with the forms natively available in Software and Business projects, as that forms engine is different from the JSM/Proforma Forms engine.
I haven't had time to test that out. Have either of you tested it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Marc -Devoteam- @Trudy Claspill
I just tested it. It works!!! Thanks a lot.
I was able to attach JSM form (The yellow forms) via n8n with HTTPS node. Work perfectly.
Thanks for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Loic
You have mentioned in a few posts your concerns about automation usage. You have said you get only 5000 rule executions per month.
I see also that the tags on your post indicate you are using a Premium subscription.
If that is correct then according to the following document you should have 1000 rule executions per licens d user per month. That would mean you have only 6 licensed Jira users. Is that correct?
https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/
If not, then from where are you getting the information that you have a limit of 5000 executions?
Have you used the usage calculation information in the above document to examine you rules to see if you can reduce project scope or use Conditions or use Schedule triggers to reduce the number of rule executions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
I now have Standar plan, because we are only 2 users for the moment, we are in development and testing phase. But even when in production we will be 5 or 6.
I used a lot of automation, but now I have analyse all my automations rules, and I can for most of then incorporate them in my n8n workflows.
Also most of my n8n webhook workflows are triggered by status transitions, so I will move them in the corresponding transition Post-functions to trigger them.
So if I can incorporate them in n8n, the rule execution limit will no longer be a problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Currently, Atlassian does not provide a public REST API for attaching JSM forms to issues. The Jira Cloud platform REST API does not list endpoints for JSM forms.
AFAIK the only feasible way is the automation rule, here are steps to do so:
In your Jira project, click on Project settings in the sidebar.
Select Automation.
Click Create rule (or Add rule).
Choose the Issue transitioned trigger.
Configure it for the status change you want (e.g., from “To Do” to “In Progress”).
Click New action.
Search for and select Attach form to issue (this is available in Jira Service Management projects).
Choose the form you want to attach from the dropdown list.
If you only want to attach the form under certain conditions (e.g., only for specific issue types), add a Condition before the action.
Give your rule a clear name (e.g., “Attach Form on Status Transition”).
Click Turn it on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks, but I want to avoid using jira automation. I'm limited to 5000 executions, and they go fast. I have to limit them and only using them if I have no choice... Looks like its one of those :(((((
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @yqiao
Currently, Atlassian does not provide a public REST API for attaching JSM forms to issues.
Are you sure?
Why can't @Loic use the Forms APIs to attach a JSM form to an Issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If your goal is specifically auto-attaching a form after a transition without consuming Jira Automation runs, Smart Forms can handle that automatically at the project/issue-type level.
You can configure a form so it appears on the issue as soon as it is created — even if the issue is created by n8n or another integration.
This avoids the need for Automation rules altogether:
Setup:
Smart Forms → Settings → Add to issues automatically → select project + issue type.
Once enabled, the form just appears on every issue of that type — no rules consumed.
Since Smart Forms allows you to update issue status after submission, you can even chain workflows without automation rules.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.