Outdated Documentation and AI

Good day,

Certain documentation links like SimpleDateFormat here: How to Sync Date/DateTime Custom Fields in Jira Cloud seem to be outdated and do not work in my Groovy scripts. Whenever I have asked the AI chat agent (Aida | Exalate Documentation) anything, it always refers me to documentation on dead links.

This is not urgent, but outdated documentation does concern me as I don’t have a reliable source to validate any deprecated functionality against and remediate before it is completely removed, and doing things with trial and error is more time consuming (especially since we have Exalate connectivity issues on ADO).

Is there any source where I can get up to date documentation? Thanks.

Hi @Kris ,

The flag is much appreciated! Let us get this fixed pronto.

In terms of documentation, our official site is indeed the documentation site. The scripts do change from time to time (due to product evolution etc.) but these are updated on the site itself. But clearly we missed the ball on this one.

The particular document you cited is supposed to be used with Jira Cloud and Jira Server, but you have a little mention of ADO there as well. Can you please clarify which platforms you are connecting (what is source of datetime field, and what is destination), and also is there an error you are getting - maybe we can help to resolve this.

Thanks
Majid

2 Likes

Hi @Majid

Thank you for the feedback. Much appreciated. I have worked around and pretty much resolved the issue with the date before this post (as I was asked to create a community post).

In my case there were multiple new actions I was trying to perform using both the Exalate docs and Aida as a reference and either kept hitting dead links or like the nodeHelper.getuserbyemail for ADO that said “Returns a null in case the Exalate user has no ‘Browse Users’ permissions” but got an “Invalid token” error instead leading me down that road of renewing the token, then going through all the lines I added to the connection string one by one until the error disappeared.

Everything here was fixable, but I was concerned about changes being documented and how we get deprecation notices for Exalate specific functions, not Groovy (though would like to know when a Groovy version is updated if possible).

1 Like

Thank you for the details Kris.
I will surely pass the feedback onto Product and AI teams.

Thanks once again for raising this!

Majid