Looking for a little assistance.
I have a form that captures the JIRA Key as ${iftttResult_JIRAID} and when creating an issue in JIRA my table view of that confluence entry displays the JIRA ticket number and short description as expected.
Ideally I'd like to not create a confiform entry against the master form but copy these fields over to another form with more fields. I can map over all the fields without issue but the JIRA issue field refuses to map over. It must be something simple I'm missing. Any help is appreciated!
Same question pertaining to importing into that table API. If I were to download the API the JIRA Key field looks like "IMG-123" in my csv. However when importing back into the confiform API I run into the same issues. Again, desperate for help on this one. Thanks!
Jira field in ConfiForms holds a Jira key as text.
That means when you import or copy it to another form then you just copy the "text" that represents the Jira key.
Hard to tell what does not work for you, as there is no difference in how fields are copied.
Of course, for copying I suggest to reference a field value, not an IFTTT result (${iftttResult_JIRAID}), as it might be not available anymore
Thanks for the quick response!
So you are right, that field is stored as text, but when I look at the record in the confiform table it's formatted as a link that I can click on to navigate to the JIRA issue. Also, if I were to create a Table View Macro and bring in that field in my view it displays as a link as well which is perfect.
The issue arrives when I run an IFTTT macro to copy the JIRA key over to another table it doesn't map over. I'm assuming that's due to the JIRA Key field on the destination table is a "JIRA Issue" type field. Is there a work around to move the text based JIRA Key field from the origination table to a JIRA Issue formatted field on the destination table?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I was trying to say is that it really should make any difference - having it as text or as Jira field. It is all about presentation - Jira field just attempts to show it as a link. Storage wise it is just a text value for both types
Could you show me what are you trying to do? How do you attempt to copy the value?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I figured out my error.
I had custom CSS rules for those fields on the 2 tables that I wanted to copy over to.
display: none;
Sigh. I should probably get more sleep before reaching out to support. Thanks so much for reaching out though!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries! Glad it is resolved for you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One last question!
So the Jira Issue field maps over to my 2 other tables but I loose the hyperlink to the JIRA issue on the tables that I copied the original fields over to. The link is there on the master table but not on the table that receives the JIRA key value from the IFTTT Copy Confiforms Data over to. An I missing a velocity rule or something?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have a Jira field (type) in the target form? There is nothing extra you need to do - just copy the issue key over. And if the target field is also of type Jira field then you will see it rendered as a link to Jira issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Figured it out. Clerical error on my part. Again, thank you for the quick replies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.