In search of the answer I managed to arrive and this result, it is not so eutomatized mes attracted me:
Strategy:
1 - Create a JSON where custom field will be created
2 - In a TESTS project or similar, create an issue where the Name of this custom field will be covered, such as ABSTRACT etc...
3 - Create an automation where fire this JSON to create each custom field in the issue creation
Strategy application:
URL:
https://your instance.atlassian.net/rest/api/3//field
1 - Creation of JSON:
{
"name": "New custom field-5",
"type": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons"
}
2 - Test project with custom name field: Field name
3 - Automation created with Scheduling Trigger for manual triggering with JQL for issues created on this date
Action:
send web request
Headers (optional)
Content-Type - application/json
Authorization - (Key of your API)
HTTP method*
POST
Web request body*
Custom Date
"Custom date"
{
"name": "{{Field name}}",
"type": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons"
}
Important, don't forget to change the customfield type according to your needs:
"adiobuttons" or "textarea" Consult the documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need Jira Admin permissions to import the data from CSV.
Thanks,
Pramodh
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.