Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From primary commit message:
The rows of the Pivotal export CSV each represent either a story or an
epic. The Pivotal iteration to which a story might belong is found in
an Iteration column, and when that is defined there are also populated
Iteration Start and Iteration End columns.
This commit extends the build_entity function to return an iteration
and pt_iteration_id entry for every row. The iteration entry is a
string containing the id, start, and end dates. A string was chosen
instead of a dict or other data structure, because those are not
hashable and thus not includable in a Python set, whereas a string
is. At commit() time, the unique set of these iteration strings is
used to create Shortcut Iterations.
The title of imported Iterations is "PT {id}" where id is the Pivotal
iteration ID. The start and end dates are also imported. At this time,
no Team/Group association is made for imported Iterations.
At commit() time this code also ensures each story is associated with
the correct imported Iteration.