17
Views
1
Comments
[Jira Connector] We need more flexibility in the JiraConnector library (ODC)
Jira Connector
Forge asset by Luís Monteiro
Application Type
Reactive

As mentioned in the title, we would greatly benefit if the recently created library "JiraConnector" featured a little more parametrization to it's consumer applications.

Specifically for us, we need to be able to do two things:

1.- add/transmit our own request headers to the REST METHODS that run in the library


2.- (this one will beneft anyone else using JiraConnector) We should also be able to set "jira custom fields" in the "Issue_Create" method, and these should also be part of the returned data in the "Issue_GetById" method.

The reason we believe these updates are needed is because we can't edit JiraConnector directly, unless we want to use a clone of it. Which prompts yet another question. If we did use a clone of JiraConnector, what would happen to the updates the original library would receive over time? would our clone also get those updates? if it did get updated, would it then overwrite our changes?


Thanks

2025-09-25 14-38-22
Lokesh Kumar Yadav

You’re right more parameterization in Jira Connector would help a lot. Currently, to customize headers or handle custom fields, you'd need to clone it. But cloned libraries won’t receive future updates from the original; you’d have to manually merge changes, and updates could overwrite your customizations. So, native support in the official component would be ideal. 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.