I am experiencing an issue that might be similar to Jira Issue Tracker setup issues - #16 by zandreb.
I currently use Octopus Cloud and Jira cloud, and have set up my integration between the two correctly (the two Test buttons come back green). I’m using Jenkins pipelines for my build process and am pushing the build information before creating the Release. I have also configured my Octopus environments to match up to various Jira environments.
I can also see the build information in Library -> Packages in Octopus correctly. If I go through Library -> Build Information, I get a red error with some nice dev notes: "Error converting value “Currently hardcoded to 60-second idle and 30-second timeout for staying active to ease testing. Let me know if that should be smaller, and make a story to reconfigure with prod values when passed testing.” to type ‘Octopus.Server.Extensibility.JiraIntegration.Integration.JiraDoc’. Path ‘issues.fields.comment.comments.body’, line 1, position 1592. Could not cast or convert from System.String to Octopus.Server.Extensibility.JiraIntegration.Integration.JiraDoc.
The problems I’m seeing is that the Jira issues are not links in the Release Notes, and I do not get deployment information in my Jira stories when connected via commit comments.
This WAS working weeks ago, but at some point it stopped. I’m not sure when, we just noticed it was missing when we needed it the most.
Can anyone provide some advice, maybe things I might have misconfigured or otherwise messed up?