Jira Integration with Jira Spoke - Mapping fields to work with bi-directional connection

[SnowDesign03]

Hello all. We have elected to use Jira Spoke for our integration. I have successfully connected the spoke and was able to trigger incidents into logs in Jira. However, I wanted to see if someone was able to achieve some difficulties mapping the required fields. 

1) Were you able to achieve creating stories for different projects or does it have to go to one project? (Example. When using the create story action, it asks for a project key & issue type. I tried creating a custom table in SN to achieve the mappings. If a project was found with the same name in Jira, it would get created in that particular project board vs setting a manual, static project that all incidents go to. I can elaborate further if someone needs more details and may know what I mean)

2) When comments & work notes are added, can we determine what is available to get populated back into Jira from SN. I will attempt to do this again with the "Add Comment" action and see if I don't get any other errors. 

3) Any overall feedback using this spoke and things you may have had to hurdle thru or operate manually due to lack of possible actions. Any information will be appreciated for anyone that fully integrated this into their environment. Mainly looking for a resource I can gain some additional insight from, as most forums and discussions urge to use things like Exalate and we are not going that route as we are getting rid of it. Thanks

[Josh Gold]

@SnowDesign03 Just curious - can I ask why you're getting rid of Exalate? What were the issues you encountered?

[SnowDesign03]

Unfortunately, looks as they are looking to move from the subscription and work with IntegrationHub, which we already use for other integrations