Jira integration architecture

[layla]

Hello experts,

Actually I'm working on The integration of Jira with servicenow; the need for now is to create projects in jira directly from serviceNow instance.

I have tow solutions to do:

provide a service catalog from which the user can request a project creation in Jira.

Create a new service in service portal for the same purpose.

Once a request was done I'm wondering if I should create a request with a RITM for it or should I create a new table in which I'll store jira project data.

if I have to create a new table shall I inherit from Task table?

I will need that for the Update operation, I'll need a record to ensure the synchronization between snow and Jira.

Please let me know if you have already made such an implementation and what solution have you choosen

Thanks in advance.

[Kaka Nayeem]

Hi,

  If you goes with Service Catalog solution then you need not to create new table.

  other way, you can create new table then extend from task table and create a record producer as a front-end form.

Regards,

Kaka Nayeem

PS: Hit like, Helpful or Correct depending on the impact of the response

[Brad Tilton]

If you're looking to sync your Jira records with a record in ServiceNow, I would build a table for that purpose and extend it from task. You probably don't want to sync a subset of your RITMs with an external tool. Using a record producer to front end should also make it available in Service Portal.

[layla]

Hi

Thank you for your responses.

Actually I have too many new fields related to this integration that is why I dont want to add them to an existing table; as with new coming integrations we risk to have too many fields to add.

Regarding the fact of extending Task table I have found in this blog post When to Create a New Table vs. When to Extend that there is a cost behind extending task table. Can you confirm please this and also if there is any cost while extending sc_req_item too?

Thanks a lot!

[Daniel Draes]

I would not recommend to extend sc_req_item due to the internal logics and processes around service catalog.

If it is not task based I would go for a simple standalone table. Infact, project sounds like a standalone table, but I do not know Jira good enough.