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
Import JIRA sprint names as labels. #381
Conversation
You can also import the names of any sprints associated with an issue as tags, | ||
by setting the ``jira.import_sprints`` option:: | ||
|
||
jira.import_sprints = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know you're going to hate me for suggesting this, but even though I might regret naming import_labels_as_tags
what I did name it, it might be less confusing for future readers if both import configuration options were named similarly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No hate here. It's reasonable!
if field['name'] == 'Sprint'] | ||
if len(sprint_fields) > 1: | ||
log.warn("More than one sprint custom field found. Ignoring sprints.") | ||
self.import_sprints_as_tags = False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know anything about jira but why not add multiple sprint tags?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, this is dealt with in b2ca93d
I'd like to import more jira attributes (like use the end date of the sprint as
the due date for active issues in the sprint), but that's a bit more
complicated and can wait until later.