Feature Request
Applying the same change to many tickets requires a shell loop:
for ticket in PROJ-100 PROJ-101 PROJ-102 ...; do
jr-a issue edit "$ticket" --label add:some.label --no-input
done
This works but makes one HTTP request per ticket. For 50+ tickets this takes 30-60 seconds.
Proposed
Accept multiple keys:
jr-a issue move PROJ-100 PROJ-101 PROJ-102 "Done"
jr-a issue edit PROJ-100 PROJ-101 PROJ-102 --label add:some.label
Or JQL-based bulk operations:
jr-a issue edit --jql 'labels = "some.label" AND status = "To Do"' --label add:another.label
jr-a issue move --jql 'project = PROJ AND status = "To Do"' "Done"
Caveat
Bulk operations carry risk (applying wrong labels to many tickets at once). A --dry-run flag showing what would change before applying would mitigate this. This may also be out of scope for a CLI tool if the Jira API doesn't support batch mutations.
Feature Request
Applying the same change to many tickets requires a shell loop:
This works but makes one HTTP request per ticket. For 50+ tickets this takes 30-60 seconds.
Proposed
Accept multiple keys:
jr-a issue move PROJ-100 PROJ-101 PROJ-102 "Done" jr-a issue edit PROJ-100 PROJ-101 PROJ-102 --label add:some.labelOr JQL-based bulk operations:
Caveat
Bulk operations carry risk (applying wrong labels to many tickets at once). A
--dry-runflag showing what would change before applying would mitigate this. This may also be out of scope for a CLI tool if the Jira API doesn't support batch mutations.