Hi. Trying to find a way to pass additional fields using create issue in Jira Spoke, additional field option is currently greyed out, do we need to create any additional steps to get all fields from Jira to map between SNOW and Jira for Create issue?
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: ua-cam.com/video/0qm5fbgXA6E/v-deo.html
Hi, once again thanks for another great video, it is very very helpful. Quick question Justin please - do you know how can I get the issue key (Jira ticked number) from Jira and update the incident that is linked to that issue with using Jira spoke? Kindly advise please
Thank you thank you! I try to walk through what I'm going to share here in this comment roll-up video: ua-cam.com/video/SSRnomApE6A/v-deo.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!
Can't create Connection after using related link Create new Connection & Credentials. It says API key length is too long. Increate field length. Where is that field?
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): ua-cam.com/video/37iJjKz94Qw/v-deo.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?
Hi, can you do a tutorial for an Oauth connection? Thank you
Hi Suzi - thank you for watching! I haven't done that before but will add it to my list for sure - stay tuned!
Hi Justin. Does this work for on premise Jira instance? One thats not hosted in the Atlassian cloud but it's n AWS instead?
Hi. Trying to find a way to pass additional fields using create issue in Jira Spoke, additional field option is currently greyed out, do we need to create any additional steps to get all fields from Jira to map between SNOW and Jira for Create issue?
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: ua-cam.com/video/0qm5fbgXA6E/v-deo.html
Hi, once again thanks for another great video, it is very very helpful. Quick question Justin please - do you know how can I get the issue key (Jira ticked number) from Jira and update the incident that is linked to that issue with using Jira spoke? Kindly advise please
Thank you thank you! I try to walk through what I'm going to share here in this comment roll-up video: ua-cam.com/video/SSRnomApE6A/v-deo.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!
Thanks Justin!
Stay tuned! There's more coming!
Can't create Connection after using related link Create new Connection & Credentials. It says API key length is too long. Increate field length. Where is that field?
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): ua-cam.com/video/37iJjKz94Qw/v-deo.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.
What User name should I give under the related link?
Hi there! The username and password should be a Jira admin account. The password is typically an API token.