-
Bug
-
Resolution: Timed out
-
Low
-
Severity 3 - Minor
-
Issue Summary
Jira Rest API's accept a URL in SSH and HTTP format, however automation triggers only work when the URL is supplied in HTTP format.
Steps to Reproduce
- Step 1
Use the JIRA Development Information API to store repository details, providing the repository URL in SSH format, for example
{ "id": "d2e56c5c-5cae-4852-9fc6-4f25abee7212", "url": "git@bitbucket.org:repo12.git", "name": "repo12", "avatar": "my-avatar-url", "commits": [], "branches": [], "description": "The repo1 repository", "pullRequests": [], "updateSequenceId": 2, "avatarDescription": "Something witty" }
- Step 2
Create an automation trigger for a 'Commit Created' event, then create a commit in your repository.
Expected Results
An error is displayed when the URL is supplied in the incorrect format; OR
Automation events are triggered for SSH URL's
Actual Results
No error is displayed when the URL is supplied in SSH format; AND
Automation events are not triggered for SSH URL's
Workaround
Entering all URL's in HTTP format and not SSH format.
Hi all,
Thank you for raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.
To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.