It seems the API to update a JIRA Issue is not made available in the JIRA Connector, could you please add it? An example of usage would be great too!
Hey, I believe I can help here... I've been working on some enhancements in the component, and one of these is and Issue_Update action.
It's attached here so you can use for reference. Hope this helps.
PS.: It's a dev-version, so please, take good care on testing it before putting on Production.
Thanks for the quick reply, I will check it out. I hope and expect Outsystems to provide an official solution if this is a supported component. It would be great if create / update could also handle custom fields (of type text at least).
This connector is meant to be a base for integrations with Jira. Our user community is encouraged to extend it to suit their purposes, by following the implementation patterns already present.
Did you try to add the API using the existing ones as an example? Did you run into a specific issue we can help you with?
I extended the connector by cloning it, added support for updating an issue and using custom fields. See https://www.outsystems.com/forge/component/1792/JIRAConnectorWithCustomFields
It is regrettable that in order to support custom fields you need to hard code the associated JSON names in extra attributes on IssueFields requiring to deploy a version specific to a certain JIRA instance. See also my post https://www.outsystems.com/forums/discussion/16004/create-issue-with-custom-fields/
JIRA has an API to discover the JSON keys necessary to use for the custom fields, but I can't figure out how to dynamically generate a form to capture data for these custom fields and how to generate the rest call... Any ideas on how to support these dynamic JIRA custom fields in a generic way?
First of all let me thank you for your initiative to extend this connector and for sharing the result.
We are currently working on the Jira connector as well, and as soon as I saw that you published your clone I made a note for us to go and look at what you've been working on and get in touch with you.
In order to answer your question properly we need to take some time and I'm hoping we can fit this into our next sprint, which means sometime next week. I don't think we can spare the time to do it this week.
Extending the connector to support custom fields posed some difficulties for us too, and once we get a chance to see how you went about it we can compare to our approach and comment.
Does that help?
Sure, I'll be happy to answer any questions; I fear we might be hitting an inherent limitation in the platform support for web services. I am curious to your findings, good luck!