Loading...

XML

Word

Printable

UIS:
1
Support reference count:
3
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

If you could filter via JQL in Jira cloud for Jira Issues with MERGED pull requests (like "development[pullRequests].merged > 1" for example), that would be amazing for our workflow!
It would be really useful for us if we could get the author of a commit in a smart value. It would hopefully enable me to set up automations that assign issues to a user when they make a commit. Likewise, we tag commits when creating releases and it would be useful to be able to get those from a commit where they exist so that we can use them to set fix versions. The DevOps triggers are great and are really helping but it would definitely be helpful to have access to more of the data in Bitbucket when we use them
GitHub actions trigger the automation, and it would help if we can update the build number on the Jira issues. Currently, this action is not supported in Automation for Jira. Suggestion: Ability to use the Automation Log action to get the build number or the possibility to print the payload of the GitHub action trigger using smart values for deployment.
Add support a Deployment started event

is duplicated by

AUTO-644 Add the ability to get the payload of the GitHub action that triggers the rule.

JSWCLOUD-21666 DevOps Automation: Smart Value should include more fields

JSWCLOUD-21908 DevOps Automation: Support more smart values for DevOps triggers in Automation