Shift the jql construction to the user #126
Assignees
Labels
enhancement
New feature or request
Comments
sgkiokas
added a commit
that referenced
this issue
Sep 7, 2021
As per title. Contributes to: #126 Signed-off-by: Stelios Gkiokas <[email protected]>
sgkiokas
added a commit
that referenced
this issue
Sep 7, 2021
* feat: Shift the jql construction to the user This PR: - shifts the jql construction is shifted to the user by letting him specify the criteria of how to search of resolved and open issues as part of the action's duplication mechanism prevention - prints more info when an error occurs in a REST call to Jira - fixes a bug with the UPLOAD_FILES parameter and with the search criteria of the issues that are already open - updates the unit tests Contributes to: #126 Signed-off-by: Stelios Gkiokas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It has been spotted that the users of the action would like to be able to pick and choose which of the fields of an issue would like to be populated with specific values (e.g.
Epic Name,Teametc.). This will make it easier for them to automatically link the issues created by the action with pre-existing Kanban boards, Dashboards, team of assignees and so on and so forth.Currently, we provide rather a rigid form of
jqlquery for such actions as shown here. The suggestion here is to move the basic parts of the query to theworkflow.yamlfile.The text was updated successfully, but these errors were encountered: