10/29/2025

• Implementation JIM-7: Initial JIRA migration spike
  updated by Pavel Balashou on 10/29/2025 06:19 PM
  • Description changed (Details)
• Implementation JIM-7: Initial JIRA migration spike
  updated by Pavel Balashou on 10/29/2025 04:44 PM
  • Description changed (Details)
• Open Point JIM-11: Does the Jira API offer all past work item keys?
  updated by Pavel Balashou on 10/29/2025 03: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 JIM-3: When do we make this project public?
  updated by Pavel Balashou on 10/29/2025 03: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 JIM-4: What is our Enterprise plan for the migration tool?
  updated by Pavel Balashou on 10/29/2025 03: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 JIM-5: Is the migration code GPL3?
  updated by Pavel Balashou on 10/29/2025 03:02 PM
  • Status changed from new to decided
  • Assignee deleted (Wieland Lindenthal)
  • % Complete set to 100%
  • Decision set to Yes
• Open Point JIM-10: Do we actually get the internal database ID from the API?
  updated by Pavel Balashou on 10/29/2025 02:56 PM
  • Description set (Details)
  • Status changed from new to resolved
  • Assignee deleted (Pavel Balashou)
  • % Complete set to 100%
• Implementation JIM-7: Initial JIRA migration spike
  updated by Pavel Balashou on 10/29/2025 09:25 AM
  • Description changed (Details)

10/28/2025

• Task JIM-6: Get example data (donations) to migrate
  updated by Rosanna Sibora on 10/28/2025 10:10 AM
  • Description changed (Details)
• Feature JIM-9: Work package identifier aliases and redirects
  updated by Wieland Lindenthal on 10/28/2025 09:50 AM
  • Comment added

    Updated automatically by changing values within child work package JIM-11

  • Scheduling mode set to Automatic
• Open Point JIM-11: Does the Jira API offer all past work item keys?
  created by Wieland Lindenthal on 10/28/2025 09:50 AM
• Feature JIM-8: Origin Key and Origin Internal ID for imported work packages
  updated by Wieland Lindenthal on 10/28/2025 09:45 AM
  • Comment added

    Updated automatically by changing values within child work package JIM-10

  • Scheduling mode set to Automatic
• Open Point JIM-10: Do we actually get the internal database ID from the API?
  created by Wieland Lindenthal on 10/28/2025 09:45 AM
• Task JIM-6: Get example data (donations) to migrate
  updated by Rosanna Sibora on 10/28/2025 09:39 AM
  • Description changed (Details)

10/27/2025

• Feature JIM-9: Work package identifier aliases and redirects
  updated by Wieland Lindenthal on 10/27/2025 06:13 PM
  • Comment added

    There can even be interesting operators like "greater than" which allow you select those work items that have a sequence...

• Feature JIM-9: Work package identifier aliases and redirects
  updated by Wieland Lindenthal on 10/27/2025 06:08 PM
  • Comment added

    I just found out that in JQL you can filter on old keys and still find the issues:

• Implementation JIM-7: Initial JIRA migration spike
  updated by Pavel Balashou on 10/27/2025 03:25 PM
  • Description changed (Details)
• Feature JIM-8: Origin Key and Origin Internal ID for imported work packages
  updated by Wieland Lindenthal on 10/27/2025 03:19 PM
  • Description changed (Details)
• Feature JIM-9: Work package identifier aliases and redirects
  created by Wieland Lindenthal on 10/27/2025 02:19 PM
• Feature JIM-8: Origin Key and Origin Internal ID for imported work packages
  created by Wieland Lindenthal on 10/27/2025 02:17 PM