Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for unassigning JIRA issues #1

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

wschroeder
Copy link

I added support for unassigning JIRA issues. I settled on using the word "Unassigned", which matches what users see when observing issues in JIRA through its UI. The REST API will perform an unassignment when assignee=null. I chose a magic value approach for now for least disruption to existing dependencies.

An alternative magic value could be the string "null", but this feels more like an implementation detail, a quirk of the REST interface. Another alternative would be an explicit --unassign option/command. There is some precedence for this with the --delete command. Possibly, we could clean up the entire jiraclient interface with a subcommand-plus-options approach, similar to what git uses, which would be helpful for separating the notions of search from modification. I have avoided the bigger architecture issues with the choice of simple magic value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant