- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 12:26 AM
Hi Everyone,
We are working on implementing ServiceNow - Jira integration using spokes. We have established the connections and tested it.
We are able to create project/update projects in Jira. We recently had another ask from the client where we are asked to update the users as well. Now the users in ServiceNow has a different name and ID whereas Jira has different usernames and ID.
We thought of leveraging the action "Look up Users Stream by Name" which is part of Jira spoke to retrieve the username first, then make the changes and send it back to Jira.
But we are unable to figure out how above action works, currently it has two parameters i.e. Page size and username.
We tried giving pagesize as 1 and username as "akashsrivastav", but when executed, it keeps on running forever.
Can anyone help on this?
Regards,
Akash Srivastav
Here is the complete info on the action:
Retrieves a list of users that match the search string.
Note : This action is available only for Jira Server.
Inputs:
- Page Size - The maximum number of users to return per page.
- Username - A query string that is used to search username, name or e-mail address.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2025 11:19 PM
I found the cause the did the fix as well. Below are the steps that I took to resolve this...
Step 1: U must create a copy of OOB Datastream "Look up Users Stream by Name" and then replace the default credentials with your Jira authentication details.
Step 2: If you are trying to retrieve the data based on username, then it won't work, as you will run into below errors which we encountered.
{"errorMessages": ["The query parameter 'username' is not supported in GDPR strict mode."],"errors":{}}
Step 3: According to support, the username is not supported, so we have to use another parameter for retrieving user details. So, we updated the DataStream to use "query" instead of "username", and in the query we are giving the email id of the users which can be easily obtained from the user table.
Step 4: Once done, when tested you can see the user details in the output.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 01:54 AM
unless you know what that flow action does you won't know how to use
Did you open that flow action and see
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2025 11:08 PM
Hi Ankur,
Thanks for response. I did open the flow action (i.e. Datastream) and went through the docs as well, so I got an idea what its use is.
Just the thing with the syntax is where we are facing issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2025 11:20 PM
what that flow action accepts?
what you are sending?
Did you test the flow action by passing the values?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2025 11:19 PM
I found the cause the did the fix as well. Below are the steps that I took to resolve this...
Step 1: U must create a copy of OOB Datastream "Look up Users Stream by Name" and then replace the default credentials with your Jira authentication details.
Step 2: If you are trying to retrieve the data based on username, then it won't work, as you will run into below errors which we encountered.
{"errorMessages": ["The query parameter 'username' is not supported in GDPR strict mode."],"errors":{}}
Step 3: According to support, the username is not supported, so we have to use another parameter for retrieving user details. So, we updated the DataStream to use "query" instead of "username", and in the query we are giving the email id of the users which can be easily obtained from the user table.
Step 4: Once done, when tested you can see the user details in the output.