Hello everyone! Im trying to automate a Custom Field in JSM from a Microsoft List. In the list we have 150+ locations which I want to be able to select in the Custom field. I have set up a Power Automate flow, connected the list and got GET and POST to work, however im not sure this is the best approach? I also want to be able to Delete and change an entry if its name is updated in the list (post will only add a new entry if the name is changed) Current Setup: Power Automate flow, connected to MS List. Trigger: "When an item is Created or Modified" -> HTTP with GET -> HTTP with POST (successfully adds new entries but doesnt change name or delete entries) Using URI: rest/api/3/field/customfield_100xx/context/102xx/option which get my CustomField including the Values. (more specific: "id": "10147", "value": "TestLocation", "disabled": false If anyone has any experience with this, I'll gladly listen to ideas! Cheers!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automatically update CustomField using Rest API and Microsoft List

Tim Posselwhite

Hello everyone!

Im trying to automate a Custom Field in JSM from a Microsoft List. In the list we have 150+ locations which I want to be able to select in the Custom field.

I have set up a Power Automate flow, connected the list and got GET and POST to work, however im not sure this is the best approach? I also want to be able to Delete and change an entry if its name is updated in the list (post will only add a new entry if the name is changed)

Current Setup: Skärmbild 2025-01-20 130254.png

Power Automate flow, connected to MS List.

Trigger: "When an item is Created or Modified" -> HTTP with GET -> HTTP with POST (successfully adds new entries but doesnt change name or delete entries)

Using URI: rest/api/3/field/customfield_100xx/context/102xx/option which get my CustomField including the Values.
(more specific:

"id": "10147",
"value": "TestLocation",
"disabled": false

If anyone has any experience with this, I'll gladly listen to ideas!

Cheers!

Accepted answers

Marc -Devoteam-

Hi @Tim Posselwhite

API options to change are available, see:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-configuration--apps-/#api-group-issue-custom-field-configuration--apps-

You have the option to POST and GET (as you use), you will need to use the PUT option.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options/#api-rest-api-3-field-fieldid-context-contextid-option-put

All comments

Marc -Devoteam-

Hi @Tim Posselwhite

API options to change are available, see:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-configuration--apps-/#api-group-issue-custom-field-configuration--apps-

You have the option to POST and GET (as you use), you will need to use the PUT option.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options/#api-rest-api-3-field-fieldid-context-contextid-option-put

Tim Posselwhite

Hi @Marc -Devoteam- Thank you for your reply.

I have seen the documentation and tried to apply everything needed. Im probably not smart enough

What I cant get my head around is that to delete an entry, I need to have two values, both the ID and the Name. And compare the values between the MSList and whats already in the API list somehow.

I don't know very much of JSON scripting..

Marc -Devoteam-

Hi @Tim Posselwhite

Why delete an entry?

This will remove the information from the Jira issue, best practice is to disable the option, then it can't be used anymore on a JIra issue, but it wil retain the information for searching and maybe reporting.

Tim Posselwhite

@Marc -Devoteam- oh Thank you, I didnt think of that. Was exacly why I asked in the first place to get some good practises along with suggestions.

I agree that deleting will also remove valuable information, will look into PUT and disabling the options instead of removing!

Again, thank you for your responses

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management