Open vyprabhu opened 6 months ago
Hi @vyprabhu are you just running jira issue edit --label "abc" --no-input
or you are streaming contents from stdin echo "something" | jira issue edit --label "abc" --no-input
?
So basically, i'm searching for some keys matching a particular criteria and then I am running "jira issue edit --label "abc" --no-input" thru bash script to update the label for each key. I'm not piping anything to this command.
@ankitpokhrel
Not sure if you progressed on this one... I found a workaround in the meantime.
Research and Discovery : I observed that the command jira issue edit --label "abc" --no-input
still follows the approach of jira issue edit --label "abc"
and it waits for an "Enter" command for the description field even if you provide no-input parameter. And hence it pulls the previous output of stdin.
Workaround / Solution : The below workaround was discovered to add char code for "Enter" in the Description field alongwith --no-input to stop the command from piping in stdin:
jira issue edit -b$'\x0a' -l"$lbl" --no-input
Note that the $'\x0a' in the description field referred to as '-b' acts as an enter command without any input / amendment to the description field.
Describe the bug
Please provide following details
jira version
here.jira serverinfo
here. Version: 1001.0.0-SNAPSHOT Build Number: 100248 Deployment Type: Cloud Default Locale: en_USTo Reproduce
Steps to reproduce the behavior:
Expected behavior since no other parameter (be it summary / description / any other field) is not passed, the other fields should not be updated.
Screenshots
Additional context