ServiceNow Jira Spoke: Connect and Test 

Stay tuned! There's more coming!

Hello! First thank you for watching! The username I was using is from Jira. The connection and credential should be for a Jira account with admin-level permissions. I hope this helps you and your integration!

Thank you thank you! I try to walk through what I'm going to share here in this comment roll-up video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-SSRnomApE6A.html. But essentially when you create an issue in Jira using the spoke, you need to store that key on the related incident record in ServiceNow. And on the Jira side you probably want to store the Incident number in a field in Jira. This way no matter which direction you're pushing/pulling from, you have the foreign key of the other system. I hope this helps you - thank you for watching!

Hi Suzi - thank you for watching! I haven't done that before but will add it to my list for sure - stay tuned!

Hey there, thank you for watching and leaving a comment! I had a similar question to this one and answered both in this comment response video if you're interested in watching (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-0qm5fbgXA6E.html). Simply put, there are some dynamic inputs (like the project key dropdown) in that spoke that require the connection to be working so I would (1) ensure your configured connection and credentials are working and (2) ensure the Jira account you're using has admin-level access to the Jira instance. That's where I'd start!

I have a suspicion that the reason that additional fields box is grayed out is because the dynamic inputs are failing. Have you ensured that (1) your configured connection and credentials are working and (2) the Jira account you're using has admin-level access to the Jira instance? That's where I'd start. If you're interested, I spent a lot of time in my comment response video trying to find an instance where my credentials were working but had no luck haha - but I think one of those two things might be the issue. Here's a link to the video where I respond to your comment: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-0qm5fbgXA6E.html

Yep that can happen! The table is discovery_credential and you just need to increase the field length of the password field. I cover this step-by-step in this video (the link should go to 12:23): ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-37iJjKz94Qw.html

@@JustinMeadows Hi Justin, I tried testing the Metadata jira action after creating credentials as suggested. But it is not returning any data (No project, No issue). There is no error. Do you know what can be the reason?

Is the user you're using a Jira admin? That would be the first thing I check.

Hi there! The username and password should be a Jira admin account. The password is typically an API token.