434
Views
7
Comments
[JIRA Connector] Create Issue with custom fields?
Question
jira-connector
Web icon
Forge asset by OutSystems MVPs
It's possible create Issue with values for custom fields?
2024-01-22 15-21-29
Pedro Cardoso
Hello ALberto,

yes it is, but you'll need to change the connector to fit your custom fileds.

Cheers,
Pedro Cardoso
2013-01-21 18-58-15
Alberto Granja
Hi Pedro!

Could you help me telling which is the connector?
2024-01-22 15-21-29
Pedro Cardoso
Hello Alberto,

I meant that you need to change the Jira connector itself. I would advise you to clone the existing one and start from there.

After that, it depends on what you're planning to do: creating or listing issues. You'll have to read the documentation of the Jira REST API to understand how to use your custom fields and where.
UserImage.jpg
Salil Agrahari
Hi Pedro,

As you mentioned in your post, where we can get the documentation of the Jira REST API.

Thanks.

2024-01-22 15-21-29
Pedro Cardoso
Hello Salil.

You can check the documentation in JIRA https://docs.atlassian.com/jira/REST/latest/

Cheers
UserImage.jpg
Salil Agrahari
Thanks, Let me read !
2019-03-13 07-21-40
Adrian

Dears,

This is what you need to do to be able to create Issues with custom fields:


1) First find out what JIRA keys your installation uses for the custom fields you want to use. For instance the custom field Epic Name is mandatory for Epics but has different keys depending on the environment. Use Postman or SoapUI to find out what these fields are with the url below for JIRA Cloud installations. Don't forget to configure basic authentication of course. 

In my case I am interested in a couple of custom fields:

  •  "name": "Epic Name", "key": “customfield_10002",
  • "name": "Epic Link","key": “customfield_10005"

2) Add each custom field as a Text attribute to the IssueFields structure in JIRAConnector

Good luck!

Best regards,

Adrian


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.