what links a comment to an issue, i.e. the key field

[Sam Dunkerton]

So Im trying to integrate Jira with Salesforce cases using Zapier as the intermediate/API tool.  The aim - when someone posts a comment to any Jira Issue, I use zapier to trigger on comment creation, find the details of the related issue (whichs holds the SF case number) and then marry that up to the SF case.  However, I can get the comment ok, but struggling to then use Zapier to find the Jira tcket details in order to then search SF for a match.  Anyone know what links the comment to the Jira Issue (as in, some kind of ID/lookup field).  Or indeed, another way of achieving the aim (passing Jira issue comments back to SF cases)

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

It's the issue itself that "links" the comments to the issue.  The issues are containers for comments.  In the database, there's a big table full of comments, and one of the columns in that is "issue id"

So, I think you need to rephrase the question.  What does your Zapier code need from Jira to understand that a comment is on an issue?  The issue ID?

[Sam Dunkerton]

Hi @Nic Brough -Adaptavist- thanks for the reply, yes you are correct, however when Im using Zap, triggered by a new comment, I then check the fields made available to me (the fields available from the comment) and the only ID I can find is a 5 digit one.  I then try and use that 5 digit ID to find the actual issue (because the field I need to match upon is stored as a 'label' on the issue) but the record returned by that ID is NOT the issue, and the label field I need is not available, so im trying to figure out how I can find the label from the issue itself (which stores my SF case number).  Any ideas/guidance?  When I try to find the Jira issue using that 5 digit key, it seems to return me something else, including multiple keys and ids (so I think its gathering detail from a range of issues within a project, not just the one I want).  Sorry got myself a bit lost in the world of Jira ID's and data model!

[Sam Dunkerton]

my steps are:

1 - triggered by new comment created in Jira

2 - find the details of the issue the comment is related to (screenshot below - FAIL)

3 - then attempt to find the SF case to match the label of the issue

4 - update the SF case by pushing the Jira comment to the case feed

Any guidance you can give to help find the right Jira issue and the associated label so I can advance to step 3 would greatly help, thanks

[Nic Brough -Adaptavist-]

That ID is probably the issue id in the database, which is not normally exposed to users and other systems.  It's also pretty much useless, as you can't search by it remotely.

You should probably be giving it the issue key, which is the unique human identifier that can be used in search and to build URLs for direct access to Jira issues.

The issue key is always exposed on any view of the issue, and in the URL if you are referring to it directly. 

[Sam Dunkerton]

ok thanks @Nic Brough -Adaptavist- I think it must be a limitation with Zapier then because I cant see any other ids made available to me at all (using the 'new comment' trigger).  I tried matching on the issue URL but that doesnt work, and theres no sign of the issue id, name or anything remotely useful unfortunately.  Might have to think on another solution......

[Nic Brough -Adaptavist-]

I cannot work out a way to do this with Zapier (which annoys me because I think we should be able to)

[Sam Dunkerton]

hey @Nic Brough -Adaptavist- I agree, thanks for trying, at least Im finding some solace in that it wasn't just me doing something silly!  Let me know if you do find an avenue to solve this one.  Seems odd Zapier would have a trigger on Jira comment creation but no-way of then getting to the actual issue (and associated data) that the comment was related to!  thanks for your help so far!

[Sam Dunkerton]

p.s.I already have ticket creation (SF case --> Jira ticket) and passback to SF (Jira ticket number and url link) working a-okay using Zapier.  I just want to pass any updates/comments from Jira back to the SF case feed also