Hi All!
It would be great if any attachments added to the paragraph fields in the planning section of change requests exposed the attachments URLs in the JSON code. For integration purposes the public attachments URLs in the planning fields needs to be shared to third parties but without the code being exposed it can’t be done.
+16Yes, great suggestion!!! Please expose as much information as possible in these JSON payloads. It would open up a number of options for us to be able to extend integrations and pass along relevant ticket information. Changes and Releases require substantial documentation throughout their lifecycle, and giving us the ability to access all that information through the API would have huge benefits!
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
