You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2023. It is now read-only.
Could you investigate and add a support of mentioning standard and custom JIRA fields within the "#action" command? It may cover cases when in resolve or close or reopen transitions it is required to give some fields filled out, -- not just "resolution", but some more: like, "fixVersion", "affectedVersion" or some custom fields.
It might be simplified as possible, like in commit just point [#action <workflow action to be executed>[, &<jira_field>=<valid jira_field value>]].
For example, issue-123 add support of JIRA fields #time 1h #action resolve, &fixVersion=0.1.1, &cf[10900]=some value, &resolution=fixed, &some Custom Field=more value
The text was updated successfully, but these errors were encountered:
Thanks a lot for using the add-on. Your suggestion and the proposed syntax looks reasonable. Adding it now to the list of ideas to be explored. Thanks!
This is something we'd definitely be interested in, for the exact same use case - we can't resolve issues with the plugin because we require resolved issues to be markerd with a commit hash and fix version.
Hi, thanks for useful plugin. It really works!
Could you investigate and add a support of mentioning standard and custom JIRA fields within the "#action" command? It may cover cases when in resolve or close or reopen transitions it is required to give some fields filled out, -- not just "resolution", but some more: like, "fixVersion", "affectedVersion" or some custom fields.
It might be simplified as possible, like in commit just point
[#action <workflow action to be executed>[, &<jira_field>=<valid jira_field value>]]
.For example,
issue-123 add support of JIRA fields #time 1h #action resolve, &fixVersion=0.1.1, &cf[10900]=some value, &resolution=fixed, &some Custom Field=more value
The text was updated successfully, but these errors were encountered: