10/29/2025

• Implementation #68575: Initial JIRA migration spike
  updated by Pavel Balashou on 10/29/2025 05:19 PM
  • Description changed (Details)
• Implementation #68575: Initial JIRA migration spike
  updated by Pavel Balashou on 10/29/2025 03:44 PM
  • Description changed (Details)
• Open Point #68624: Does the Jira API offer all past work item keys?
  updated by Pavel Balashou on 10/29/2025 02:05 PM
  • Comment added

    I have not found a way yet to get old issue keys through JIRA API. I assume it is not possible. If I find a way I will r...

  • Status changed from new to resolved
  • % Complete set to 100%
  • Decision set to No
• Open Point #68525: When do we make this project public?
  updated by Pavel Balashou on 10/29/2025 02:03 PM
  • Status changed from new to decided
  • Assignee deleted (Wieland Lindenthal)
  • % Complete set to 100%
  • Decision set to Right from the beggining.
• Open Point #68526: What is our Enterprise plan for the migration tool?
  updated by Pavel Balashou on 10/29/2025 02:02 PM
  • Status changed from new to decided
  • Assignee deleted (Wieland Lindenthal)
  • % Complete set to 100%
  • Decision set to Part of Community Edition.
• Open Point #68527: Is the migration code GPL3?
  updated by Pavel Balashou on 10/29/2025 02:02 PM
  • Status changed from new to decided
  • Assignee deleted (Wieland Lindenthal)
  • % Complete set to 100%
  • Decision set to Yes
• Open Point #68623: Do we actually get the internal database ID from the API?
  updated by Pavel Balashou on 10/29/2025 01:56 PM
  • Description set (Details)
  • Status changed from new to resolved
  • Assignee deleted (Pavel Balashou)
  • % Complete set to 100%
• Implementation #68575: Initial JIRA migration spike
  updated by Pavel Balashou on 10/29/2025 08:25 AM
  • Description changed (Details)