I am using the Field Definition rules to lookup and set Jira issue data and am having some trouble with a few fields and virtual functions.
1. Cascading Select Field - I can get it to pull the parent or the child value using .value or .child.value but is there a way to pull and set both values at once like in Jira? e.g. Parent - Child
2. Linked Issues - No matter what I put in, I can't seem to get anything useful
.value gets nothing
.key gets nothing
.name gets nothing
.id gets a number that I don't recognize
.type pulls up a REST code for issuelinks that includes another ID number I don't recognize, (likely associated with the linked issue)
I was hoping to set the key, or title of the linked issue, perhaps even the relationship. Would a transform virtual function help here?
3. Date Fields - Obviously it pulls the date in .jiraDate format. I have tried .formatDate .convertDate and .friendlyDate all with multiple formats (MMM dd, yyyy) (MMM/dd/yyyy) etc. and none function. Nothing gets pulled into the field, do these not work in this instance?
4. Label Manager Fields - I am trying to add some spacing or something to separate the values that it pulls. .join works on multi selects but not Label Managers
Not sure if you saw this or not, older question of mine. I am working on pulling all of the Jira fields of an issue into a Confiform and having trouble with some fields. After I get the pull working I am going to start trying to tackle updating the Jira issue via the form if you have any insight on how I should set that up
Honestly, this sounds like you want to use ConfiForms as a UI to your Jira issue... which it is not. ConfiForms is not a UI for your Jira.
To answer your question you need to provide the details of the JSON structure you have from Jira. And what fields in particular you want to "extract". Only this way it could be constructive.
For date fields you need to use parseDate function with "yyyy-MM-dd" format, as per Jira spec, to get the value from Jira into ConfiForms
Hard to advise anything else on other fields, without knowing the structures you are extracting them from
That is an excellent way of putting it. I am essentially attempting to do that (at the request of coworkers) because people don't like going back and forth between Wiki and Jira. I am going to use your opening statement as part of my argument the next time we discuss it.
Sorry Wiki= Confluence at least to everyone outside my organization
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events