-
Suggestion
-
Resolution: Timed out
-
2
-
Issue Summary
The free Jenkins for Jira (Official) plugin, developed by Atlassian to integrate with Jenkins, allow users to send build and deployment events to Jira so that they’re visible in Jira issues, on the deployments timeline, and in the Releases feature by including Jira issue keys (e.g. FUSE-123) in their commit messages.
However, it doesn't work the other way around - trigger builds events from Jira.
Suggestion
Builds could be triggered from within Jira, manually, or by having a Post-Function that could trigger the build (or automation action).
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management