actions-marketplace-validations/Backlog Notifier

Automatically comments on tickets connected to your PRs, with the release version, when they get released.

Trust Signals

name	description	required	default
repo-references	Unique, human readable (1) identifiers and (2) repository names in JSON format. (1) are used as prefixes for issue numbers in PR description bodies. (2) The names of the linked repositories. Both are specified as list of associated arrays. You can specify as many ID/repo combinations as you want. The identifiers should be single words, like BACKLOG or BUGLOG which e.g. could identify repos for backlog and bug tickets. The ID, as the action searches it in the PR description, should be the prefix of the issue number. Prefix and the issue number must be separated by a dash, e.g. `BACKLOG-539`.	yes	{ "data": [ {"repo_id": "BACKLOG", "repo_name": "backlog"} ] }
message	The message that is posted in the backlog ticket. Use `#` as placeholder for the version number.	no	This issue has been resolved in version # 🚀
changelog-path	The path to the CHANGELOG.md file. Defaults to CHANGELOG.md	no	CHANGELOG.md
action	The action performed by this GitHub Action. Possible values are `notify` and `move`. Notify is the default and creates comments on tickets. Move can move an issue to a new lane on a GitHub Issues board.	no	notify
project-number	The number of the project where the issue should be moved.	no	1
updating-field	The name of the field that should be updated. It is not restricted to Status. You can update any "single selection field", e.g. the custom field "Priority".	no	Status
new-field-value	The value the respecting field should be updated to.	no	Done

no outputs