Sprints without start and end date in JIRA fail to migrate to Iterations

Open
#482 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
backend

Research direction

Start by locating the Jira sprint import path and how it converts sprint dates into iterations. Check the importer’s handling of missing start and end dates, then find or add coverage for a sprint without either date. Done when importing that sprint creates an iteration instead of silently skipping it.

Written by the indexing model from the issue text.

Description

fixed-0.9.5

A sprint in JIRA is not required to have a start and end date. We have one of those sprints and this (silently) fails to import to an iteration because the dates were missing. There was no error or warning, just a missing iteration.

Dominant language
Go
Stars
421
Forks
50
Avg merge
17h 34m
Merged PRs (30d)
80

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Windshiftapp/core

All issues in Windshiftapp/core

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.