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 was archived by the owner on Feb 14, 2025. It is now read-only.
I have searched the existing issues and found none that matched mine
Describe the issue
Labeling an issue with jira and then labeling/unlabeling the issue with a different label that contains a space will cause Jira to create/delete the ticket as if the jira label was added/removed. This leads to duplicated issues or deletion when it isn't desired.
Steps to reproduce it
Add some label with a space and the jira label to issue
See Issue added to Jira correctly
Remove some label with a space
See Jira delete the issue
Re-add some label with a space
See Jira recreate the issue
Relevant information
Unlabel actions logs have /home/runner/work/_temp/<hash>.sh: line 26: [: too many arguments which references if [ unlabeled == "unlabeled" ] && [ needs triage == jira ]; then. It appears the issue is caused by the expansion on the label name not being quoted.
Double check your logs
I have redacted any sensitive information from the logs
Is there an existing issue for this?
Describe the issue
Labeling an issue with
jiraand then labeling/unlabeling the issue with a different label that contains a space will cause Jira to create/delete the ticket as if thejiralabel was added/removed. This leads to duplicated issues or deletion when it isn't desired.Steps to reproduce it
some label with a spaceand thejiralabel to issuesome label with a spacesome label with a spaceRelevant information
Unlabel actions logs have
/home/runner/work/_temp/<hash>.sh: line 26: [: too many argumentswhich referencesif [ unlabeled == "unlabeled" ] && [ needs triage == jira ]; then. It appears the issue is caused by the expansion on the label name not being quoted.Double check your logs