Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
We are using Jira Integration to get most of the Jira fields value. But somehow "Resolved" date field is not coming in response for Jira type as Bug.
Appreciate your suggestions.
Discussion posts and replies are publicly visible
Jira fields can be weird, but they're part of what adds the customizability to Jira.
If Jira has an official field that says "Resolved", it will show up in the API JSON as "Resolved".
If your Jira Admin or project team added a custom field called "Resolved", it will show up as "customField123456" in the JSON. There is an API which gives the fields for a project, which should then tell you want custom field id you want.
On a past project, I solved some of these nuances by having Appian sync'ed records that were backed by an integration call to Jira's API's for project and issue type.