There is a flaky scenario in the update release endpoint:
When a release is updated and a new ticket from a Jira board that does not have a release is called, looks like the entire changelog enters as new [Needs investigation]
It would be nice if baroneza created the release when updating. This could be configured through a parameter.
There is a flaky scenario in the update release endpoint:
When a release is updated and a new ticket from a Jira board that does not have a release is called, looks like the entire changelog enters as new [Needs investigation]
It would be nice if baroneza created the release when updating. This could be configured through a parameter.